Documentation

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

Learn how to stake NEAR, delegate to validators, track rewards, and withdraw staked tokens safely. You can delegate NEAR tokens to a validator to help secure the network and earn staking rewards. This

Explore how NEAR smart contracts manage their state. Smart contracts store data in their account's state, which is public on the chain. The storage starts empty until a contract is deployed and the st

Clean up a contract's state. State Cleaner is an extension for NEAR CLI that wipes a contract account's on-chain state without deleting the account, so you can redeploy a fresh contract or free the st

Learn about NEAR Protocol's storage staking mechanism, including costs, storage pricing, attack prevention, and strategies for managing on-chain data storage. NEAR's storage staking is a mechanism tha

Prevent attackers from locking a contract's balance by forcing unbounded state growth. NEAR accounts must maintain a balance proportional to the data they store. If users can grow contract state witho

Wind down a staking pool, pause staking, and help delegators withdraw their tokens. If you are a stake pool owner and want to wind down your validator service, follow these steps to ensure delegators

Design NEAR applications that do not mistake multiple accounts for independent participants. A Sybil attack occurs when one actor creates or controls many accounts to gain extra votes, rewards, reputa

Test an integration on NEAR testnet or in a local sandbox. Use testnet to exercise deposit detection, withdrawal submission, and reconciliation before enabling mainnet operations. [!TIP] Testnet token

Learn how Fungible Tokens (FT) are defined on NEAR Besides the native NEAR token, users have access to a multitude of tokens created by institutions and other users known as fungible tokens. In contra

Learn how Linkdrops are defined on NEAR Linkdrops allow users to distribute assets and onboard people to Web3 apps through a simple web link. They work by storing assets and linking AccessKeys to them

Learn how Non-Fungible Tokens (NFT) are defined on NEAR In contrast with fungible tokens, non-fungible tokens (NFT) are unitary and therefore unique. This makes NFTs ideal to represent ownership of as

Learn how NEAR Drop enables token drops (NEAR, FT, NFT) claimable via private keys. NEAR Drop is a smart contract that allows users to create token drops ($NEAR, Fungible and Non-Fungible Tokens), and

Learn how to get free testnet tokens for development and testing on the NEAR blockchain A faucet provides free testnet tokens for testing and development purposes. There are two testnet faucets: the b