FAQ

How are Virtual Chains different from L2s or L3s?

Virtual Chains are not separate chains such as L2s or L3s. They are deployed as smart contracts on an existing chain and inherit all of its security and scalability.

This means that they do not require additional infrastructure and are extremely cost efficient.

Besides, they can natively communicate between each other, which means that they offer some customisation options while staying connected to the wider ecosystem.

How do I create an Aurora Virtual Chain?

Aurora Virtual Chains are available through a monthly plan on Aurora Cloud. We have a range of options available to suit your needs.

Get in touch with Aurora and we will advise on the best setup for your use case.

Do I need an engineering team to run an Aurora Virtual Chain?

Absolutely not. The advantage of virtual chains is that they are using the existing infrastructure of the mother chain, in this case Near Protocol. This means that no maintenance is required from the owner of the Virtual Chain.
Besides, the Aurora Cloud Console provides a simple interface to access most of the parameters of the Virtual Chain.

What assets can be bridged to an Aurora Virtual Chain?

As the Aurora Engine is running on Near Protocol, any asset on Near can be automatically bridged to an Aurora Chain.

Besides, ERC-20 tokens on Ethereum can be bridged directly to a virtual chain using the Rainbow Bridge.

A custom widget version of the rainbow bridge can be configured from the Aurora Cloud Console, enabling you to embed the bridge into your application directly.

Has Aurora been audited?

Aurora constantly engage with top tier blockchain security firms to audit existing and new developments.

The full list of audit reports can be found at https://aurora.dev/audits