• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

cameri / nostream / 44398554820
80%

Build:
DEFAULT BRANCH: main
Ran 18 Nov 2026 09:13PM UTC
Jobs 2
Files 339
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

18 Nov 2026 09:09PM UTC coverage: 79.258% (+0.01%) from 79.245%
44398554820

push

github

web-flow
fix(nip05): a changed identifier does not inherit the earlier verification (#1172)

## Description
When an author publishes a kind-0 profile, `processNip05Metadata` looks
the `nip05` identifier up and `buildMetadataVerification` builds the row
to store. For a transient lookup error (a timeout, a 5xx) the row kept
`isVerified` and `lastVerifiedAt` from the existing row, so that one
network hiccup does not lock out a verified author. It did this
**whatever identifier the profile now carried**: the row was written
with the new `nip05` and `domain` but the old verification.

With `nip05.mode: enabled`, `checkNip05Verification` accepts an author
whose row has a `lastVerifiedAt` inside `verifyExpiration` and whose
domain passes the allow and block lists. So an author who was verified
at one identifier could change the profile to another one, make the
lookup fail (for example with a domain that times out or answers 5xx),
and be treated as verified at the new identifier and domain: for up to
`verifyExpiration` (one week by default) they publish under an
identifier they have not proven, including a domain a later change to
the allow or block list was meant to exclude.

- the earlier `isVerified` and `lastVerifiedAt` are now kept after a
transient error only when the identifier and the domain are the same as
in the existing row (compared without regard to letter case, since the
local part and domain of a NIP-05 identifier are case-insensitive);
- a changed identifier starts as unverified with no `lastVerifiedAt`, so
publishing is refused ("NIP-05 verification required") until a lookup of
that identifier succeeds;
- `failureCount` and `lastCheckedAt` are bumped as before, and nothing
changes for a successful lookup or a definitive mismatch.

Who is affected: only relays that set `nip05.mode` to `enabled`; the
default is `disabled`.

## Related Issue
Partly addresses #1020 (finding F-039). That issue groups six findings;
this PR only does F-039, so it does not cl... (continued)

5442 of 7452 branches covered (73.03%)

Branch coverage included in aggregate %.

1 of 1 new or added line in 1 file covered. (100.0%)

11474 of 13891 relevant lines covered (82.6%)

679.01 hits per line

Jobs
ID Job ID Ran Files Coverage
1 Integration - 44398554820.1 18 Nov 2026 09:13PM UTC 339
34.94
GitHub Action Run
2 Unit - 44398554820.2 18 Nov 2026 09:14PM UTC 339
77.14
GitHub Action Run
Source Files on build 44398554820
  • Tree
  • List 339
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #44398554820
  • 5f25408a on github
  • Prev Build on main (#44396771360)
  • Next Build on main (#44399267484)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc