NEAR Protocol near

NEAR Protocol is a proof-of-stake blockchain and developer platform for building decentralized applications and smart contracts. Its design separates a blockchain layer from a runtime layer, so execution rules can evolve independently from consensus, networking, and sharding. The native asset is NEAR (Ⓝ).

NEAR uses an account-based model with human-readable named accounts such as alice.near, implicit accounts, and Ethereum-compatible accounts. Accounts can hold contracts and multiple access keys with distinct permissions, enabling safer delegated or limited-function access.

The protocol is intended to make Web3 application development and use more approachable: official docs describe Rust/WASM contracts, community SDKs for JavaScript/TypeScript, Python, and Go, frontend tooling, testnet faucets, and command-line scaffolding. NEAR also supports asynchronous contract calls and cross-contract receipts.

NEAR's current platform positioning extends beyond a single chain: its account and signing model is documented as able to control accounts on other chains, while the core protocol remains a sharded PoS network for applications, assets, and data.

General-purpose blockchains have historically faced a tradeoff between decentralization, throughput, low fees, and a usable developer experience. A single execution path can become a bottleneck as application demand grows, while complicated key/address models and expensive transactions make onboarding difficult.

NEAR addresses scalability by partitioning state and execution across shards while maintaining one logical protocol. It addresses usability with named accounts, permissioned access keys, asynchronous execution, low-cost storage/transaction accounting, Rust-first tooling, and community language SDKs.

Energy use is another concern for blockchain infrastructure. NEAR uses proof-of-stake rather than proof-of-work, and the NEAR Foundation has published climate-neutrality/carbon-accounting commitments and joined the Ethereum Climate Platform. These are sustainability initiatives and should not be read as a guarantee that every use of the broader ecosystem has zero environmental impact.

Every account belongs to a shard, and the account's balance, staking balance, contract code, contract storage, and access keys are kept together. NEAR partitions its state trie between shards to distribute load. The runtime processes transactions and receipts without needing to know the global shard layout; the blockchain layer routes receipts to the destination shard.

NEAR's execution model is asynchronous. A user transaction creates actions and receipts; contract calls can produce further receipts and callbacks. This message-passing design lets cross-contract work proceed across shards while preserving a single account/state model for developers.

Validators secure the network through proof-of-stake. NEAR holders can delegate tokens to validators; staking secures transaction processing and rewards are paid in NEAR. NEAR is also the unit used to price computation, transaction fees, and storage, and it can transfer value between accounts and applications.

For builders, a standard Rust workflow uses cargo near to scaffold, test, compile to WebAssembly, and deploy contracts; the official quickstart demonstrates a complete auction contract on testnet. Contracts may be written in other languages that compile to WebAssembly, with community SDKs available for JavaScript/TypeScript, Python, and Go.