🤖
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
On this page
  • Abstract
  • Motivation
  • Specification
  • Copyright
Edit on GitHub
  1. ENS Improvement Proposals

ENSIP-11: EVM compatible Chain Address Resolution

Introduces coinType for EVM compatible chains (amending ENSIP9).

PreviousENSIP-10: Wildcard ResolutionNextENSIP-12: Avatar Text Records

Last updated 3 years ago

Author

Makoto Inoue <makoto@ens.domains>

Status

Draft

Submitted

2022-01-13

Abstract

This ENSIP extends , dedicates a range of coin types for EVM compatible chains, and specifies a way to derive EVM chain IDs to the designated coin types.

The dedicated range uses over 0x80000000 (2147483648) which is reserved under ENSIP 9 so there will be no possibility of coin type collision with other non EVM coin types to be added in future. However, some of coin types previously allocated to EVM chain ides will be deprecated.

Motivation

The existing ENSIP 9 relies on the existence of coin types on which was designed to define address encoding type for deterministic wallets. As the majority of EVM compatible chains inherit the same encoding type as Ethereum, it is redundant to keep requesting the addition of EVM compatible chains into SLIP 44. This specification standardises a way to derive coinType based on .

Specification

This specification amends ENSIP 9 to specify that coin types with the most-significant bit set are to be treated as EVM chain IDs. The MSB is reserved in SLIP44 for other purposes relating to HD wallet key derivation, so no coin types exist in this range.

To compute the new coin type for EVM chains, bitwise-OR the chain ID with 0x80000000: 0x80000000 | chainId.

export const convertEVMChainIdToCoinType = (chainId: number) =>{
  return  (0x80000000 | chainId) >>> 0
}

And to reverse the operation, bitwise-AND the cointType with 0x7fffffff: 0x7fffffff & coinType.

export const convertCoinTypeToEVMChainId = (coinType: number) =>{
  return  (0x7fffffff & coinType) >> 0
}

Implementation

Example

To compute the new coin type for EVM chains, call convertEVMChainIdToCoinType(chainId)

const encoder = require('@ensdomains/address-encoder')
>  encoder.convertEVMChainIdToCoinType(61)
2147483709
> encoder.convertCoinTypeToEVMChainId(2147483709)
61

You can also use existing functions formatsByName and formatsByCoinType to derive these chain IDs

> encoder.formatsByName['XDAI']
{
 coinType: 2147483748,
 decoder: [Function (anonymous)],
 encoder: [Function (anonymous)],
 name: 'XDAI'
}
> encoder.formatsByCoinType[2147483748]
{
 coinType: 2147483748,
 decoder: [Function (anonymous)],
 encoder: [Function (anonymous)],
 name: 'XDAI'
}

Exceptions

The following EVM chains are the exception to this standard.

  • AVAX = AVAX has multiple chain address formats, and only c chain is EVM compatible

  • RSK = RSK has its own additional validation

They will continue using coinType defined at SLIP44

Backwards Compatibility

The following EVM compatible cointypes existed before introducing this new standard.

  • NRG

  • POA

  • TT

  • CELO

  • CLO

  • TOMO

  • EWT

  • THETA

  • GO

  • FTM

  • XDAI

  • ETC

When you display them for backward compatibility purposes, append _LEGACY to the cointype and make them read only.

Copyright

An implementation of this interface is provided in the repository.

Copyright and related rights waived via .

ENSIP 9 (multichain address resolution)
SLIP44
Chain ID
ensdomains/address-encoder
CC0