silentmode/argus
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: how a resolver reads a covenant-held name; site bundle rebuilt

Browse source 
The addendum states the claim, the paid-entry rule, why a name inside the
covenant answers only to a verified state, and when a name stops
resolving. The registration bundle is rebuilt so the dashboard and market
index names by the same rules as the gateway.
This commit is contained in:
Local Dev 2026-10-04 18:14:49 +02:00
parent 9404c024b7
commit 18385600fa
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
PROTOCOL.md
View file

@ -82,6 +82,10 @@ party had fixed in it. No transaction on chipnet carried more than one.)*
released (rule 5), the `REG` must be in a later block than the confirmed
release — the one-block gap.
4. `UPD`: valid if some output of the tx carries the name's category.
A name whose certificate is held by the registry covenant answers only to
an `UPD` that states the covenant state (`c`) and whose claim matches the
certificate's address; it stops resolving once its grace period has
passed. See `PROTOCOL-ADDENDUM-covenant-names.md`. *(Chipnet, 2026-10-04.)*
5. `REL`: valid if the name is registered, no output of the tx carries the
name's category, and one input spends an output of an earlier beacon
transaction that carries the certificate. The name leaves the index.