Curious about a word? Tap a dotted term for its meaning.

Layer 1 / NETWORK PROFILE

NEAR Protocol

NEAR CMC #18 in the snapshot

A sharded application chain with named accounts, access keys and WebAssembly contracts.

Profile checked Asset ranks captured 14 Nov 2026Snapshot & methodology ↗

01 / THE PURPOSE

What is NEAR Protocol for?

NEAR aims to make application accounts and interactions easier to manage while splitting network work across shards. Its surrounding ecosystem also offers cross-chain signing and intent-based services.

02 / THE ARCHITECTURE

Three questions about the machinery.

01

How does it agree?

Consensus & security

Proof-of-stake validators secure the chain. Sharding divides state and processing work, while the protocol coordinates a shared history rather than treating every shard as an unrelated network.

02

Where do instructions run?

Execution model

Contracts typically compile from Rust to WebAssembly. Cross-contract work can use asynchronous receipts and callbacks; applications must account for intermediate outcomes and failure handling.

03

What is the token for?

NEAR in the system

NEAR pays computation and storage-related costs and is used for staking. An application may sponsor a user’s gas, but the underlying resource cost still exists.

03 / THE DESIGN CHOICES

What comes with the design?

Each architecture makes choices about security, performance, coordination, and who can participate.

04 / IN PRACTICE

Follow one use.

Illustrative: an app grants a session key permission to call selected contract functions. That permission is narrower than the full-access key controlling the entire account.

05 / CHECK THE EXPLANATION

Sources & snapshot.

Network descriptions use the references below. The CoinMarketCap snapshot determines which assets are in scope and their captured rank; it does not assess the quality of a network.

Profile checked 14 Nov 2026. Network designs and ranked positions can change.