Repository navigation
Message Signing
Verified against: Pinned source and release revisions, Qwertycoin mainnet where applicable, 2026-09-29.
Message signing proves control of a wallet key for a particular message; it is not a transaction and does not reveal a spend key. It does not prove a legal identity unless the address-to-person binding was established separately.
The current wallet RPC exposes sign and verify through /json_rpc. Keep RPC authenticated and private.
Illustrative request:
{"jsonrpc":"2.0","id":"sign-1","method":"sign","params":{"data":"release statement"}}Verification requires the message, address, and returned signature. Inspect the exact request fields for the pinned release in Wallet RPC Reference.
The historical simplewallet instructions are retired; use current CLI/GUI/RPC features.
Qwertycoin documentation · Verified against pinned revisions · Report a documentation issue
Start
Project
Wallets
Nodes and builds
- Run a Full Node
- Configuration and Ports
- Docker
- Linux Service Operation
- Upgrade and Recovery
- Synchronization Troubleshooting
- Build Overview
EPoSE
- Overview
- Service Node Quickstart
- Configuration and Identity
- Admission and Lifecycle
- Epochs and Qualification
- Rewards
- Monitoring and Diagnostics
- FAQ and Troubleshooting
APIs
- API Overview
- Daemon JSON-RPC
- Daemon HTTP and Binary RPC
- Wallet RPC Setup
- Wallet RPC Reference
- EPoSE RPC Reference
- Errors and Compatibility
- Integration Examples
- Complete Route Inventory
Mining and ecosystem
- RandomX Mining
- Solo Mining
- Pool Mining
- Pool Operator Integration
- Explorer and Web Wallet Hosting
- Exchanges and Compatibility
Contributing