NEAR private key import rejects standard ed25519: format

[GemWalletBot]

NEAR private key import currently expects a hexadecimal key and rejects the standard NEAR ed25519:... format used by other NEAR wallets, showing "Invalid private key". The import should accept the ed25519: prefix, split by :, and base58-decode the key portion so users can import keys exported from other NEAR wallets.

[GemWalletBot]

Implementation note: to accept the standard NEAR format, split the input by :, drop the ed25519 prefix, and base58-decode the remaining key portion. The current path only accepts a hexadecimal key, which is why exports from other NEAR wallets (e.g. NearMobile) fail with "Invalid private key". Reported via the NEAR forum thread; recovery phrase import still works since it does not rely on the private-key format.

[0xh3rman]

fixed in 7bf87e3