MagnetGate
What comes next
MagnetGate's use of RQT grows in phases. Each phase uses only what Requant's consensus already has.
Phase 1: prepaid full access — live on the test network
- Deposit address per code from an offline list; no keys on the server
- Crediting after 6 confirmations, once per payment; balance carried over
- Days with discounts; code extended by the paid days
- Separate full-access listeners on both exit nodes
- Payment screen in the Windows and Android apps
- Payment screen in the macOS app
- Free tier lowered to 2–3 Mbit/s once most apps have updated
- Payment settings and deposits visible and editable in the operator's admin panel
- A clearer entry point to full access on the app's home screen
In-app wallet
- A wallet inside MagnetGate with an encrypted key-file backup and local signing, so paying does not need a second app
- Balance, history and "pay for N days" in one screen
Phase 2: exits earn RQT
- People who run exit nodes receive RQT for the traffic they carry: half of what users pay, shared by measured traffic
- Payout addresses for exits and batched payouts
- More countries through community exits
Phase 3: pay as you go
- One-way payment channels: a client deposits into a 2-of-2 output with a refund after a time lock and signs ever larger payments to the exit
- No per-payment transaction on the chain; the channel closes with one
Requant already has the spending conditions these channels need.
On the main network
- New deposit wallet and addresses for the main network (
rq1…), and main-network prices - Confirmation depth scaled with the amount
- Ways to get RQT besides mining: swaps with Bitcoin-family, EVM and Monero chains