In order to make it easy for people to get started using Arbitrum Rollup, we've launched our own hosted Arbitrum Rollup chain hosted on the Rinkeby testnet.
For a general introduction to the Arbitrum Testnet, see our announcement.
For a convenient landing page for all your testnet needs, see our website.
Connecting to the chain
If you're using Metamask, add a custom RPC network to connect to the Arbitrum testnet:
- Network Name: Arbitrum Testnet
- RPC URL: https://rinkeby.arbitrum.io/rpc
- ChainID: 421611
- Symbol: ETH
- Block Explorer URL: https://rinkeby-explorer.arbitrum.io/#/
If you'd like to see your transactions in action, check out our block explorer!
There you'll be able to see all the transactions being executed in Arbitrum and also see exactly how much Ethereum Gas each transaction uses.
Bridging Eth and ERC-20 Tokens
In order to deposit and withdraw Eth or tokens, visit https://bridge.arbitrum.io.
In order to start using the chain, you'll have deposit Eth from Rinkeby so that you can pay for fees in L2. In order to get Rinkeby Eth, use one of the standard faucets from https://faucet.rinkeby.io/
Interacting with the chain
Once you've added the Arbitrum Rinkeby Testnet network to Metamask, you should be able to interact with the Arbitrum chain just like you would with Ethereum.
The are a couple things to note on the Arbitrum chain.
- Arbitrum uses an EIP-1559-like gas auction system so the gas price you list in your transaction is a bid, but the actual price may be lower
- In order to do a ETH transfer through Metamask, you must manually enter a higher gas limit than the default 21,000 gas. 800,000 should work well
- The majority of gas costs paid in the arbitrum chain go to pay for the cost of posting your transaction data to Ethereum
Deploying your contracts
Deploying your contracts onto the Arbitrum testnet is as easy as changing your RPC endpoint to https://rinkeby.arbitrum.io/rpc
For a deeper dive into deploying with truffle see here.
Porting your frontend
Porting your frontend is just as easy as deploying your contracts. Just take your existing frontend and point it at our RPC endpoint after deploying your contract. For more information and code samples see here
All contracts are deployed from https://github.com/OffchainLabs/arbitrum/tree/69c58d6b33c4dfb7d8293ccfdcb1675798201b7e/packages/arb-bridge-eth/contracts
- Main L1 Rollup Contract: 0xFe2c86CF40F89Fe2F726cFBBACEBae631300b50c
- Ethereum Inbox Contract: 0x578BAde599406A8fE3d24Fd7f7211c0911F5B29e
- L1 Gateway Router: 0x70C143928eCfFaf9F5b406f7f4fC28Dc43d68380
- L1 Standard ERC20 Gateway: 0x91169Dbb45e6804743F94609De50D511C437572E
- L1 Custom Gateway: 0x917dc9a69F65dC3082D518192cd3725E1Fa96cA2
- L1 WETH Gateway: 0x81d1a19cf7071732D4313c75dE8DD5b8CF697eFD
- L1 WETH Address: 0xc778417E063141139Fce010982780140Aa0cD5Ab
- L2 Gateway Router: 0x9413AD42910c1eA60c737dB5f58d1C504498a3cD
- L2 Standard ERC20 Gateway: 0x195C107F3F75c4C93Eba7d9a1312F19305d6375f
- L2 Custom Gateway: 0x9b014455AcC2Fe90c52803849d0002aeEC184a06
- L2 WETH Gateway: 0xf94bc045c4E926CC0b34e8D1c41Cd7a043304ac9
- L2 WETH Address: 0xB47e6A5f8b33b3F17603C83a0535A9dcD7E32681