Contracts Overview

Makechain's active contract surface is small — far smaller than the legacy relay-era stack. Validators do not relay host-chain identity or signer events into consensus.

What remains relevant

  • STORAGE_CLAIM settlement verification
  • the host_chain_id(network) mapping used by typed data

Those are message-local checks. They do not create Makechain accounts, inject system messages, or mutate consensus state through relayed events.

What was removed from active protocol semantics

These are not part of address-native behavior:

  • registry-driven account creation
  • validator relaying of Tempo events into blocks
  • relay-derived signer authorization
  • ERC-1271 custody and verification
  • protocol-level ownership transfer
  • protocol-level recovery

That means the old identity-contract stack is not an active ingress path for consensus.

Storage claims

STORAGE_CLAIM is the only Tempo-backed storage ingress path.

The claim carries a self-verifying in-band proof of the Tempo settlement directly in the message body — a Tempo BLS finalization certificate, the RLP block header, the transaction receipt, and a receipts-trie inclusion proof:

  • settlement_chain_id
  • tx_index — index of the settlement transaction in its block (the receipts-trie key)
  • settlement_log_index — index of the Rent log within that receipt
  • finalization_cert — Tempo threshold-BLS finalization certificate over the settlement block
  • header_rlp — RLP-encoded Tempo block header; its hash must equal the certificate's finalized payload
  • receipt_rlp — RLP-encoded settlement transaction receipt
  • proof_nodes — receipts-trie inclusion proof binding the receipt to header.receiptsRoot
  • settlement_tx_hash — display-only, for explorer and relayer reconciliation; not part of the claim identity

Every node verifies the claim in-band with a pure function and zero Tempo RPC — it BLS-verifies the certificate against the chainspec-pinned Tempo identity, binds the header to the certificate, and verifies the receipt's trie inclusion. The economic values (actor, owner, units, and the settlement-block timestamp that derives grant expiry) are derived from the proven Rent log and header, not carried in the body. There is no validator/follower split and no replay against Tempo — the off-chain relayer, which cannot forge a threshold-BLS certificate, only supplies the evidence.

Appendix A now assigns both DEVNET and TESTNET to the Tempo Moderato StorageRelay proxy 0x930dc180AaD00fc9302278d502Ff8b52bB0a0F79.

MAINNET still uses the zero-address fail-closed sentinel until its canonical StorageRelay deployment is published.

AccountKeychain custody and external-address verification are verified from Makechain message bytes and state only. The node does not perform ERC-1271 eth_call checks during propose, verify, apply, replay, or sync.