NEAR Protocol

P2P Protocol

A sharded Layer-1 blockchain (Nightshade sharding) designed for usability and developer accessibility, with human-readable account names and a focus on onboarding non-crypto-native users. Governed by the NEAR Foundation.

Foundation
Links
Visit Website Suggest an edit

Details

License MIT/Apache-2.0 dual — confirmed via nearcore's licenses/LICENSE-MIT and licenses/LICENSE-APACHE (the repo keeps its license files in a licenses/ subfolder rather than root).
Dev Status 🟢 Active
Owner NEAR Foundation, plus a broad open-source nearcore contributor base.
Governing Body NEAR Foundation (non-profit).
Country Switzerland (NEAR Foundation is Swiss-registered, same jurisdiction pattern as several other L1 foundations in this batch)
Start Year 2020
Stack Rust.
Funding NEAR Foundation grants; also historically raised via token sale.
Last Investigated Aug 23, 2026

Use Case Domains

Platform Evolution & Sovereignty

P2P Protocol Attributes

Origins Sharded, developer/usability-focused L1 (Nightshade sharding), aiming to reduce onboarding friction (human-readable accounts, no seed-phrase-only UX) versus earlier L1s.
Database N/A conventional DB; JSON-RPC for node queries.
Query Language JSON-RPC.
Data Formats Borsh binary serialization.
Collaborative Live Editing N/A
Rich Text Editing N/A
Mobile Support Via third-party wallets (NEAR Wallet, Meteor, etc.) and dApp frontends.
Web Support Via third-party wallets and dApp frontends.
Native Apps Node software ships as binaries.
Terms Free, open-source (MIT/Apache-2.0 dual, confirmed); network gas fees paid to validators.
Funds NEAR Foundation treasury not independently sized this pass.
Based On Novel sharding design; not forked from a prior chain's codebase.
P2P Architecture Validator/node gossip network; Nightshade shards transaction processing across multiple shard chains coordinated by a beacon-chain-like mechanism.
Overlay Network Global, permissionless.
Content Addressing No.
Local-First N/A
E2EE N/A
CRDTs Lib N/A
Byzantine Fault Tolerance Yes — Doomslug (a PoS/BFT-hybrid finality gadget).
Signature Ed25519.
Permissions Permissionless for transacting; validating requires staked NEAR.
Semantic Web Compatibility No.
Smart Contract Yes — WASM-based runtime, contracts commonly written in Rust or AssemblyScript.
Protocol Stack Position Base-layer settlement + execution (Layer 1), sharded.
Asset / Value Embedding Native (NEAR) plus NEP-standard tokens.
Protocol Maturity / Standardization Mature, mainnet since 2020, no formal external standards body.