NEAR Contract Standards

Smart Contract Standard

Suite of Rust-based smart contract standards for the NEAR Protocol, including NEP-141 (fungible tokens), NEP-171 (NFTs), NEP-145 (storage management), and NEP-297 (events), providing interoperable primitives for the NEAR ecosystem.

Foundation
Links
Visit Website See this tool in the graph Suggest an edit

Details

License https://github.com/near/near-sdk-rs
Dev Status 🟢 Active
Dev Status Detail Active
Owner NEAR Protocol / NEAR Foundation
Governing Body NEAR Foundation (NEP standards process)
Country Switzerland (NEAR Foundation HQ)
Start Year 2020
Stack Rust (primary, via near-sdk-rs); JavaScript/TypeScript (via near-sdk-js); AssemblyScript (legacy)
Funding NEAR Foundation grants; NEAR Protocol core team R&D
Last Investigated Mar 9, 2026

Topology view

This tool in the centre and the things it is directly related to. Each line names the kind of relationship.

Topology view: NEAR Contract StandardsThis tool in the centre and the things it is directly related to. Each line names the kind of relationship.NEARContract St…NEAR Protocol (Built on)NEARProtocol

Open in Graph Explorer

Use Case Domains

Platform Evolution & Sovereignty

Affordances

Self-hostable

Smart Contract Standard Attributes

Origins Developed by NEAR Protocol core team and community as the ecosystem grew beyond simple contracts; NEP (NEAR Enhancement Proposal) process mirrors EIP process; designed for NEAR's sharded, account-model runtime with storage-staking economics.
Data Formats JSON for cross-contract calls and event logs (NEP-297 event standard); borsh for efficient state serialization; NEAR account IDs as string types; storage-key prefixed state trees
Terms MIT / Apache 2.0 (near-sdk-rs dual licensed)
Funds Unknown; NEAR Foundation funds ecosystem development broadly but no public figure specific to standards work
Based On ERC-20 / ERC-721 concepts adapted to NEAR's account model and storage-staking economics; NEP-141 is functionally analogous to ERC-20 but NEAR-native
Permissions Permissionless contract deployment by any NEAR account; storage staking required (account must hold NEAR proportional to storage used)
Development Tools near-sdk-rs (Rust SDK), near-sdk-js (JS SDK), NEAR CLI, near-workspaces (integration testing), Pagoda / NEAR developer console
Protocol Maturity / Standardization NEP-141 and NEP-171 are ratified standards; broadly adopted by NEAR ecosystem wallets, DEXes, and marketplaces (Ref Finance, Paras, etc.)
Trust Framework NEAR's account-based model: contracts are named accounts; cross-contract calls are async with callbacks; no built-in reputation layer; storage staking as economic spam prevention
Target Application Domain DeFi, NFTs, gaming, DAOs, social apps (NEAR Social / SocialDB), civic coordination, identity (linkdrop pattern)
Deployment Model Per-account contract deployment; each NEAR account can hold exactly one contract; factory pattern used for multi-instance deployments
Standard Type Token Standard; Interface Standard
Ecosystem NEAR Protocol

Relationships

How this tool connects to other tools and organizations, from relationships reviewed by the OpenHaven data steward. They describe how projects connect, not how good they are.

Built on