A repository for NEAR Enhancement Proposals (NEPs), defining the NEAR Protocol's core specifications, APIs, and smart contract standards.
NEPs (NEAR Enhancement Proposals) is the official repository for the specifications and standards of the NEAR Protocol blockchain. It defines the core protocol rules, smart contract interfaces (like token standards), APIs, and the governance process for proposing changes. It serves as the authoritative source for developers building on or interacting with the NEAR network.
Blockchain core developers, smart contract developers on NEAR, protocol engineers, and contributors involved in NEAR's governance and standardization processes.
It provides a single, structured, and community-vetted source of truth for NEAR's technical standards, ensuring compatibility and reducing fragmentation. The transparent proposal process allows for collaborative evolution of the protocol.
The Near Enhancement Proposals repository
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Hosts all core NEAR protocol specifications and standards in one repository, ensuring ecosystem-wide consistency, as evidenced by the structured NEP table and governance workflow.
Includes finalized standards like NEP-141 for fungible tokens and NEP-171 for NFTs, providing clear, community-vetted interfaces for interoperable smart contract development.
Follows a documented workflow from forum discussions to pull requests and finalization, per NEP-0001, ensuring open community consensus and accountability.
Continuously updated with new proposals for features like stateless validation and resharding, showing ongoing development and adaptation to technological advances.
Requires multiple steps including forum posts and formal pull requests, which can delay implementation and deter casual or urgent contributions.
Standards are specific to NEAR Protocol, with no built-in guidance for cross-chain interoperability or comparisons with other blockchain ecosystems.
Proposals are dense and assume prior knowledge, lacking beginner-friendly explanations or practical code examples, making onboarding challenging.