Skip to content
BSC Twins Hub
← All topics

Learn · 10

New L1 for developers

Transaction types, the transaction lifecycle, RPC differences and storage, for people who build on EVM chains.

Checked against official docs on 2026-10-29

StatusDevnet only. Interfaces and parameters may change before any public launch.

Tools that work unchanged

Solidity, Foundry, Hardhat, Remix, ethers.js, viem and web3.py work against the standard JSON-RPC endpoint. The eth_*, net_* and web3_* methods behave as in Geth.

Transaction types

Type Status
Legacy, EIP-2930, EIP-1559 Supported, as on Ethereum
0x76 account abstraction Batched calls, session and admin keys, passkeys, sponsored gas
0x77 shielded Private transfers and withdrawals with zk-proofs
EIP-4844 blobs (0x03) Rejected
EIP-7702 (0x04) Rejected

The transaction lifecycle

  1. Submit with eth_sendRawTransaction. It is forwarded straight to upcoming block producers. There is no global mempool.
  2. Pool. The transaction is ready if its nonce is next in line, or parked if there is a gap.
  3. Pre-confirmed (optional). It appears in a signed sub-block. This can still be revoked.
  4. Ordered. It has a fixed position in a block.
  5. Executed. A receipt exists. Until then, receipt calls return error -38004, so retry.
  6. Order-finalized. Two-thirds of validators have voted on the block.
  7. Execution-finalized. The result is committed in a later finalized block. Wait for this before irreversible actions.

Unconfirmed transactions expire from the pool after 3 hours.

Habits to change

  • You pay the gas limit you declare, not the gas used. Receipts show the declared limit. Don't pad gas limits.
  • The base fee is zero. Set a real priority tip, because a zero tip is rejected.
  • latest means executed, not just ordered. Use finalized or safe for consensus-level reads.
  • About 5 blocks per second. Recalculate anything that counts blocks, and expect several blocks to share a timestamp.
  • block.prevrandao is not randomness on New L1.

Storage and its trade-offs

State is a flat key-value store committed with a lattice hash (LtHash), not a Merkle-Patricia trie. Updates cost the same regardless of state size.

Confirmed by official docsBecause there is no trie, eth_getProof, snap sync and whole-state debug methods are unavailable. Bridges and light clients rely on BLS finality votes and full nodes instead.

New L1-specific RPC

Methods in the newl1_ namespace cover pre-confirmation streams, account-abstraction key state, Multi-Lane configuration, pool status and system-transaction receipts. See the official JSON-RPC reference for the exact names.

System contracts

Validator set, slashing, rewards, staking (StakeHub), governance (GovHub, Governor, Timelock, govBNB), LaneRegistry, account-abstraction precompiles and the shielded pool live at fixed system addresses. These are listed on the official system contracts page.

Our analysis (unofficial)Start with the official examples page. It walks through finality, live pre-confirmations and gas-limit charging using standard tools.