After your contract is ready you can deploy it in the NEAR network for everyone to use it.
Let us guide you on how to use the NEAR CLI to deploy your contract and call its methods.
On this page, we will only cover the basics of NEAR CLI. For more information visit the NEAR CLI documentation page.
Deploying the Contract
Thanks to the
NEAR CLI deploying a contract is as simple as:
- Compiling the contract to wasm (done automatically through
yarn buildin our templates).
- Deploy it into the desired account using the NEAR CLI:
Create an Account and Deploy
# Automatically deploy the wasm in a new account
near dev-deploy <route_to_wasm>
# Get the account name
Deploy in an Existing Account
# login into your account
# deploy the contract
near deploy <accountId> <route_to_wasm>
You can overwrite a contract by deploying another on top of it. In this case, the account's logic will change, but the state will persist
near-cli uses the
testnet network. Define
NEAR_ENV=mainnet to deploy into
Once the contract is deployed to the network, anyone and any other contract (i.e., any other account on NEAR) can interact with it by calling its methods. Furthermore, any transactions involving the contract will also be included in the network's data stream, which means its activity can also be visible to any who listens to particular events.
Considering this, we advise to name methods using
snake_case in all SDKs as this is compatible with the remainder of the NEAR ecosystem which is predominantly comprised of Rust contracts.
Initializing the Contract
If your contract has an initialization method you can call it to
initialize the state. This is not necessary if your contract implements
default values for the state.
# Call the initialization method (`init` in our examples)
near call <contractId> <initMethod> [<args>] --accountId <accountId>
You can initialize your contract during deployment using the
Calling the Contract
Once your contract is deployed you can interact with it right away using NEAR CLI.
View methods are those that perform read-only operations. Calling these methods is free, and do not require to specify which account is being used to make the call:
near view <contractId> <methodName>
View methods have by default 200 TGAS for execution
Change methods are those that perform both read and write operations. For these methods we do need to specify the account being used to make the call, since that account will expend GAS in the call.
near call <contractId> <methodName> <jsonArgs> --accountId <yourAccount> [--deposit <amount>] [--gas <GAS>]