I received an 8 RTC community payout at the human-readable miner ID martinextrabox-netizen:
- Transaction: ba021e20b027dd165d5e3eea9bb1f7a0
- Sender: founder_community
- Current balance endpoint reports: 8.0 RTC
The current wallet setup guide correctly explains that a miner ID can receive RTC but cannot submit POST /wallet/transfer/signed; signed transfers require an Ed25519-backed RTC... wallet.
What is the supported, ownership-preserving path to move this existing balance into a new signed wallet so it can be used with the official wRTC bridge?
Would the project prefer one of these flows?
- An authenticated migration/claim from the GitHub-linked miner ID to a new public RTC... address.
- An admin-assisted transfer after proof of ownership of the GitHub account and payout transaction.
- A direct bridge request from the legacy miner ID to a user-provided Solana public address.
I will provide only public destination addresses and will never post a seed phrase or private key.
I received an 8 RTC community payout at the human-readable miner ID martinextrabox-netizen:
The current wallet setup guide correctly explains that a miner ID can receive RTC but cannot submit POST /wallet/transfer/signed; signed transfers require an Ed25519-backed RTC... wallet.
What is the supported, ownership-preserving path to move this existing balance into a new signed wallet so it can be used with the official wRTC bridge?
Would the project prefer one of these flows?
I will provide only public destination addresses and will never post a seed phrase or private key.