Infrastructure

EIP-658 receipts report whether top-level execution succeeded or failed. Inclusion, execution success, the intended application result, and finality are different states. JSON-RPC encodes status as 0x1 or 0x0; normalize the representation returned by your SDK before displaying an outcome.

Stages: Status & Confirmation

EIP-1014 introduced CREATE2, which calculates a contract address from a deployer, salt and exact initialization code before deployment. Counterfactual wallets can use this when they have a supported factory and verified control path. A predicted address alone does not guarantee deployment, sponsorship or safe recovery of funds.

Stages: Infrastructure

ERC-1167 defines minimal clones that delegate calls to a fixed implementation address. Many instances can share code while keeping separate storage. The small runtime can reduce deployment gas, but the actual fee and confirmation time depend on the factory, initialization and network.

Stages: Infrastructure

EIP-1559 defines Ethereum's type-2 fee market: a base fee, optional priority fee, max fee cap, and base-fee burn on Ethereum. Monad supports EIP-1559-compatible type-2 transactions but uses chain-specific accounting: gas is charged from the gas limit and its base-fee controller differs from Ethereum's. Label the network and verify fee accounting instead of reusing Ethereum burn, recipient, adjustment, or capacity claims.

Stages: Gas & Fees

ERC-1967 defines storage slots for a proxy's implementation, beacon, and admin information. Tools can resolve supported proxies and show the code they delegate to. Discover actual upgrade authority and source verification separately; standard slots do not establish safe code or universal explorer support.

Stages: Infrastructure

ERC-2535 lets a diamond route function calls to multiple facet contracts at one address. Facet composition and any upgrade authority must be inspected for that deployment. The pattern does not remove transaction gas limits or make a diamond safe or necessarily upgradeable.

Stages: Infrastructure

EIP-4844 introduced Type 3 blob transactions so rollups can post data using a separate blob-fee market. This can lower data costs, but the end-user fee depends on the rollup, execution costs, demand and its pricing policy. Show a current network-specific estimate rather than a fixed dollar price or savings guarantee.

Stages: Gas & Fees

ERC-5202 identifies blueprint bytecode that stores initialization code for later deployment. The blueprint is not a callable application. A deployment action needs a compatible factory or tool, and the resulting instance has its own address, initialization, and control policy.

Stages: Infrastructure

ERC-7201 defines named storage namespaces and their location formula. Correct implementations can reduce storage-collision risk, while developer tools can explain the checks performed. A namespace check alone does not prove that an upgrade is safe.

Stages: Infrastructure

MIP-3 changes how Monad prices memory-heavy transactions. Show a Monad-aware fee estimate and surface simulation failures before signing. Memory is shared across calls under an 8 MiB cap, so linear pricing does not guarantee a lower fee or successful execution.

Stages: Gas & Fees

Monad's asynchronous execution is a protocol-level separation between consensus and execution. Consensus can agree on the ordered transactions without executing them first, while execution runs in a separate, slightly lagged lane. Nodes may speculatively execute a Proposed block before it finalizes, but consuming that data is optional, so a receipt or execution outcome and finality are separate product states.

Stages: Status & Confirmation

Monad executes transactions in parallel by default while preserving the serial semantics of a linearly ordered block. The execution system checks dependencies and merges state updates in block order, so parallel execution is not a user-controlled ordering feature. A feed's arrival order does not prove execution order, and network capacity does not promise a result or latency for one consumer.

Stages: Executing Transactions, Status & Confirmation