Workshop Notes: Non-Transferable NFT standards

[bumblefudge]

• NTNFT, Account-Bound, Soul-bound
• Reqs from KYCDAO use case that came out of Near NTNFT WG

• Burn (holder-initiated)
• Revoke (issuer-initiated)
• Send to trash (doesn’t remove from supply on EVM but does on Tezos!)
• Metadata –
  • Can link out: Image, Credential, Ticket usecases
  • Status property (revoked, invalid)
  • Can only issuer update?
  • Could contain DIDs or external addresses, controllers/controlled, etc

• Practice <> Specs : OpenZeppelin implementation has an NTNFT variant that doesn’t remove transfer() func, it PAUSES it (per open-ended governance by issuer)
• EIP logistics?
  • 1238 almost officially stale; @TimDaub wrote an EIP two weeks ago telling people to use 165 properly
  • Revocation could be an extension-EIP that requires 721 that DOESN’T implement transfer()
  • NEP already underway from NEAR community - NEP + EIP4973 --> CAIP baybee

[TimDaub]

• NEP already underway from NEAR community - NEP + EIP4973 --> CAIP baybee

interesting! Would you mind sharing a link @bumblefudge, I'm interested in taking a look.

• 1238 almost officially stale; @TimDaub wrote an EIP two weeks ago telling people to use 165 properly

😆 ERC165 FTW!

[bumblefudge]

NB @nembal @alftom

[nembal]

Hi @TimDaub here you go:
https://gov.near.org/t/non-transferable-nft-standard/18227

made by @blackghost1987 and I