Skip to content
This repository was archived by the owner on Oct 22, 2026. It is now read-only.

Add Rootstock network support and hardware wallet derivation paths - #1808

Open
jbokser wants to merge 1 commit into
floating:developfrom
jbokser:feat/rootstock-derivation-paths
Open

jbokser wants to merge 1 commit into
floating:developfrom
jbokser:feat/rootstock-derivation-paths

Conversation

@jbokser

@jbokser jbokser commented Oct 1, 2026

Copy link
Copy Markdown

Add Rootstock network support and hardware wallet derivation paths

Summary

This PR adds Rootstock Mainnet and Testnet as preconfigured networks in Frame and makes Rootstock-specific derivation paths available for hardware wallets.

Rootstock uses dedicated BIP-44 coin types for these paths:

  • Rootstock Mainnet: m/44'/137'/0'/0/<index>
  • Rootstock Testnet: m/44'/37310'/0'/0/<index>

These paths were supported by wallets such as Nifty Wallet and are still used by existing Rootstock accounts.

Motivation

Frame supports several hardware wallet derivation schemes, but users with existing Rootstock accounts could not select the paths needed to derive their addresses. Rootstock users also had to add the networks manually.

Changes

  • Add Rootstock Mainnet (chain ID 30) and Rootstock Testnet (chain ID 31) as preconfigured networks, including their RPC endpoints, explorers, and native currencies.
  • Add a state migration so the networks appear in existing installations without replacing user-configured networks.
  • Add both Rootstock derivation paths to the Ledger, Trezor, and Lattice settings.
  • Add tests for the derivation paths and network migration.

Compatibility

Existing derivation paths and account behavior remain unchanged. The Rootstock networks are initially disabled and can be enabled by the user.

The BIP-44 coin types 137 and 37310 identify derivation paths; they are distinct from Rootstock's network chain IDs 30 and 31.

Add both networks to the default configuration and migrate existing installs.
Expose Rootstock derivation paths for hardware signers and cover them with tests.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant