Nifter
  • NFTR Overview
  • Basics
    • Getting Started
      • Ethereum Wallet
      • Ether (ETH)
        • Coinbase
        • Transak (Bank & Card)
      • How to Name an NFT
    • Why Name NFTs?
  • NFTR
    • Names + Domains
    • Profiles
    • ERC-6551 Integration
    • Roadmap
    • Name Marketplace
    • NFTR API
    • Golden Tickets
  • Architecture
    • Architecture Overview
    • NFTR DAO Treasury
    • Contracts
    • Under the Hood
    • Frontend
    • API
    • FAQ
  • Miscellaneous
    • Press
    • Acknowledgements
  • Nifter
  • Twitter
  • Medium
  • Discord
  • Sushiswap
Powered by GitBook
On this page

Was this helpful?

  1. NFTR

ERC-6551 Integration

PreviousProfilesNextRoadmap

Last updated 1 year ago

Was this helpful?

From : "Each token bound account is owned by a single ERC-721 token, allowing the token to interact with the blockchain, record transaction history, and own on-chain assets. Control of each token bound account is delegated to the owner of the ERC-721 token, allowing the owner to initiate on-chain actions on behalf of their token."

If ERC-721s (NFTs) are to be so active, they must be simply and uniquely identifiable.

ENS, fundamentally, provides this service to Ethereum wallets.

NFTR, fundamentally, provides this service to NFTs.

As ENS provides limitless value and utility beyond reach/reference, so does NFTR.

ERC-6551's whitepaper