Network profile: Aurora
Does this article need to be translated?
-
Network name
Aurora
-
Token
ETH
-
RPC
-
Chain ID
1313161554
-
Block explorer
-
Website
Aurora is a version of the Ethereum Virtual Machine (EVM) that exists on NEAR Protocol. Although NEAR and Aurora are developed by the same team, Aurora is best conceptualized as a network in its own right due to its EVM compatibility.
Aurora's objective is to function similarly to NEAR itself, just with the key difference that it can be used to host decentralized applications (dapps) and run smart contracts which were originally written on Ethereum. This makes it highly appealing for developers: in their own words, Aurora"provides the Ethereum 1.0 development experience, with layer-2-like speed and scalability." Creating an appealing space for developers means a higher-quality and more diverse ecosystem, which, in turn, draws in users.
In parallel to smoothing the transition for developers, Aurora is also designed to present a relatively flat learning curve for those more familiar with Ethereum, principally through its native token choice. Rather than having its own native token (the token you use to pay gas fees) like many layer 1 chains, Aurora simply uses ETH.
Since it resides on NEAR, Aurora retains many of the former's core features. These include:
- Low transaction costs (gas fees), typically $0.02 per transaction
- Faster transaction finality of <3 seconds
- Carbon neutrality.
Another key feature of Aurora is the fact that is governed by AuroraDAO, a decentralized autonomous organization which votes on high-level matters relating to the network. Governance uses the AURORA token (though, as we mentioned earlier, Aurora's native token for gas fees is ETH).
There's also a membership platform available on Aurora called Aurora+, promising 50 free transactions per month, AURORA staking, and potential governance involvement.
Using Aurora
How do I add Aurora to MetaMask?
Simply follow our instructions for adding networks here. The details you'll need to add it manually, including RPC, chain ID, and token are detailed at the top of this page.
What's the relationship between Aurora and NEAR? Why can't I use NEAR with MetaMask?
Aurora is a version of the Ethereum Virtual Machine that runs on NEAR, and is developed by the NEAR Protocol team.
NEAR, by contrast, is a distinct layer-1 blockchain, completely separate from Ethereum, and so cannot be used with MetaMask (which is only usable with EVM-compatible networks). There is a useful graphic here explaining how Aurora interacts with NEAR for each transaction.
How do I bridge tokens to and from Aurora?
The NEAR Protocol team have built the Rainbow Bridge specifically to support transactions between Ethereum mainnet, Aurora, and NEAR.
To use it, head to the site and connect the MetaMask account you want to use and the Aurora or NEAR address you want to transact with.
Bear in mind that not all transfer directions cost the same. As the Rainbow Bridge FAQs explain:
Transfers between NEAR and Aurora require a single transaction, cost a few cents and happen instantaneously.
Transfers from Ethereum require a single transaction, and happen in about 10 minutes. The cost will be estimated in MetaMask prior to confirming the transaction.
Transfers to Ethereum, however, involve two transactions — the kick-off on Aurora or NEAR, and the finalization on Ethereum. The finalization can take up to 16 hours, and its cost will depend on gas prices at that time, and are therefore unpredictable.
Is ETH on Aurora the same as ETH on Ethereum mainnet?
No.
Although ETH is the native token of both networks, you cannot simply send your ETH from Ethereum mainnet straight to Aurora — it must be bridged first. See the FAQ on bridging immediately above.
Is my public address the same when using Aurora on MetaMask?
Yes.
Since Aurora is EVM-compatible, you can use the same Ethereum address (i.e. the type you have in MetaMask) as an existing MetaMask account.
Once you've added Aurora to MetaMask, notice how your address stays the same even when you switch between networks. This means that even if you send some ETH to your MetaMask and haven't bridged it onto the correct network (one of Ethereum mainnet or Aurora), it will still be retrievable in your MetaMask by just switching to the network it's on.
NEAR has a completely different approach to public addresses.
Does Infura's partnership with NEAR mean I can access NEAR with MetaMask?
The announcement simply means that developers can use Infura to easily access the NEAR blockchain.
Although, by default, MetaMask uses Infura to connect to the blockchain, Infura's compatibility with NEAR does not mean MetaMask does. MetaMask and Infura are different products, and the former can only be used with EVM-compatible networks.
Useful resources
Aurora knowledge base (aimed at users)
Aurora docs (aimed at developers)
Rainbow Bridge (official Ethereum <-> Aurora <-> NEAR bridge developed by NEAR)