Documentation

/openapi.json post /networkinfo Queries the current state of node network connections. This includes information about active peers, transmitted data, known producers, etc.

/openapi.json post /nextlightclientblock Returns the next light client block.

/openapi.json post /query This module allows you to make generic requests to the network. The RpcQueryRequest struct takes in a BlockReference and a QueryRequest. The BlockReference enum allows you to

/openapi.json post /sendtx Sends transaction. Returns the guaranteed execution status and the results the blockchain can provide at the moment.

/openapi.json post /status Requests the status of the connected RPC node. This includes information about sync status, nearcore node version, protocol version, the current set of validators, etc.

/openapi.json post /tx Queries status of a transaction by hash and returns the final transaction result.

/openapi.json post /txstatus Queries status of a transaction by hash, returning the final transaction result and details of all receipts.

/openapi.json post /validators Queries active validators on the network. Returns details and the state of validation on the blockchain.

Remember to make your callbacks private In NEAR, your contract can call a function from another contract, and then schedule a callback to handle its result. The callback function needs to be "public"

Enable users to login with their social accounts (Google, GitHub, etc.) Privy is a third-party service that allows users to login using their email or social accounts (Google, Facebook, Twitter, etc).

Reduce contract size and create reproducible builds that users can verify against the deployed code. In this page, we will explore strategies for reducing the size of smart contracts on NEAR. This is

Learn how to retrieve the genesis and current protocol configurations using the NEAR RPC API. The RPC API enables you to retrieve the current genesis and protocol configuration. Quick Reference | Meth

Overview of tools and methods for interacting with the NEAR Protocol. NEAR Protocol provides multiple ways to interact with the network — from low-level JSON-RPC calls to visual explorers and wallets.

Avoid predictable randomness vulnerabilities When writing smart contracts in NEAR you have access to a random seed that enables you to create random numbers/strings within your contract. This random s

Track finalized native NEAR deposits through blocks, chunks, and receipt outcomes. Native NEAR deposits can arrive as direct transfers or as transfers generated by contract calls. Both are detected th

Explore NEAR contracts deployed across projects. List of contracts of various projects deployed on NEAR. This list is not exhaustive and is meant to be a reference for developers and users [!NOTE] Fin

Return attached NEAR tokens to the original user when a cross-contract call fails. When your contract sends attached NEAR tokens in a cross-contract call and that call fails, the tokens return to your

Require a deposit-capable access key for sensitive smart contract methods. NEAR accounts can have two types of access keys: Full-access keys have complete control over the account, including the abili

List of public RPC endpoints for the NEAR Protocol. NEAR Protocol exposes a JSON-RPC API for interacting with the network. You can use any of the providers below or run your own node. RPC Providers Fa

Learn how to run a localnet on NEAR. Now that we understand what a localnet is, let's walk through the complete workflow of running it and testing it with a simple smart contract and a frontend applic

Explore NEAR Protocol's runtime system, including core runtime operations, cross-contract calls, action and data receipts, and state management. The runtime applies NEAR's execution rules to transacti

The Rust SDK for building smart contracts. NEAR's only official smart-contract SDK is near-sdk-rs, the NEAR SDK for Rust. It provides APIs for contract state, serialization, cross-contract calls, and

Lets test our contract in a realistic sandbox environment. In the previous section, we went through the contract's code, analyzing how it worked. Now, we need to test it and make sure it works as expe

Learn how to create, sign, and send transactions on NEAR protocol, including transaction structure, actions, and best practices for integration. You can send a transfer on NEAR using NEAR CLI or an AP

Learn how contract serialize data for function calls and storage. Smart contracts need to be able to communicate complex data in a simple way, while also reading and storing such data into their state

Set up a NEAR account to be securely controlled via MPC by deriving a public key and adding it as an access key. One of the powerful features of the NEAR Protocol is its flexible access keys architect

Learn how to sign transactions across multiple blockchains. Chain signatures enable NEAR accounts, including smart contracts, to sign and execute transactions across many blockchain protocols. This un

Learn the main security risks in NEAR smart contracts and review them before deployment. Smart contracts handle assets and shared state in an adversarial environment. A secure contract must protect it

Learn how to build social features on NEAR - profiles, posts, follows, likes and notifications - using SocialDB (social.near) and the near-social-js SDK. SocialDB is a smart contract deployed at socia

Validator selection, delegation, withdrawal availability, and staking-pool custody. NEAR delegation uses staking-pool contracts to manage delegated funds and distribute rewards. For an exchange, this