🤖
LNS Documentation
  • Introduction
  • Terminology
  • Frequently Asked Questions
  • Tokenomics
  • LNS Deployments
  • Registrar Frequently Asked Questions
  • Deploying LNS on a Private Chain
  • DNS Registrar guide
  • Bug Bounty Program
  • ENS Improvement Proposals
    • ENSIP-1: ENS
    • ENSIP-2: Initial Hash Registrar
    • ENSIP-3: Reverse Resolution
    • ENSIP-4: Support for contract ABIs
    • ENSIP-5: Text Records
    • ENSIP-6: DNS-in-ENS
    • ENSIP-7: Contenthash field
    • ENSIP-8: Interface Discovery
    • ENSIP-9: Multichain Address Resolution
    • ENSIP-10: Wildcard Resolution
    • ENSIP-11: EVM compatible Chain Address Resolution
    • ENSIP-12: Avatar Text Records
  • Dapp Developer Guide
    • LNS Enabling your DApp
    • LNS Libraries
    • Working with LNS
    • Resolving Names
    • Managing Names
    • Registering & Renewing Names
    • LNS Front-End Design Guidelines
    • LNS as NFT
  • Contract API Reference
    • Name Processing
    • Registry
    • ReverseRegistrar
    • PublicResolver
    • .bch Permanent Registrar
      • Registrar
      • Controller
    • DNS Registrar
  • Contract Developer Guide
    • Resolving Names On-chain
    • Writing a Resolver
    • Writing a Registrar
    • LNS Support Chat
Powered by GitBook

ENS Improvement Proposals

Standards documentation describing the ENS protocol

PreviousBug Bounty ProgramNextENSIP-1: ENS

Last updated 2 years ago

On this page
Edit on GitHub
ENSIP-1: ENS
ENSIP-2: Initial Hash Registrar
ENSIP-3: Reverse Resolution
ENSIP-4: Support for contract ABIs
ENSIP-5: Text Records
ENSIP-6: DNS-in-ENS
ENSIP-7: Contenthash field
ENSIP-8: Interface Discovery
ENSIP-9: Multichain Address Resolution
ENSIP-10: Wildcard Resolution
ENSIP-11: EVM compatible Chain Address Resolution
ENSIP-12: Avatar Text Records