“A Capsule certificate is defined by the requirement that its Tx Hash must be an anchor transaction fired at the moment of registration, making the Etherscan link immediately verifiable upon issue.”
PropositionsThe Tx Hash embedded in a Capsule certificate is not merely any transaction reference but specifically an anchor transaction. This anchor fires as part of the registration process itself, so the verifiable Etherscan link is present at the moment of issue rather than added later.
ConstraintsThe Tx Hash must be an anchor transaction; no other transaction type satisfies the Capsule certificate definition. The Etherscan link must be verifiable at the moment of issue, excluding any arrangement where verification is deferred by days.
MechanismsThe anchor transaction fires as an integral part of the registration event, simultaneously producing the Tx Hash that is embedded in the certificate and making the corresponding Etherscan link live and verifiable.
BoundariesThe excerpt addresses only the relationship between the Capsule certificate, its Tx Hash, the anchor transaction, and the timing of Etherscan verifiability; it does not cover other certificate types, blockchain networks beyond Etherscan, or broader registry processes.
Files fingerprinted by this registration
These files were fingerprinted by the registrant and were never uploaded. The registration time above applies to each fingerprint below: a fingerprint cannot be produced without the file it describes. This record does not establish authorship or ownership of the files named.