Glossary

Protocol

Message — signed operation envelope containing data, hash, signature, and Ed25519 signer.
MessageData — canonical address-native payload carrying type, timestamp, network, owner_address, and exactly one body variant.
owner_address — the sole canonical account identifier in V2. Raw 20-byte EVM-style address.
1P — one-phase state change with no paired remove message.
2P — add/remove set semantics where remove wins on a tie.
CAS — compare-and-swap semantics used by refs.
ExecutionPayload — canonical committed execution payload paired with each persisted block in V2.

Delegated key — Ed25519 protocol signing key registered to an owner_address.
Scope — delegated-key privilege level: OWNER, SIGNING, or AGENT.
allowed_projects — optional project allowlist bound into SIGNER_ADD for AGENT keys.
custody signature — EIP-712 signature from owner_address authorizing SIGNER_ADD or SIGNER_REMOVE.
request_owner_address — external wallet address that requested a signer addition. Used for app attribution.
request_signature — EIP-712 app-attribution signature proving the requesting app wallet participated in SIGNER_ADD.
custody_nonce — monotonic per-account replay counter for signer-management messages.
claim signature — proof used by VERIFICATION_ADD to attest an ETH or SOL identity.

SIGNER_ADD — custody-backed add operation for an Ed25519 delegated key.
SIGNER_REMOVE — custody-backed remove operation for an Ed25519 delegated key.
STORAGE_CLAIM — the only Tempo-backed storage ingress path in V2.
target_owner_address — address-native collaborator or follow target.
author_address — self-attested commit author identity in CommitMeta.
claim_key_type — wallet signature family used by an ETH verification claim.
claim_block_hash — historical Tempo block hash bound into an ERC-1271 ETH verification claim.

Merge request — a cross-project contribution proposal from a fork descendant to an upstream project. Recorded onchain as MERGE_REQUEST_ADD and closed by MERGE_REQUEST_REMOVE.
request_id — content-addressed merge request identity: H(canonical_encode(MessageData)), the MERGE_REQUEST_ADD message hash. Different timestamps produce different IDs, so the same requester can open multiple requests against the same project.
Fork lineage — the retained parent-chain under prefix 0x1A that links a fork descendant to its source project. Bounded to MAX_FORK_LINEAGE_DEPTH = 256 hops. Persists across project removal and pruning.
Dual authorization — MERGE_REQUEST_REMOVE authorization model: the original requester may withdraw, or a target project owner/collaborator with WRITE+ may close.