Documentation

Create a deterministic fungible-token account using a published global contract and initial storage. A deterministic account starts with contract code and initial storage, but no access keys. Its 0s a

Create implicit accounts through transfers and named accounts through parent-account contracts or CreateAccount actions. You can create an account from a key pair or choose a readable name like alice.

Three ways to create and initialize a 0u universal account: relayer-assisted, self-signed bootstrap, and from inside a smart contract, with code and RPC examples. A universal account's address is the

Learn how to perform a basic cross-contract call on NEAR to set and retrieve greetings. This example performs the simplest cross-contract call possible: it calls our Hello NEAR example to set and retr

Contract can interact with other contracts on the network NEAR contracts can interact with other deployed contracts, querying information and executing functions on them through cross-contract calls.

Explore community-built APIs for accessing on-chain data If you are building a decentralized applications, chances are that you will need to query on-chain data. Since building a full indexer is not a

Indexers are constantly listening for transactions and storing them so they can be easily queried. Data Services are constantly listening to the blockchain, processing the transactions and storing the

Learn about Decentralized Autonomous Organizations (DAOs) on NEAR - self-organized groups that coordinate membership, decision-making, and funding through smart contract voting. Decentralized Autonomo

Learn how to interact with decentralized exchanges on NEAR Protocol, including token swapping, liquidity pools, and integration with Ref Finance DEX. A Decentralized Exchange (DEX) is an application t

Learn about W3C-compliant identity resolution on NEAR. This document details how to use the did:near method for decentralized identifiers on the NEAR blockchain, how it complies with W3C DID Core, and

Deploy a contract to the network. 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 cal

Lets deploy our action contract to testnet. In the previous sections, we saw how a simple auction smart contract is implemented, and checked its correctness using sandbox testing. The time has come to

Learn how to deploy your own Liquid Staking Contract on NEAR At its core, the Liquid Staking Contract issues a token that follows the Fungible Token (NEP-141) standard. When you stake NEAR, you don’t

Handle failed cross-contract calls without aborting the cleanup or refund path. A callback runs in its own receipt. If it panics, all state changes made by that callback are reverted, and any later tr

Prevent callers from redeeming the same treasury token more than once by repeating its ID. A treasury can let users burn share tokens to redeem a proportional share of its holdings. If it charges the

Know which account called you, how much gas and tokens were attached, and more. The environment is a set of variables and functions that are available to your smart contract when it is executed. It pr

Learn about epochs in NEAR Protocol, including their duration, role in validator selection, and how they affect network operations and data retention. This section explains the concept of an epoch in

Learn about common error patterns in NEAR protocol integrations and how to handle and troubleshoot issues in your applications. Transaction submission can fail before execution, and accepted transacti

Learn how to integrate NEAR Protocol. NEAR is an open-source, sharded proof-of-stake blockchain with support for smart contracts. | Property | Value / behavior | Reference | | - | - | - | | Native tok

Learn how a factory creates fungible token contracts on sub-accounts using a global contract ID. A factory is a smart contract that creates sub-accounts and deploys contracts onto them. Our factory ex

Prevent transaction observers from profiting by copying or reordering pending actions. A transaction can reveal information before it executes. Validators can inspect transactions available for inclus

Interact with multiple contracts in your frontend. This example showcases how to interact with multiple contracts from a single frontend. The frontend uses @hot-labs/near-connect to connect a wallet a

Secure ftontransfer deposits and ftresolvetransfer refunds in NEP-141 transfer calls. The best practice for implementing a fungible token contract is to use the contract-tools crate. However, if you n

Integrate NEP-141 fungible tokens, including balance queries, storage registration, transfers, and metadata. Fungible tokens on NEAR follow the NEP-141 standard. Each token is implemented as a smart c

Query gas prices for specific blocks or hashes using the NEAR RPC API. The RPC API enables you to query the gas price for a specific block or hash. Quick Reference | Parameter | Type | Description | |

Learn about NEAR's gas system - execution fees that prevent spam and use deterministic gas units with dynamic pricing. This section explains how gas works in the NEAR Protocol, including how it is cal

Send transactions in parallel using access keys with a prepaid gas balance and independent nonce lanes. Gas keys (NEP-611) are access keys designed for sending many transactions in parallel. They were

Deploy a contract once and reuse it across accounts. Global contracts allow contract code to be deployed once and reused across multiple accounts. With regular deployments, each account pays the full

Learn how to handle common data types when interacting with NEAR When calling methods in a contract or receiving results from them, you will need to encode/decode parameters correctly. For this, it is

Learn how Omni Bridge uses Chain Signatures to enable cross-chain transfers. The journey toward truly trustless cross-chain communication took a significant leap forward when the NEAR team created the