docs: commit-reveal as built, and its chipnet run; site bundle rebuilt
The addendum gains a section stating the rule that was implemented and why the contest window and the commit's lifetime differ from the first specification. The run records a front-runner registering a name first and losing it to the older commit.
This commit is contained in:
parent
cc683130b5
commit
b1c77db313
1 changed files with 5 additions and 1 deletions
|
|
@ -70,7 +70,11 @@ party had fixed in it. No transaction on chipnet carried more than one.)*
|
||||||
from. Independent transactions keep the `txid` tiebreak. *(See "Ordering"
|
from. Independent transactions keep the `txid` tiebreak. *(See "Ordering"
|
||||||
below — this rule is load-bearing, added 2026-07-26.)*
|
below — this rule is load-bearing, added 2026-07-26.)*
|
||||||
3. `REG`: valid if the same tx mints a certificate whose commitment matches the name
|
3. `REG`: valid if the same tx mints a certificate whose commitment matches the name
|
||||||
and the name is not yet taken. **First valid REG wins.** The certificate
|
and the name is not yet taken. **First valid REG wins** — with one
|
||||||
|
refinement since 2026-10-05: a `REG` may be the reveal of an earlier `CMT`
|
||||||
|
(it carries the salt `s`), and for six blocks after a name's first valid
|
||||||
|
`REG` one with an older commit takes the name instead. Optional on chipnet,
|
||||||
|
required on mainnet. See `PROTOCOL-ADDENDUM-commit-reveal.md` §0. The certificate
|
||||||
must be the **only token of its category**: the category is created by
|
must be the **only token of its category**: the category is created by
|
||||||
this transaction (it spends, at output index 0, the outpoint whose txid is
|
this transaction (it spends, at output index 0, the outpoint whose txid is
|
||||||
the category), exactly one output carries it, and that output is an NFT
|
the category), exactly one output carries it, and that output is an NFT
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue