Tatum Wallets use specific Mnemonic derivation paths per chain. These derivation paths are the same for API, SDKs, and KMS.
Tatum Derivation Paths
//MAINNET BTC: "m/44'/0'/0'/0", LTC: "m/44'/2'/0'/0", ETH: "m/44'/60'/0'/0", DOGE: "m/44'/3'/0'/0", CELO: "m/44'/52752'/0'/0", POLYGON: "m/44'/966'/0'/0", KCS: "m/44'/60'/0'/0", HARMONY: "m/44'/1023'/0'/0", KLAY: "m/44'/8217'/0'/0", BSC: "m/44'/60'/0'/0", BCH: "m/44'/145'/0'/0", TRON: "m/44'/195'/0'/0", EGLD: "m/44'/508'/0'/0'", ALGO: '@TODO - TBD', ADA: "m/1852'/1815'/0'", FLOW: "m/44'/539'/0'/0", NEO: "m/44'/888'/0'/0", SOL: "m/44'/501'/0'/0'", VET: "m/44'/818'/0'/0", XDC: "m/44'/550'/0'/0", XLM: "m/44'/148'/0'", XRP: "m/44'/144'/0'/0", BNB: "m/44'/714'/0'/0", //TESTNET COMMON_TESTNET_DERIVATION_PATH = "m/44'/1'/0'/0"
Additional information is available at the following link.
Good to know
Customers that want to import addresses generated from Tatum API and or KMS should be mindful of other Wallet services like MetaMask using a different derivation path.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article