Aurora Engine

Aurora Engine implements an Ethereum Virtual Machine (EVM) on the NEAR Protocol. See doc.aurora.dev for additional documentation.

Deployments

Network	Contract ID	Chain ID
Mainnet	aurora	1313161554
Testnet	aurora	1313161555
Local	aurora.test.near	1313161556

Development

Prerequisites

• Node.js (v14+)
• cargo-make

cargo install --force cargo-make

Prerequisites for Development

• Node.js (v14+)
• Docker
• cargo-make

Development

Branches

• master is the current stable branch. It must be ready, anytime, to deployed on chain at a moment's notice.

• develop is our bleeding-edge development branch. In general, kindly target all pull requests to this branch.

Building & Make Commands

Every task with cargo make must have a --profile argument.

The current available profiles are:

• mainnet, suitable for mainnet.
• testnet, suitable for testnet.
• local, suitable for local development.
• custom, suitable for custom environments, see note below.

A custom environment may be required depending on the circumstances. This can be created in the .env folder as custom.env following the structure of the other .env files. See bin/local-custom.env for more details.

Every make most follow the following pattern, though --profile is not required for all such as cleanup:

cargo make [--profile <profile>] <task>

Building the engine and contracts

To build the binaries there are a few commands to do such following the format.

The current available build tasks are:

• default, does not need to be specified, runs build. Requires a --profile argument.
• build, builds all engine smart contract and produces the aurora-<profile>-test.wasm in the bin folder. Requires build-contracts. Requires a --profile argument.
• build-test, builds all the below using test features. Requires a --profile argument.
• build-contracts, builds all the ETH contracts.
• build-docker, builds the aurora-<profile>-test.wasm in the bin folder using docker build environment. The purpose of this task is to produce reproducible binaries.

For example, the following will build the mainnet debug binary:

cargo make --profile mainnet build

Verifying binary hash

To verify that a deployed binary matches the source code, you may want build it reproducibly and then check that their hashes match. The motivation behind that is to prevent malicious code from being deployed.

Run these commands to produce the binary hash:

cargo make --profile <profile> build-docker
shasum -a 256 bin/aurora-<profile>.wasm

Running unit & integration tests

To run tests, there are a few cargo make tasks we can run:

• test, tests the whole cargo workspace and ETH contracts. Requires a --profile argument.
• test-workspace, tests only the cargo workspace.
• test-contracts, tests only the contracts.

For example, the following will test the whole workspace and ETH contracts:

cargo make --profile mainnet test 

Running checks & lints

To run lints and checks, the following tasks are available:

• check, checks the format, clippy and ETH contracts.
• check-contracts, runs yarn lints on the ETH contracts.
• check-fmt, checks the workspace Rust format only.
• check-clippy, checks the Rust workspace with clippy only.

For example the following command will run the checks. profile is not required here:

cargo make check

Cleanup

To clean up the workspace, the following tasks are available:

• clean, cleans all built binaries and ETH contracts.
• clean-cargo, cleans with cargo.
• clean-contracts, cleans the ETH contracts.
• clean-bin, cleans the binaries.

Additionally, there is also but not included in the clean task:

• sweep, sweeps the set amount of days in the ENV, default at 30 days.

For example, the following command will clean everything. profile is not required:

cargo make clean

License

aurora-engine has multiple licenses:

• all crates except engine-test has CCO-1.0 license
• engine-test has GPL-v3 license