Compile from source

1. Dependencies

Install Rust:

curl https://sh.rustup.rs -sSf | sh
rustup component add clippy-preview
rustup default nightly

Install development dependencies (OS-dependent):

Ubuntu:

sudo apt install cmake clang

2. Clone repository

We would need to copy the entire repository:

git clone https://github.com/near/nearcore
cd nearcore

3. Compile and run

Navigate to the root of the repository, and run:

cargo run --package neard --bin neard -- init
cargo run --package neard --bin neard -- run

This will setup a local chain with init and will run the node.

You can now check the status of the node with http tool (brew install httpie or apt install httpie or configure CURL for POST requests) via RPC:

http get http://localhost:3030/status
http post http://localhost:3030/ method=query jsonrpc=2.0 id=1 params:='["account/test.near", ""]'

See full list of RPC endpoints here

Unfortunately, transactions needs to be signed and encoded in base64, which is hard to do from the command line. Use near-cli tool to manage keys and send transactions (npm install -g near-cli).

Code Style

We follow style enforced by rustfmt. Therefore before submitting code make sure you ran it on your code. Also, please make sure you have our rustfmt config in your ~/.config/rustfmt/ directory.

If you are using CLion IDE you can configure it to run rustfmt automatically every time your file is saved to the disk. Go to Preferences→Languages & Frameworks→Rust→Rustfmt and check Run rustfmt on Save.

Testing

To run NEARCore node in the testing mode, for example to test it or for development of near-api-js or near-cli you can use scripts that sets up special tests-only local testnet:

./scripts/start_localnet.py

This sets up a new single node testnet, with predetermined private key of the validator and turns on "fast" mode of block production to make development and testing easy.

Logging

Many times in development of the node it’s useful to see detailed logs about what is happening. neard binary has --verbose mode to show more details about what is happening:

cargo run --package neard --bin neard -- --verbose=true run

You can also use the RUST_LOG environment variable, with env_logger semantics to override the log level for specific targets. RUST_LOG can also be used in integration tests which spawn runnable apps.

If you want to change what is logged in verbose mode / non-verbose mode, for example to add new target (e.g. info!(target: "my target", "hello")), modify neard/src/main.rs in init_logging function.

Operations

This section describes how to prepare releases and publish docker files for NEAR core client.

Build docker container

To build docker image run from the root:

make docker-nearcore

This will build an image with nearcore name.

Publishing Docker files

To publish docker image, use

sudo docker tag nearcore <your username>/mynearcore:<version>
sudo docker push <your username>/mynearcore:<version>

sudo docker tag nearcore <your username>/mynearcore:latest
sudo docker push <your username>/mynearcore:latest

Official image is published at nearprotocol/nearcore

Got a question?

Ask it on StackOverflow!

# cargo clean
# time RUSTFLAGS= RUSTC_WRAPPER= cargo build -p neard --release
real    2m13.773s
user    44m49.204s
sys     1m22.583s
# touch */*/*/*.rs
# time RUSTFLAGS= RUSTC_WRAPPER= cargo build -p neard --release
real    0m38.021s
user    9m37.045s
sys     0m5.302s

# cargo clean
# time RUSTFLAGS='-C lto=off -C link-arg=-fuse-ld=lld' RUSTC_WRAPPER= cargo build -p neard --release
real    1m50.802s
user    36m50.251s
sys     1m19.069s
# touch */*/*/*.rs
# time RUSTFLAGS='-C lto=off -C link-arg=-fuse-ld=lld' RUSTC_WRAPPER= cargo build -p neard --release
real    0m28.951s
user    6m56.670s
sys     0m4.307s

# cargo clean
# time RUSTFLAGS='-C lto=off -C link-arg=-fuse-ld=lld -Zshare-generics=y' RUSTC_WRAPPER= cargo build -p neard --release
real    1m42.999s
user    33m31.341s
sys     1m25.773s
# touch */*/*/*.rs
# time RUSTFLAGS='-C lto=off -C link-arg=-fuse-ld=lld -Zshare-generics=y' RUSTC_WRAPPER= cargo build -p neard --release
real    0m23.501s
user    4m30.597s
sys     0m3.804s

# cargo clean
# rm -rf ~/.cache/sccache/
# time RUSTFLAGS='-C lto=off -C link-arg=-fuse-ld=lld -Zshare-generics=y' RUSTC_WRAPPER=sccache cargo build -p neard --release
real    2m6.452s
user    3m24.797s
sys     0m30.919s
# cargo clean
# time RUSTFLAGS='-C lto=off -C link-arg=-fuse-ld=lld -Zshare-generics=y' RUSTC_WRAPPER=sccache cargo build -p neard --release
real    0m24.292s
user    3m3.627s
sys     0m27.619s

# cargo clean
# time RUSTFLAGS='-C lto=off -C link-arg=-fuse-ld=lld -Zshare-generics=y -C inline-threshold=25 -C debuginfo=2' RUSTC_WRAPPER=sccache cargo build -p neard --release
real    1m50.521s
user    3m39.398s
sys     0m32.069s

# cargo clean
# time RUSTFLAGS='-C lto=off -C link-arg=-fuse-ld=lld -Zshare-generics=y' RUSTC_WRAPPER=sccache cargo build -p neard
real    1m18.198s
user    4m35.409s
sys     0m32.220s

Follow guide at https://github.com/mozilla/sccache to install sccache.
If you are unable to install sccache you can remove RUSTC_WRAPPER option.

lld

For ubuntu use:

sudo apt update
sudo apt install lld

For other systems follow link at https://lld.llvm.org/
If you can’t install lld, you can remove option -C link-arg=-fuse-ld=lld.

Clion/Intellij with Rust plugin

Currently Rust plugin doesn’t support passing environment variables to cargo.
Your best option is to either modify Cargo.toml or replace
$HOME/.cargo/bin/cargo with a bash script, which sets proper
environment variables.

Command line – bash/zsh

You can add the following lines to .bashrc, .bash_profile, .zshrc depending on your OS and terminal that you use.

export RUSTFLAGS="-C lto=off -C link-arg=-fuse-ld=lld -Zshare-generics=y -C codegen-units=6 -C debuginfo=0"
export RUSTC_WRAPPER="sccache"
export SCCACHE_CACHE_SIZE="30G"