Self-hosted wallet VPS validation
This guide validates the self-hosted wallet path on a VPS without sending live transactions. It is written for the public Fased wallet model:- self-hosted wallets
local-socket-signer- explicit RPC wiring
- runtime health before wallet-bearing automation
Prerequisites
- Fased is already installed on the VPS
- native signer installed or available
- self-hosted wallet material already created or imported through onboarding or CLI
- chain RPC configured for the wallet role you are validating
Canonical runtime expectation
For unattended self-hosted operation, the wallet path should look like:- wallet entry exists in the runtime registry
local-socket-signeris healthy- RPC is configured for the relevant chain
- wallet appears in the Wallets page and status outputs
Validation flow
1. Check signer health
2. Check wallet visibility
Open the Wallets page or inspect runtime status to confirm:- wallet id
- address
- visible balances
- signer-ready state
3. Confirm chain RPC wiring
The wallet path is not ready for unattended use until chain RPC is set and responsive. Use the runtime and wallet status surfaces to confirm:- Solana readiness
- the configured RPC is responsive
4. Confirm Satcoin-mining-specific expectations when relevant
If the wallet is intended for Satcoin:- it should be a dedicated wallet role
- it should be the singleton
@wallet:miningruntime wallet - mining readiness should pass before any capital deposit or start
Operational rule
Do not treat “wallet exists on disk” as success. Treat the wallet as ready only when all of these are true:- signer is healthy
- wallet is visible in runtime state
- RPC is valid
- sends and policy checks are ready
- mining readiness passes if this wallet is meant for Satcoin