NEAR Protocol is a proof-of-stake layer-1 blockchain built around two ideas: scale by splitting the network into shards, and make accounts easier for ordinary people to use. Its mainnet launched in 2020. The native token, NEAR, pays transaction fees, is staked to secure the network and pays for data storage on chain. The project's own site, near.org, and the NEAR documentation are the primary references.
A Short History
NEAR was founded by Illia Polosukhin and Alexander Skidanov. Polosukhin previously worked at Google and is one of the co-authors of the 2017 research paper that introduced the transformer architecture used in modern AI models. Skidanov was an engineer at the database company MemSQL.
The mainnet genesis block was produced in April 2020. For the first months the network ran in a restricted mode, and in October 2020 token transfers were enabled and control passed to community validators. The non-profit NEAR Foundation, based in Switzerland, supports development and ecosystem funding.
How Sharding Works on NEAR
On most blockchains, every validator processes every transaction. That is simple and secure, but it caps capacity at what a single machine can handle. Sharding splits the workload into parallel groups, called shards, so that the network as a whole can process more.
NEAR's sharding design is called Nightshade, described in the Nightshade paper. The key points are:
- The chain still produces one block at a time, so users and applications see a single blockchain.
- Each block contains a "chunk" from every shard. A chunk holds that shard's transactions.
- Validators are assigned to shards, so no single validator has to process everything.
- The number of shards can be increased as demand grows.
Sharding was rolled out in stages. Later upgrades moved toward stateless validation, where most validators check chunks without storing the full state of a shard. That lowers the hardware needed to take part.
Sharding has a cost. A transaction that touches contracts on different shards is processed asynchronously, over more than one block. Developers have to design for that, which is different from Ethereum, where a transaction either fully succeeds or fully fails in a single step.
Speed and Fees
NEAR produces blocks roughly every second or faster, and transactions reach finality within a few seconds under normal conditions. Fees are based on the computation used, measured in gas, and a simple transfer usually costs a fraction of a cent.
A share of every transaction fee is burned. A portion of the fee from a contract call can also be paid to the contract itself, which gives developers a small income from usage.
The burn does not mean supply is shrinking. NEAR also issues new tokens as staking rewards, so total supply depends on the balance between issuance and burn. The issuance rate is set by the protocol and can be changed by validator governance.
The Account Model
NEAR accounts are one of its clearest differences from Ethereum.
- Named accounts: an account can have a readable name such as alice.near instead of a long hexadecimal string. This is part of the protocol, not an add-on service.
- Access keys: one account can have several keys. A full-access key can do anything. A function-call key can only call specific methods on a specific contract, so an app can be given limited rights without holding the main key.
- Storage staking: an account or contract must hold NEAR in proportion to the data it stores on chain. The tokens are freed when the data is deleted.
Smart Contracts and Aurora
NEAR contracts compile to WebAssembly and are mostly written in Rust. A JavaScript and TypeScript SDK is also available, which lowers the barrier for web developers.
Aurora is an Ethereum-compatible environment that runs as a contract on NEAR. It lets teams deploy Solidity code and use Ethereum wallets while settling on NEAR.
Bridges and Chain Abstraction
The Rainbow Bridge, launched in 2021, connected NEAR and Ethereum using light clients on each side instead of a custodian that holds the funds. Like all bridges, it depends on smart contracts and should be treated as a point of risk, not as risk-free. Bridge options change over time, so check the current NEAR documentation before moving assets.
In recent years the project has focused on what it calls chain abstraction: tools that let one NEAR account sign transactions on other blockchains, so that users do not have to manage a separate wallet for each chain. NEAR has also positioned itself as infrastructure for AI applications and agents.
Risks to Understand
- Competition: NEAR competes with Ethereum and its Layer 2 networks, Solana and other fast chains for developers and liquidity.
- Ecosystem size: NEAR's DeFi activity is smaller than that of the largest chains, which can mean thinner liquidity.
- Inflation: staking rewards add new supply. Holders who do not stake are diluted.
- Complexity: asynchronous cross-shard calls make some contract designs harder to get right.
- Volatility: NEAR has fallen sharply from its past highs during market downturns.
Common Mistakes
Sending tokens to a mistyped named account is hard to reverse, as on any blockchain. Deleting a full-access key without a backup can lock an account for good. Users also sometimes confuse NEAR held on Aurora with NEAR on the main network. They sit in different environments and need a bridge to move between them.
Nothing in this article is financial advice.
Key NEAR Facts
- Mainnet genesis: April 2020
- Founders: Illia Polosukhin and Alexander Skidanov
- Consensus: proof of stake
- Scaling: Nightshade sharding
- Contract languages: Rust, JavaScript and TypeScript
- Supply: no fixed cap
Track on CoinMarketGuy
The NEAR Protocol price page shows the live price, market cap, supply and chart. To compare NEAR with another asset or with a fiat currency, use the converter. The homepage shows total crypto market cap and the Fear and Greed reading.