🤖
LNS Documentation
search
Ctrlk
  • 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 Proposalschevron-right
    • 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 Registrarchevron-right
    • DNS Registrar
  • Contract Developer Guide
    • Resolving Names On-chain
    • Writing a Resolver
    • Writing a Registrar
    • LNS Support Chatarrow-up-right-from-square
gitbookPowered by GitBook
block-quoteOn this pagechevron-down
githubEdit

ENS Improvement Proposals

Standards documentation describing the ENS protocol

ENSIP-1: ENSchevron-rightENSIP-2: Initial Hash Registrarchevron-rightENSIP-3: Reverse Resolutionchevron-rightENSIP-4: Support for contract ABIschevron-rightENSIP-5: Text Recordschevron-rightENSIP-6: DNS-in-ENSchevron-rightENSIP-7: Contenthash fieldchevron-rightENSIP-8: Interface Discoverychevron-rightENSIP-9: Multichain Address Resolutionchevron-rightENSIP-10: Wildcard Resolutionchevron-rightENSIP-11: EVM compatible Chain Address Resolutionchevron-rightENSIP-12: Avatar Text Recordschevron-right
PreviousBug Bounty Programchevron-leftNextENSIP-1: ENSchevron-right

Last updated 3 years ago