Developer Quick Guide¶
If you build on any EVM chain, you can build on New L1. Solidity, the toolchain (Foundry, Hardhat, Remix), and the SDKs (ethers.js, viem, web3.py) all work unmodified against a node’s standard JSON-RPC endpoint.
Devnet stage
There is no public testnet or mainnet endpoint, no faucet, and no hosted explorer yet. Today you develop against a local devnet built from the client source. Network parameters on these pages reflect the current devnet client and may change before a public launch.
Getting Started¶
There is no endpoint to connect to yet; Network Information is where one will be published. Until then, read the differences below and work through Migrating from BSC if you’re bringing an existing app, since most of what it lists is decided in your submission path rather than in your contracts.
What’s Different from a Typical EVM Chain¶
Five things account for nearly every surprise.
| What | Why it matters | Details |
|---|---|---|
| You pay for your declared gas limit | Unused gas is never refunded, so SDK gas padding is money spent, and receipts report gasUsed equal to the limit. |
Migrating from BSC |
latest means executed, not ordered |
Ordering and execution are decoupled; state reads resolve to the executed tip, and an explicit block number that hasn’t executed yet returns -38004 rather than stale data. |
Async Execution |
| No global mempool | Transactions route straight to the current and next block producer. No txpool_*, no public pending-transaction feed, and replace-by-fee only affects the pools holding the transaction. |
JSON-RPC Endpoint |
No eth_getProof |
State is committed with an LtHash accumulator, not a Merkle-Patricia trie, so there is no trie proof to serve. Anything proof-based needs a different design. | Async Execution |
| 200 ms blocks | block.number advances about five times a second, and block.timestamp (still whole seconds) repeats across consecutive blocks. Block-count and timestamp math both need review. |
Migrating from BSC |
Coming from BSC specifically? Migrating from BSC is the full checklist, including what carries over unchanged: the gas asset, the Parlia staking and governance contracts at their original addresses, and the parlia_* RPC methods.
What You Get That You Don’t Have Elsewhere¶
None of these are required to run a standard EVM app. They are additive, and they are the reason to build here.
| Capability | What it gives you |
|---|---|
| Transaction pre-confirmation | A validator-signed inclusion signal in ~20 ms, long before the block lands. Advisory and revocable, so never treat it as finality. |
| Native account abstraction | The 0x76 transaction envelope: atomic call batches, session and admin keys, passkey (WebAuthn/P256) signing, and gas sponsorship, with no bundler and no EntryPoint contract. |
| Multi-Lane | Governance-configured reserved gas quota per traffic class, so latency-sensitive flows aren’t crowded out by unrelated load. |
| Shielded pool | An opt-in native system contract for private transfers, alongside ordinary transparent ones. |
| BLS fast finality | Fast finality for transaction ordering. The execution result becomes final only after a later block records it and that block also finalizes. |
Reference¶
- Examples collects runnable demos: watch a pre-confirmation land, find the current leader, drive load, run the end-to-end scenario suite.
- Transaction Types documents the two native EIP-2718 types (
0x76account abstraction,0x77shielded), their fields, how to sign them, and what trips people up. - JSON-RPC Endpoint covers endpoints, transports, and how the API surface maps onto Geth’s.
- New L1 API List lists every method that goes beyond or differs from Geth, with parameters and
curlexamples. - Network Information holds the network identifiers, protocol parameters, and endpoints.
- System Contracts lists every system contract and precompile address, including the BSC carry-overs and the New L1–original ones.
- Governance walks the propose → vote → queue → execute lifecycle that controls protocol parameters.
- FAQ
Tooling¶
Standard EVM tooling connects with no chain-specific client:
Two caveats when you wire them up: set a real maxPriorityFeePerGas (the base fee is pinned to zero, so the tip is the entire price), and don’t pad gas limits (you pay for what you declare). Hosted explorers, indexers, and faucets are not available at this stage.