Awesome

Release notes

Release notes and unreleased changes can be found in the CHANGELOG

Installation

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/near/cargo-near/releases/latest/download/cargo-near-installer.sh | sh

irm https://github.com/near/cargo-near/releases/latest/download/cargo-near-installer.ps1 | iex

npm install cargo-near

cargo install --locked cargo-near

or, install the most recent version from git repository:

$ git clone https://github.com/near/cargo-near
$ cargo install --locked --path cargo-near

Usage

See cargo near --help for a complete list of available commands or run cargo near to dive into interactive mode. Help is also available for each individual command with a --help flag, e.g. cargo near build --help.

cargo near

Starts interactive mode that will allow to explore all the available commands.

Use --teach-me flag if you want to know "how it works".

cargo near --teach-me

Starts an interactive mode with an explanation of the execution of the selected command.

Additionally depends on Git binary being installed, besides cargo.

cargo near new

Initializes a new project skeleton to create a contract from a template.

Example of github workflows configuration, created by cargo near new.

cargo near build

Builds a NEAR smart contract along with its ABI (while in the directory containing contract's Cargo.toml).

Running the above command opens a menu with following variants:

non-reproducible-wasm

Recommended variant for use during local development.

This is a regular build, which behaves much like and is a thin wrapper around a regular cargo build --target wasm32-unknown-unknown --release.

Additional flags for build configuration can be looked up by

cargo near build non-reproducible-wasm --help

if needed.

reproducible-wasm

Recommended variant for the production releases.

This variant runs a reproducible build in a Docker container, which:

1. runs against source code version, committed to git, ignoring any uncommitted changes
2. requires that Cargo.lock of project is created (e.g. via cargo update) and added to git.
   • this enables --locked build by downstream cargo command.
3. will use configuration in [package.metadata.near.reproducible_build] section of contract's Cargo.toml and package.repository field
   • default values for this section can also be found in Cargo.toml of template project, generated by cargo near new

What's a reproducible build in context of NEAR? Why is it needed? Explanation of these points and a step-by-step tutorial is present at SourceScan/verification-guide.

1. available images can be found by this link https://hub.docker.com/r/sourcescan/cargo-near/tags
   • image and image_digest are straightforward to configure:
2. flags of build command, run inside of docker container, can be configured, if needed, by changing container_build_command field
   • base container_build_command for images starting with sourcescan/cargo-near:0.13.0-rust-1.83.0 and after it is ["cargo", "near", "build", "non-reproducible-wasm", "--locked"], where the --locked flag is required
   • base container_build_command for images prior to sourcescan/cargo-near:0.13.0-rust-1.83.0 is ["cargo", "near", "build"]
   • additional flags, if needed, can be looked up on
     • cargo near build non-reproducible-wasm --help for newer/latest images
     • cargo near build --help for older ones
     • running docker run -it sourcescan/cargo-near:0.11.0-rust-1.82.0 (or another specific image) and checking the --help message of exact cargo-near in container may be helpful when in doubt
3. cargo near allows parameterizing build with values of environment variables, present at the time of the build and not present in a contract's source code, by specifying their names in passed_env array
   • supported by sourcescan/cargo-near:0.10.1-rust-1.82.0 image or later images
   • SourceScan/Nearblocks does not support verifying such contracts with additional parameters present in their metadata yet

cargo near abi

Generates NEAR smart contract's ABI (while in the directory containing contract's Cargo.toml).

Once contract is deployed, this will allow you to call a view function __contract_abi to retrieve a ZST-compressed ABI.

cargo near create-dev-account

Guides you through creation of a new NEAR account on testnet.

cargo near deploy

Builds the smart contract (equivalent to cargo near build) and guides you to deploy it to the blockchain.

Similar to build, running the above command opens a menu with following variants:

build-non-reproducible-wasm

This forwards to non-reproducible-wasm variant of build command.

build-reproducible-wasm

This forwards to reproducible-wasm variant of build command.

deploy command from Docker build requires that contract's source code:

1. doesn't have any modified tracked files, any staged changes or any untracked content.
2. has been pushed to remote repository, identified by package.repository.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as below, without any additional terms or conditions.

License

Licensed under either of

• Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
• MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)

at your option.