Arbitrum Nitro

Conduit allows you to launch a rollup in a fraction of the time with Arbitrum Nitro (often referred to as Arbitrum Orbit when referencing rollups).

Arbitrum Nitro is the one of the premiere rollup implementations on Ethereum. Their technology boasts the usual benefits of rollups, like dedicated compute for your application, in addition to:

• 10-100x cheaper fees than Ethereum Mainnet (go even cheaper with data availability committee support)
• Interoperability with Mainnet through trustless bridging and fraud proofs
• Close Ethereum Compatibility, so you can use the same workflows and tooling
• Stylus, which will allow you to write smart contracts in a more performant VM with Rust, C++, or other languages that can compile to WASM. These contracts can interoperate synchronously with the EVM.

Supported JSON RPC Methods

Arbitrum implements the same JSON RPC methods supported by go-ethereum with minimal changes to their upstream geth methods. The supported JSON RPC methods can be found here.

FAQ

How do I withdraw/bridge tokens?

Please see our guide and use of the arbitrum sdk here.

Does Arbitrum on Conduit support Stylus?

Arbitrum Stylus is enabled by default for new Conduit Rollups. If you’re unsure whether Stylus is active on your rollup, please reach out to our Support Team. Please also see the excellent arbitrum stylus docs here.

How do I deploy Stylus Contracts to my Arbitrum Orbit stack?

If Stylus is not yet enabled on your rollup, follow Arbitrum’s hello world guide. You’ll then be able to deploy to your stack with:

cargo stylus deploy --endpoint=https://nitrorpc-[your_conduit_stack_name-here].t.conduit.xyz --private-key=[your_private_key_here]

Are there any public audits?

Arbitrum audits can be found here.

For Celestia based Nitro rollups, you can find the audit here.

Why does my block explorer show a gas limit of 1,125,899,906,842,624 instead of the expected 32 million?

The gas limit shown on an Arbitrum block is an artificially large number (1,125,899,906,842,624) and represents the maximum theoretical gas limit to account for variations in Layer 1 (L1) data posting costs. This value allows for flexibility in L1 transaction costs but does not reflect the actual execution capacity of the block. In practice, the effective gas limit for transaction execution on Arbitrum is capped at 32 million gas per block. You can find more details on this in the Arbitrum documentation.