Lighter and infrastructure developer Axiom have opened an Ethereum-compatible development network to selected developer cohorts. It connects smart contracts to Lighter’s trading engine and is configured for one-second blocks. But it uses test markets and a development settlement chain, not a demonstrated production route for trading with real funds.
- Contracts can query Lighter Core data and submit, modify, or cancel orders.
- The listed EVM block time is one second; Core order instructions execute separately.
- The devnet uses mocked proofs and a private chain instead of Ethereum.
- Historical Core reads and the full asset-recovery mechanism are not yet available.
Smart contracts connect to Lighter’s trading engine
Axiom’s Yi Sun announced the release in an Oct. 16 post. The network combines a new instance of Lighter EVM, an Ethereum-compatible environment, with Lighter Core, which handles order matching and risk management. Core includes test markets and an order book for developers.
The connection lets developers build applications that interact with trading infrastructure, rather than limiting contracts to other EVM-based applications. A built-in read precompile gives contracts a direct way to query specified Core data, including accounts, balances, positions, orders, and market information.
Contracts can also send instructions to place, modify, or cancel Core orders through asynchronous writes. Core handles these instructions separately from the contract call. Axiom says they execute in seconds. Developers can then use the read interface to check an order’s status.
The devnet supports deposits from its development L1, transfers between Lighter EVM and Core, and withdrawals back to the development L1. Axiom says the network could support applications such as fast funding services, vaults, and request-for-quote platforms, which solicit prices for trades.
These are development features, not evidence of live trading with real funds. The network uses test markets and a development L1, and the available launch details do not show that it supports real funds or live markets.
Ethereum tools, with development-network limits
Lighter’s documentation lists support for the standard Ethereum JSON-RPC interface and tools such as Foundry, Hardhat, Viem, and Ethers. Developers can use familiar tools to connect and test, though support does not guarantee that every tool or workflow will work without adjustments.
The configuration lists ETH for gas, a maximum block gas limit of 17 million, a one-second EVM block time, and chain ID 19, 529. The Core identifier, 300 on the devnet, is used when signing Core transactions. Safe wallet contracts, Multicall3, and Permit2 are among the third-party contracts listed at launch.
Those compatibility details do not make the network production-ready. Lighter’s developer documentation states: “the devnet version uses mocked ZK proofs for L1 finalization.” That means the devnet uses test mechanisms instead of the zero-knowledge proofs needed to finalize activity on a layer-1 network. It does not show the intended proof-verification path working from end to end.
The documentation lists two other limitations. The permissionless escape hatch, a mechanism intended to let users recover assets if normal processing fails, is not fully functional. Core data queries also work only at the latest block. Support for earlier blocks is planned for a future update.
The planned Ethereum settlement design is still ahead
Axiom describes a planned architecture in which OpenVM verifies Lighter EVM execution, while Lighter Core continues to use its existing custom zero-knowledge circuits. An aggregation system would combine proofs from both environments into one proof for verification on Ethereum. Axiom also says the two rollups use records of state changes to reduce the amount of data they publish on Ethereum.
That planned design differs from the current devnet setup. The devnet settles to a development L1, where a privately deployed chain stands in for Ethereum as the settlement and data-availability layer. The private chain is not Ethereum, and the mocked proofs mean the devnet does not demonstrate the complete planned settlement process.
Axiom has not given dates for replacing the mocked proofs, completing the recovery mechanism, or adding historical Core reads. The launch materials also provide no security, performance, or reliability results from independent testing.
Access is rolling out in cohorts
Axiom says it is onboarding developers in cohorts so teams can respond quickly to issues. Broader access is planned in the coming weeks, but the company has not announced a specific date, cohort size, or selection criteria.
Developers can consult Lighter’s public documentation and bridge-contract code on GitHub, then apply by emailing [email protected]. They can also send feedback to the team or through Lighter’s EVM Discord channel.
Key questions about Lighter’s EVM devnet
-
What can developers build?
Contracts can read Core account and market data, manage orders, and transfer assets between Lighter EVM and Core. Axiom also names vaults, fast funding services, and request-for-quote platforms as potential uses.
-
Does a one-second block mean an order executes in one second?
No. One second is the listed EVM block time. Axiom says asynchronous Core order instructions execute in seconds. These are separate measures.
-
Does the devnet support real funds or live trading?
The launch details describe test markets and a development L1, not a production trading venue. They do not show that real funds or live markets are supported.
-
Can contracts read historical Core data?
Not yet. Reads work only at the latest block. Support for earlier blocks is planned, but no date has been given.
-
When will broader access open?
Axiom says broader access is planned for the coming weeks, but it has not announced a specific date or promised universal access.
The devnet gives developers a way to test applications that combine EVM contracts with Lighter’s trading engine. Its usefulness will depend on the integration and on how the proof, recovery, and data-access limitations are resolved before production use.
