This guide explains wallet basics, balance checks, and safe transfer practices for RustChain users.
- In RustChain docs, wallet identity is often represented by
miner_id. - Keep your wallet/miner id consistent across setup, mining, and balance checks.
curl -sk "https://50.28.86.131/wallet/balance?miner_id=YOUR_WALLET_NAME" | jq .Expected response shape:
{
"amount_i64": 0,
"amount_rtc": 0.0,
"miner_id": "YOUR_WALLET_NAME"
}curl -sk https://50.28.86.131/api/miners | jq .If your miner does not appear:
- Wait a few minutes after startup.
- Confirm the same wallet/miner id was used when starting miner.
- Check network reachability to the node.
- Verify URLs before signing transactions.
- Never share private keys or seed phrases.
- Keep a small test transfer habit before large moves.
- Save tx IDs and timestamps for audit/recovery.
The API supports signed transfers:
- Endpoint:
POST /wallet/transfer/signed - Reference examples:
docs/API.md
Only use this when you fully understand signing and key custody.
- Miner may not have completed a reward cycle yet.
- Queried
miner_idmay not match your running miner wallet.
Current docs use curl -k for self-signed TLS:
curl -sk https://50.28.86.131/health- RTC: RustChain native token
- wRTC: wrapped Solana representation
- Official wRTC mint:
12TAdKXxcGf6oCv4rqDz2NkgxjyHq6HQKoxKZYGf5i4X
When reporting wallet issues, include:
miner_idused- command run and output snippet
- timestamp (UTC)
- relevant tx hash (if any)