The RP1 wallet experience brings the chain’s public user journeys together: portfolio and activity, native transfers, staking, governance, privacy, and bridge flows.
Wallet actions
| Action | What it does | User control |
|---|---|---|
| Send and receive | Transfers native and supported assets | Confirm recipient, denom, amount, and fee. |
| Shield and unshield | Moves assets into or out of a private pool | Review privacy metadata and retain wallet-side keys. |
| Stake | Delegate RP1 to a validator | Review commission, voting power, uptime, and unbonding rules. |
| Bridge | Deposit or withdraw supported external assets | Confirm source transaction, destination, and pending state. |
| Govern | Deposit, vote, and inspect proposals | Verify proposal type, voting period, quorum, and vote choice. |
Testnet faucet
The faucet is a testnet convenience, not a production funding source. Prefer the hosted wallet at https://app.rp.one/faucet, which claims through a server-side endpoint. Never embed a faucet mnemonic in a browser bundle.
A wallet integration should:
- connect to the public testnet (
chain-1); - verify its
rp1address and chain ID against live/status; - request only the amount needed for testing from a server-side faucet API;
- display the returned transaction or claim state;
- handle one-claim or rate-limit errors without retry storms.
Staking and governance
Delegation protects consensus and gives a staker voting power. Governance proposals can change parameters or authorize module behavior, so an operator should read the full proposal and understand the activation boundary before voting.
The wallet UI is a convenience layer. Final state should be checked against chain queries, and a user should never sign a proposal or bridge request whose destination or message bytes are hidden behind a generic button.