Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

feat(nip77): advertise NIP-77 in NIP-11 and expose its settings in the admin console

已关闭
#819 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@Priyanshubhartistm 已经在做这个了。

开始于 2026年10月12日。

  • #830 来自 @Priyanshubhartistm —— 已合并

评估

这个 Issue 还没有评估数据。

描述

enhancement

Is your feature request related to a problem? Please describe.
Relays can now answer NIP-77 sync requests when nip77.enabled is set (#817/#818), but nothing tells clients so. NIP-11 supported_nips does not list 77, so a client or another relay has to open a NEG-OPEN and read the error to find out whether the relay supports negentropy. The nip77 settings can also only be changed by editing the settings file, unlike nip45, nip50 and nip56, which are available in the admin console.

Describe the solution you'd like

  • Advertise 77 in the NIP-11 supported_nips only while NIP-77 is actually active (nip77.enabled is true and eventStore.backend is postgres), the same way 43 is only listed when NIP-43 is enabled. A relay that has it switched off, or that serves another backend, must not claim to support it.
  • Add the nip77 settings (enabled, maxEventsPerSession, maxSessionsPerConnection, sessionIdleTimeoutMs) to the admin console's guided settings, with validation matching validateSettings (positive integers).
  • Tests for the NIP-11 output with the feature on, off, and with a different backend, and for the new guided settings entries.
  • A final pass over the NIP-77 section of CONFIGURATION.md so it matches the shipped behaviour.

Additional context

主要语言
TypeScript
星标
829
派生
234
平均合并
18 小时 43 分钟
30 天内合并 PR
67

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

cameri/nostream 的其他 Issue

查看 cameri/nostream 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。