Execution Address

Overview

An execution address is used by the layer that processes transactions, balances, and smart-contract calls. On Ethereum it is a 20-byte EVM address, while consensus validators use separate BLS public keys for voting and may configure an execution address for fee recipients or withdrawals.

The distinction prevents confusion between consensus identity and spendable account control. Entering an execution address in a validator setting does not transfer the validator’s signing authority, but it can determine where rewards or withdrawals are delivered. Operators must verify the correct network, checksum, custody, and configuration field before setting an execution destination. Payment systems should treat the address according to execution-layer account rules. Lost control or wrong-network configuration can make delivered funds unrecoverable. Normalization, case conversion, truncation, and alias resolution need protocol-aware rules, because a visually similar value can represent a different destination or fail checksum validation. Systems storing Execution Address should preserve the exact value together with chain identifiers and type metadata.

Testing for Execution Address should include valid and invalid examples, wrong-network values, boundary encodings, contract destinations, and any memo or tag requirements. Higher-value transfers benefit from an independent destination check rather than reliance on shortened display text. A string that passes a format check can still belong to the wrong chain, unsupported asset, contract type, or destination that requires a memo or tag. Execution Address must be interpreted with its network, address or account type, encoding rules, and any required routing fields. Settlement consideration: Execution addresses receive or control transaction-layer value, while consensus validator identities use separate keys and responsibilities.