Repository navigation
Minor Changes
-
#1088
e1f92adThanks @Ferryx349! - feat(peering): deliver paid peering invoices and gate peer feedsConfigured peers can request their BOLT11 invoice as a signed
kind 402event
and pay it through Relay B's existing processor. FeedREQ,COUNTand NIP-77
requests are refused with a payment-required reason until a paid period is
active. Expired invoices are reissued after a cooldown, and a missed webhook is
rechecked before access is denied. -
#1087
1d5c473Thanks @Ferryx349! - feat(peering): add the paid peering billing ledger -
#1089
15de73aThanks @Ferryx349! - feat(peering): renew, lapse and expose paid peering accessThe billing worker now issues renewal invoices before a period ends, rechecks
pending payments before lapsing a peer, closes live peer sockets on lapse, and
keeps stored events and sync state for a later resume.GET /admin/peeringand
the dashboard show billing status, access end, the open invoice and the last
processor error. NEG-MSG rechecks paid access so an open NIP-77 session cannot
keep syncing after the paid period ends.
Patch Changes
-
#1145
afb381fThanks @Priyanshubhartistm! - fix(admin): revoke the session token at logout, not only its cookiePOST /admin/logoutdeleted the browser cookie but the session token itself stayed valid until it expired (24 hours by default), because the token was only<expiresAt>.<signature>and nothing on the server recorded a logout. A copy of the token kept elsewhere (aBearerclient, a log, a proxy) could restore administrator access after sign-out. The token now carries a random session id under the same signature, logout records that id in Redis until the token would have expired, and every admin request checks it, so a logout on one worker ends the session on all of them and ends only that session. If Redis cannot be read the token is refused, and a logout that cannot record the id answers 500 (and still clears the cookie).Tokens issued before this change have no session id and are refused, so every administrator signs in once more after the upgrade.
-
#1091
6b3db4dThanks @Priyanshubhartistm! - fix(cli): reject a SECRET that cannot be saved to .env and read back unchanged -
#1156
69197f7Thanks @Priyanshubhartistm! - fix(logging): do not write credential headers to debug logsDebug logging of incoming requests printed every header, so the admin session cookie, an
Authorizationbearer token, API keys and webhook signatures could be read from the logs and reused. The rate-limit middleware, the WebSocket connection log and the four payment callback controllers now log the headers with the value of every credential-bearing header replaced by[redacted]. -
#1157
8e90d9eThanks @Priyanshubhartistm! - fix(settings): reload settings when either settings.yaml or settings.json changesA worker watched only the settings file whose extension existed when it started. The loader reads
settings.yamlfirst and falls back to the deprecatedsettings.json, and the admin console and the CLI always writesettings.yaml, so a worker that started fromsettings.jsonnever reloaded after the yaml file was written. A change such as removing a pubkey from the NIP-98 admin allowlist stayed unseen by that worker until it restarted. The watcher now reloads on a change to either file. -
#1118
5c4b4f0Thanks @Ferryx349! - fix(admin): serialize every settings-file writer with the settings write lockThe lock records its owner hostname and refreshes a heartbeat, so a relay in a
container no longer steals a live CLI lock just because the host PID does not
exist in its own PID namespace. On the same host the lock checks the owner's
process start time, so a reused PID is reclaimed without ever evicting a slow
writer, and async writers keep the lock until they settle.