# Standards **URL:** https://gov.near.org/c/dev/standards/29.md [Latest](https://gov.near.org/latest.md) · [Categories](https://gov.near.org/categories.md) · [Tags](https://gov.near.org/tags.md) --- ## [About the Standards category](https://gov.near.org/t/about-the-standards-category/436)
**Author:** [@jlwaugh](https://gov.near.org/u/jlwaugh)\ **Replies:** 0\ **Last updated:** [January 21, 2021, 2:49pm UTC](https://gov.near.org/t/about-the-standards-category/436 "2021-01-21T14:49:47Z")
This category is for discussion about standards ~ various common interfaces and APIs, which are used by smart contract developers on NEAR. Collaborate on GitHub: --- ## [Building the TypeScript resolver for NEP-641 (currently listed as TBD)](https://gov.near.org/t/building-the-typescript-resolver-for-nep-641-currently-listed-as-tbd/42479)
**Author:** [@jatinsahijwani](https://gov.near.org/u/jatinsahijwani)\ **Replies:** 13\ **Last updated:** [September 3, 2026, 6:26am UTC](https://gov.near.org/t/building-the-typescript-resolver-for-nep-641-currently-listed-as-tbd/42479 "2026-09-03T06:26:50Z")
NEP-641 is Final, and the last line of its Reference Implementation section reads: TypeScript resolver (wallet-selector / NEAR Connect integration): TBD. I would like to take that on. Starting this week, building in … --- ## [\[PROPOSAL\] Complement and eventual replacement of X.509 digital certificates -Standards / NEP](https://gov.near.org/t/proposal-complement-and-eventual-replacement-of-x-509-digital-certificates-standards-nep/36787)
**Author:** [@vaceituno](https://gov.near.org/u/vaceituno)\ **Replies:** 2\ **Last updated:** [December 11, 2023, 3:11pm UTC](https://gov.near.org/t/proposal-complement-and-eventual-replacement-of-x-509-digital-certificates-standards-nep/36787 "2023-12-11T15:11:46Z")
Thanks to a previous discussion about use of custom NFT for mutual authentication, I am focusing on the complement or replacement of digital certificates. The NEP509 I would like to put forward is explained here: Summar… --- ## [Customized Non-fungible tokens for VPN operations](https://gov.near.org/t/customized-non-fungible-tokens-for-vpn-operations/35982)
**Author:** [@vaceituno](https://gov.near.org/u/vaceituno)\ **Replies:** 0\ **Last updated:** [August 25, 2023, 3:44pm UTC](https://gov.near.org/t/customized-non-fungible-tokens-for-vpn-operations/35982 "2023-08-25T15:44:58Z")
Custom Non-fungible-tokens are a great alternative to package the following functionality necessary for a VPN service: Authentication: Being in control of an signed NFT-like token (or Rich Online Digital Token,or RODiT… --- ## [Multi-Token Standard Discussion](https://gov.near.org/t/multi-token-standard-discussion/2917)
**Author:** [@zcstarr](https://gov.near.org/u/zcstarr)\ **Replies:** 22\ **Last updated:** [April 25, 2023, 10:39pm UTC](https://gov.near.org/t/multi-token-standard-discussion/2917 "2023-04-25T22:39:33Z")
Hi all I wanted to start a conversation and gather interest for developing a multi-token standard contract. This would be very similar to the NFT and FT standards that have been developed. The principle motivation would … --- ## [Non-Transferable NFT Standard](https://gov.near.org/t/non-transferable-nft-standard/18227)
**Author:** [@blackghost1987](https://gov.near.org/u/blackghost1987)\ **Replies:** 12\ **Last updated:** [March 31, 2023, 4:38am UTC](https://gov.near.org/t/non-transferable-nft-standard/18227 "2023-03-31T04:38:38Z")
Goal: Create a standardised way of constructing NFTs that are not meant to be transfered. These non-transferable NFTs (NTNFTs, or “soulbound” NFTs) should be bound to an owner address on minting, so the owner would never… --- ## [Discussion of Soulbound Token Standard](https://gov.near.org/t/discussion-of-soulbound-token-standard/31223)
**Author:** [@JasperTimm](https://gov.near.org/u/JasperTimm)\ **Replies:** 9\ **Last updated:** [February 6, 2023, 3:30pm UTC](https://gov.near.org/t/discussion-of-soulbound-token-standard/31223 "2023-02-06T15:30:38Z")
Hi all, Creating this topic to coordinate efforts on a NEP for Soulbound Tokens (previously non-transferable NFTs). Hoping to form a (rough) consensus here on some key decisions before continuing with the NEP itself. H… --- ## [Official Linkdrop Standard](https://gov.near.org/t/official-linkdrop-standard/32463)
**Author:** [@Ben](https://gov.near.org/u/Ben)\ **Replies:** 12\ **Last updated:** [January 24, 2023, 2:34pm UTC](https://gov.near.org/t/official-linkdrop-standard/32463 "2023-01-24T14:34:33Z")
We’re proposing a new standard for Linkdrops! Huge thanks to Ken Miyachi for helping out with this standard! Summary A standard interface for linkdrops that support $NEAR, fungible tokens, non-fungible tokens, and is ex… --- ## [Personal Smart Contract Whitepaper](https://gov.near.org/t/personal-smart-contract-whitepaper/32327)
**Author:** [@Neafiol](https://gov.near.org/u/Neafiol)\ **Replies:** 4\ **Last updated:** [January 16, 2023, 10:43am UTC](https://gov.near.org/t/personal-smart-contract-whitepaper/32327 "2023-01-16T10:43:43Z")
At NEAR, every user can upload a smart contract to his or her account. This smart contract will be able to use dApps on behalf of the user. We designed a universal personal smart contract on top of which many services ca… --- ## [\[HELP WANTED\] Bounty Metadata](https://gov.near.org/t/help-wanted-bounty-metadata/32022)
**Author:** [@minorityprogrammers](https://gov.near.org/u/minorityprogrammers)\ **Replies:** 0\ **Last updated:** [December 14, 2022, 3:50pm UTC](https://gov.near.org/t/help-wanted-bounty-metadata/32022 "2022-12-14T15:50:11Z")
Hello everybody, in the DAO builder group we have been exploring the idea of creating a chain agnostic DAO bounty metadata standard. Please refer to this document to help draft such a specification out. Also we are a… --- ## [\[DRAFT\] Non Fungible Token Burn Standard](https://gov.near.org/t/draft-non-fungible-token-burn-standard/28859)
**Author:** [@marmajfoundation](https://gov.near.org/u/marmajfoundation)\ **Replies:** 1\ **Last updated:** [December 14, 2022, 12:22pm UTC](https://gov.near.org/t/draft-non-fungible-token-burn-standard/28859 "2022-12-14T12:22:16Z")
What is a NEAR Enhancement Proposal (NEP)? A NEP is a design document for providing information to the NEAR community or describing a new feature for the NEAR protocol or Smart Contract standards. The NEP should provide … --- ## [\[DISCUSSION\] Push A Bridgeable NFT Chain Agnostic Standard](https://gov.near.org/t/discussion-push-a-bridgeable-nft-chain-agnostic-standard/30425)
**Author:** [@minorityprogrammers](https://gov.near.org/u/minorityprogrammers)\ **Replies:** 0\ **Last updated:** [October 14, 2022, 6:00pm UTC](https://gov.near.org/t/discussion-push-a-bridgeable-nft-chain-agnostic-standard/30425 "2022-10-14T18:00:35Z")
Hello everybody, after talking to some key bridge builders it has come to our attention that NEAR NFT implementation is complex or not intuitively compatible with other NFT standards outlined in protocols like Ethereum c… --- ## [\[DRAFT\] xNFTs](https://gov.near.org/t/draft-xnfts/30562)
**Author:** [@minorityprogrammers](https://gov.near.org/u/minorityprogrammers)\ **Replies:** 3\ **Last updated:** [December 14, 2022, 12:44am UTC](https://gov.near.org/t/draft-xnfts/30562 "2022-12-14T00:44:21Z")
Summary React xNFT is a framework for building “executable NFTs” that can be rendered in react. Motivation xNFT is already chain agnostic and has been of interest to multiple stakeholders on NEAR. Additionally the rise … --- ## [Rentable NFTs \[DRAFT\]](https://gov.near.org/t/rentable-nfts-draft/31977)
**Author:** [@minorityprogrammers](https://gov.near.org/u/minorityprogrammers)\ **Replies:** 0\ **Last updated:** [December 13, 2022, 2:02am UTC](https://gov.near.org/t/rentable-nfts-draft/31977 "2022-12-13T02:02:24Z")
NEP Title Author Discussions To Status Type Category Created SupersededBy TBD Rentable NFTs Shot shot@banyan.gg Rentable NFTs \[DRAFT\] DRAFT Standards Track Contract 12/12/2022 Summary This is a NEP Extension … --- ## [Few and Far NFT Specification](https://gov.near.org/t/few-and-far-nft-specification/30828)
**Author:** [@lachlanglen](https://gov.near.org/u/lachlanglen)\ **Replies:** 18\ **Last updated:** [November 18, 2022, 5:52pm UTC](https://gov.near.org/t/few-and-far-nft-specification/30828 "2022-11-18T17:52:35Z")
Hi NEAR Community, We wanted to share some technical specifics on the Few and Far NFT Specification, a fully backwards-compatible extension of NEP-171. The below information can also be found on Medium here. At Few and… --- ## [Injected Wallet Standard](https://gov.near.org/t/injected-wallet-standard/25683)
**Author:** [@lewis-sqa](https://gov.near.org/u/lewis-sqa)\ **Replies:** 1\ **Last updated:** [October 20, 2022, 7:18pm UTC](https://gov.near.org/t/injected-wallet-standard/25683 "2022-10-20T19:18:40Z")
Hi everyone, I’d like to get some feedback on a proposal for standardising injected wallets in the NEAR ecosystem: Injected Wallet Standard by lewis-sqa · Pull Request #370 · near/NEPs · GitHub. --- ## [Audio/Video NFTs discussion](https://gov.near.org/t/audio-video-nfts-discussion/18666)
**Author:** [@lachlanglen](https://gov.near.org/u/lachlanglen)\ **Replies:** 4\ **Last updated:** [October 19, 2022, 3:22pm UTC](https://gov.near.org/t/audio-video-nfts-discussion/18666 "2022-10-19T15:22:57Z")
Hi everyone, I know some in this community may have already found their own solutions to these questions, but I’d love to open a discussion and try to come to some consensus on how to support non-image NFT media, so we … --- ## [Bridge Wallet Standard](https://gov.near.org/t/bridge-wallet-standard/25685)
**Author:** [@lewis-sqa](https://gov.near.org/u/lewis-sqa)\ **Replies:** 0\ **Last updated:** [July 26, 2022, 4:14pm UTC](https://gov.near.org/t/bridge-wallet-standard/25685 "2022-07-26T16:14:14Z")
Hi everyone, I’d like to get some feedback on a proposal for standardising bridge wallets (e.g. WalletConnect) in the NEAR ecosystem: Bridge Wallet Standard by lewis-sqa · Pull Request #368 · near/NEPs · GitHub. --- ## [Proposed smart contract interaction for an unified NEAR KYC standard](https://gov.near.org/t/proposed-smart-contract-interaction-for-an-unified-near-kyc-standard/17753)
**Author:** [@Gus](https://gov.near.org/u/Gus)\ **Replies:** 2\ **Last updated:** [April 3, 2022, 1:01am UTC](https://gov.near.org/t/proposed-smart-contract-interaction-for-an-unified-near-kyc-standard/17753 "2022-04-03T01:01:36Z")
Purpose: The main goal of this project is to establish a standard for reusable KYC (for end-users & DAOs) within the greater NEAR ecosystem. The rationale for this is providing KYC as a main building block for DAOs & Da… --- ## [Formal NEP Submission Process](https://gov.near.org/t/formal-nep-submission-process/17058)
**Author:** [@lodge](https://gov.near.org/u/lodge)\ **Replies:** 0\ **Last updated:** [March 21, 2022, 5:44pm UTC](https://gov.near.org/t/formal-nep-submission-process/17058 "2022-03-21T17:44:25Z")
Hey everyone, The NEP submission process has been formalized to feel more like the familiar PEP/BIP/EIP model, with pepperings of RustRFC. This should help us transition the plethora of really awesome ideas floating aro… --- ## [Improving customizable NEAR Contract Standards](https://gov.near.org/t/improving-customizable-near-contract-standards/5649)
**Author:** [@mikedotexe](https://gov.near.org/u/mikedotexe)\ **Replies:** 1\ **Last updated:** [September 14, 2021, 9:28am UTC](https://gov.near.org/t/improving-customizable-near-contract-standards/5649 "2021-09-14T09:28:07Z")
Currently the way NEAR Contract Standards work aren’t as great as they could be. Some thoughts have been noted here: NFT standard: expose minimal usable interface · Issue #542 · near/near-sdk-rs · GitHub NFT example up… --- ## [Standard / convention for structured logging or "events"](https://gov.near.org/t/standard-convention-for-structured-logging-or-events/3809)
**Author:** [@mikedotexe](https://gov.near.org/u/mikedotexe)\ **Replies:** 5\ **Last updated:** [July 27, 2021, 5:39am UTC](https://gov.near.org/t/standard-convention-for-structured-logging-or-events/3809 "2021-07-27T05:39:34Z")
Given recent discussions with The Graph and @zcstarr on the multi-token standard, I feel like this is a good time to discuss structured logging. This can also be thought of as “events” that can be picked up by indexers. … --- ## [NFT Standard Discussion](https://gov.near.org/t/nft-standard-discussion/853)
**Author:** [@mattlockyer](https://gov.near.org/u/mattlockyer)\ **Replies:** 13\ **Last updated:** [March 9, 2021, 6:04pm UTC](https://gov.near.org/t/nft-standard-discussion/853 "2021-03-09T18:04:46Z")
Why? We have a lot of questions floating around various groups and stakeholders about the NFT standard. I would like to align those discussions somewhere official, here on the forum, to establish the following things: G…