Documentation

Accounts Account ID NEAR Protocol has an account names system. Account ID is similar to a username. Account IDs have to follow the rules. Account ID Rules • minimum length is 2 • maximum length is 64

actioncreationconfig Describes the cost of creating a specific action, Action. It covers the actions up to delegatecost. The fees of newer actions, such as global contract, state init and gas key acti

Actions There are a several action types in Near: ![allow(unused)] fn main() { pub enum Action { CreateAccount(CreateAccountAction), DeployContract(DeployContractAction), FunctionCall(FunctionCallActi

Cross-Contract Call This guide assumes that you have read the Financial Transaction section. Suppose Alice is a calling a function reservetrip(city: String, date: u64) on a smart contract deployed to

Financial Transaction Suppose Alice wants to transfer 100 tokens to Bob. In this case we are talking about native Near Protocol tokens, oppose to user-defined tokens implemented through a smart contra

Fraction A rational number. In code it is a Rational32. In the genesis config and in RPC responses it is a JSON array of two signed 32-bit integers, [numerator, denominator]. For example, [3, 10] mean

Light Client Note: This page is out of date and may contain errors. Do not use it as the only reference when you build a light client. Have any light client implementation reviewed independently befor

Messages All messages sent in the network are of type PeerMessage. A PeerMessage is encoded with Protocol Buffers , using the schema in network.proto . Some fields of that schema are bytes fields that

Receipt All cross-contract (we assume that each account lives in its own shard) communication in Near happens through Receipts. Receipts are stateful in a sense that they serve not only as messages be

Refunds When execution of a receipt fails or there is some unused amount of prepaid gas left after a function call, the Runtime generates refund receipts. The are 2 types of refunds: • Refunds for the

Runtime crate Runtime crate encapsulates the logic of how transactions and receipts should be handled. If it encounters a smart contract call within a transaction or a receipt it calls near-vm-runner,

RuntimeConfig The structure that holds the parameters of the runtime, mostly economics. It is not part of genesis. Each nearcore release contains the runtime config for every protocol version (core/pa

RuntimeFeesConfig Economic parameters for runtime actionreceiptcreationconfig type: Fee Describes the cost of creating an action receipt, ActionReceipt, excluding the actual cost of actions. datarecei

Selecting Chunk and Block Producers Background Note: this section describes the Simple Nightshade design as of March 2021. Since stateless validation (protocol version 69), block producers no longer t

StorageUsageConfig Describes how the storage that an account uses is counted for storage staking. numbytesaccount type: u64 Number of bytes counted for the account record, including rounding up for th

VMConfig Config of wasm operations. The fields from maxgasburnt to maxtotalloglength belong to the limit config. In the JSON view they are nested under the limitconfig key of wasmconfig. extcosts type

POST /block Returns block details for given height or hash Request body (application/json): - id (string): JSON-RPC request id. Auto-populated; can be any string. - jsonrpc (string): JSON-RPC protocol

POST /blockeffects Returns changes in block for given block height or hash over all transactions for all the types. Includes changes like accounttouched, accesskeytouched, datatouched, contractcodetou

POST /broadcasttxasync [Deprecated] Sends a transaction and immediately returns transaction hash. Consider using sendtx instead. Request body (application/json): - id (string): JSON-RPC request id. Au

POST /broadcasttxcommit [Deprecated] Sends a transaction and waits until transaction is fully complete. (Has a 10 second timeout). Consider using sendtx instead. Request body (application/json): - id

POST /changes Returns changes for a given account, contract or contract code for given block height or hash. Request body (application/json): - id (string): JSON-RPC request id. Auto-populated; can be

POST /chunk Returns details of a specific chunk. You can run a block details query to get a valid chunk hash. Request body (application/json): - id (string): JSON-RPC request id. Auto-populated; can b

POST /clientconfig Queries client node configuration Request body (application/json): - id (string): JSON-RPC request id. Auto-populated; can be any string. - jsonrpc (string): JSON-RPC protocol versi

POST /EXPERIMENTALcallfunction Calls a view function on a contract and returns the result. Request body (application/json): - id (string): JSON-RPC request id. Auto-populated; can be any string. - jso

POST /EXPERIMENTALchanges [Deprecated] Returns changes for a given account, contract or contract code for given block height or hash. Consider using changes instead. Request body (application/json): -

POST /EXPERIMENTALchangesinblock [Deprecated] Returns changes in block for given block height or hash over all transactions for all the types. Includes changes like accounttouched, accesskeytouched, d

POST /EXPERIMENTALcongestionlevel Queries the congestion level of a shard. More info about congestion here Request body (application/json): - id (string): JSON-RPC request id. Auto-populated; can be a

POST /EXPERIMENTALgenesisconfig [Deprecated] Get initial state and parameters for the genesis block. Consider genesisconfig instead. Request body (application/json): - id (string): JSON-RPC request id

POST /EXPERIMENTALlightclientblockproof Returns the proofs for a transaction execution. Request body (application/json): - id (string): JSON-RPC request id. Auto-populated; can be any string. - jsonrp

POST /EXPERIMENTALlightclientproof Returns the proofs for a transaction execution. Request body (application/json): - id (string): JSON-RPC request id. Auto-populated; can be any string. - jsonrpc (st