Layer 2 networks run transactions outside Ethereum mainnet and settle them on Ethereum. Users pay a fraction of mainnet fees and get faster confirmations, while the chain inherits much of Ethereum's security. Today most users, trading volume and new applications on EVM chains live on layer 2s, so building there is usually the default, not an extra.
Optimistic and ZK Rollups
Most layer 2s are rollups. Optimistic rollups such as Arbitrum, Optimism and Base assume transactions are valid unless challenged, which is why withdrawals to Ethereum take about a week without a fast bridge. ZK rollups such as zkSync prove every batch with a validity proof, so withdrawals can finalise faster, at the cost of more complex infrastructure and sometimes small differences from Ethereum behaviour.
Chains We Work With
- Arbitrum: large DeFi ecosystem; Orbit for app-specific chains.
- Optimism and the OP Stack that many chains are built on.
- Base: OP Stack chain with a large consumer user base.
- zkSync: ZK rollup with native account abstraction.
- Polygon: Polygon PoS, widely used for payments and consumer apps.
What We Build
- Multi-chain deployments of your contracts with identical addresses and consistent configuration, see smart contract development.
- Porting existing dApps from mainnet or other chains, including the chain-specific differences that break naive ports.
- Fee handling: accurate gas estimation including the data fee each rollup charges for posting to Ethereum.
- Bridging and withdrawals: canonical bridges, fast bridges and the user experience around waiting times. See cross-chain bridges.
- Gasless and smart account flows, which are cheap on layer 2. See account abstraction.
Frequently Asked Questions
Which layer 2 should we choose?
Start from where your users and liquidity are, then weigh fees, withdrawal times, tooling and any EVM differences. Many products deploy on several layer 2s.
Do our Solidity contracts work unchanged?
On EVM-equivalent rollups such as Arbitrum, Optimism and Base, almost always. On zkSync, some details differ, so contracts are tested on the target chain.
Can we launch our own chain?
Yes, with frameworks such as the OP Stack or Arbitrum Orbit. It only pays off with enough activity, so we look at that first.
Who owns the code?
Ownership of the source code is set out in the contract, and the code can be fully yours, including documentation and tests.
Build on Layer 2
Tell us what you are building and who uses it. We will help you choose the chains and build an application that is fast and cheap for your users.
Book a free call about layer 2 development
Arbitrum Development: dApps, Stylus and Orbit Chains
Arbitrum development: deploy and port dApps on Arbitrum One and Nova, write contracts in Rust with Stylus, and evaluate Orbit chains. Fees, bridging, pitfalls.
Base Development: Consumer dApps on Coinbase's Layer 2
Base development: consumer dApps, payments and smart wallets on Coinbase's OP Stack layer 2. Onboarding, gasless flows, fees and multi-chain deployment.
Cross-Chain Bridge Integration: Assets and Messages
Cross-chain bridge integration: canonical bridges, fast liquidity bridges, CCTP for native USDC and messaging protocols. Security, monitoring and UX.
Optimism Development: OP Mainnet and OP Stack Chains
Optimism development: dApps on OP Mainnet and other OP Stack chains, the Superchain, fault proofs, fees and withdrawals, and when your own chain makes sense.
Polygon Development: dApps, Payments and Tokens
Polygon development: dApps, stablecoin payments and tokens on Polygon PoS, with bridging, fee handling and multi-chain deployment alongside other layer 2s.
zkSync Development: ZK Rollup With Native Account Abstraction
zkSync development: dApps on a ZK rollup with native account abstraction and built-in paymasters. Compiler and deployment differences, fees and withdrawals.