Anchor Contract
The Anchor Contract is a data inscription published on Bitcoin. A validator is configured to follow a particular anchor and uses its contents to establish the protocol's initial identity and rules. It is not a program that Bitcoin nodes execute.
Published contents
Network and domain: identify the Bitcoin network and protocol instance.
Boot height: identifies the height from which protocol indexing begins.
Assets: bind recognised Rune IDs to their mint commitments.
Signers: identify authorised public keys by role and index, including guardian groups and oracles.
Terms: define values used in validation, such as collateral requirements, liquidation rates and minimum output amounts.
Publication makes this configuration independently inspectable. It does not prove that an application uses that configuration, that its operators are available, or that governance voting is operational.
Anchor and contract identifiers
The anchor location can be represented as height:transaction_index:transaction_id. The API's anchor_id is a tagged hash of those publication coordinates.
A contract_id is a separate tagged hash that binds an anchor ID to contract publication coordinates. It is not the raw Bitcoin transaction ID. In the configuration documented here, the anchor publication also supplies the contract publication coordinates.
The parameter reference gives the publication coordinates for the UNIT/USD mainnet snapshot used in these docs.
Versions and governance
The implementation includes protocol profiles, historical state and identifiers that support distinguishing versions. This does not by itself implement tokenholder voting or automatic publication of updated terms under an unchanged anchor.
The planned governance model should be distinguished from current anchor configuration. Existing vault scripts commit to their spending keys and threshold hashes; publishing a new data record alone cannot rewrite those Bitcoin outputs.
Last updated

