Account Based RSK Addresses

RSK Addresses incorporate an optional blockchain identifier (also known as chainId). If the chainId is not present, it is assumed the address refers to the RSK main network.

How to get an address

Check out the already integrated wallets or integrate your wallet.

Derivation path info

When using BIP-44-compatible wallet software, you will need to specify a derivation path.

RSK Mainnet: m/44'/137'/0'/0/N
RSK Testnet: m/44'/37310'/0'/0/N
  • The first level of the hierarchy is for purpose. This is always 44', as per the BIP44 specification.
  • The second level of the hierarchy is for the registered coin type.
    • For RSK Mainnet, this should be 137', as per the SLIP-44 specification.
    • For RSK Testnet, this should be 37310', as per the RSKIP-57 specification.
  • The final level of the hierarchy is for index: Addresses are numbered from index 0 in sequentially increasing manner. This number is used as child index in BIP32 derivation. Public derivation is used at this level.

Checksum

RSK implements EIP-1191 to protect users from losing funds by mixing addresses of different Ethereum based networks.

In this document, you can find out how to apply the checksum and validate an address. This EIP is also supported by Web3 and hardware wallets.

ChainId

To avoid a replay attack by using an already-signed transaction, originally broadcast in “network A”, and subsequently replayed it in “network B”, the EVM-based networks use chainId as part of the transaction properties. All chainIds can be found at chainid.network.

RSK Mainnet: 30
RSK Testnet: 31

See EIP-155 for more information.

We strongly recommend the following:

  1. Add the chainId in the RSK integration (and every time you integrate EVM-based blockchains)
  2. Use a different account to hold value for each blockchain (do not share the same account among RSK, ETH, and others)