Contracts Overview

Makechain V2 does not use validator-relayed host-chain identity or signer events.

The active protocol contract surface is much smaller than the legacy relay-era stack.

What remains relevant

• STORAGE_CLAIM settlement verification
• historical ERC-1271 validation pinned to a finalized Tempo blockHash
• the host_chain_id(network) mapping used by V2 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 V2AddressNative behavior:

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

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

Storage claims

STORAGE_CLAIM is the only Tempo-backed storage ingress path.

The claim carries settlement evidence directly in the message body:

• settlement_tx_hash
• settlement_chain_id
• settlement_log_index
• actor

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.

ERC-1271

ERC-1271 is supported for:

• custody signatures
• app-attribution signatures
• ETH verification claims

Validation is performed only on the Tempo settlement chain selected by host_chain_id(network) and only at the exact finalized blockHash bound into the signed payload.