[REQUEST] Support restoring accounts using Trust Wallet Core's Ed25519 implementation

[Juanma0x]

Restoring a Polkadot account from a private key generated by wallets using Trust Wallet Core's Ed25519 implementation (e.g., Trust Wallet, Crypto.com, etc.) is technically complex.

This creates a barrier for non-technical users trying to migrate to Polkadot-native wallets.

I kindly request adding support for Ed25519 signature used by Trust Wallet Core to Polkadot-JS apps when restoring Polkadot accounts from the main Trust Wallet Core account's mnemonic phrase.

[arifyyyyyy]

🔥 bullish

[SmartLedger123]

I’ve run into this problem as well when trying to restore a Polkadot account from Trust Wallet, and it can get messy since the Ed25519 implementation isn’t directly compatible with Polkadot-JS. For non-technical users, this feels almost impossible without extra tools. It reminds me of the issues with CapCutMODAPK, where things break because you’re working with a version or method that isn’t officially supported. Until Polkadot-JS adds native support for Trust Wallet Core’s Ed25519, the only workaround I found was using an intermediate tool to convert the key format before importing. It’s not ideal, but it works if you really need access before full support gets added.

[mouazuaf2330-spec]

Adding support for restoring accounts with Trust Wallet Core’s Ed25519 sounds like a big step for security and reliability. In a similar way, CapCut Premium ensures creators don’t lose access to advanced tools—both focus on giving users a smoother, more trusted experience.