Accepting Monero in an Online Store
The payment-processor pattern: BTCPay, a fresh subaddress per invoice, a watch-only wallet, e-commerce plugins and confirmation handling.
#development
10 lessons with this tag.
Building Real Services
Capstone: assemble a BTCPay-style payment processor, an instant-swap exchange, and a Cake-style mobile wallet from the building blocks you've learned.
Security, Architecture & Production
Run it safely in production: hot/cold key separation, confirmations and reorgs, idempotency, monitoring, key management, and testing on stagenet first.
Building a Light Wallet
How Cake Wallet and MyMonero work: embedded wallet2 vs a light-wallet server, view-key scanning and view tags, and the security trade-offs of each.
Sending Payments & Managing Outputs
Build the payout side: transfer, transfer_split and sweep_all, fees and priority, locked vs unlocked balance, change outputs, and hot/cold wallet design.
Receiving Payments: Subaddresses & Watch-Only Wallets
The payment-processor pattern: a fresh subaddress per invoice plus a watch-only (view-key) wallet to detect payments securely, with confirmations and the 10-block lock.
monero-wallet-rpc: The Workhorse
monero-wallet-rpc as a service: accounts and subaddresses, get_balance, create_address, get_transfers, transfer and sweep_all — the engine behind most server integrations.
The Daemon RPC API
The daemon's JSON-RPC and legacy endpoints — get_info, get_fee_estimate, get_outs, send_raw_transaction — the read-and-broadcast layer of the chain.
Running monerod for Integration
Run your own node for an integration: restricted vs unrestricted daemon RPC, ZMQ push notifications, pruning, auth and Tor, and why you must not trust a remote node.
The Monero Developer Stack
monerod, monero-wallet-rpc, wallet2 and light-wallet servers — the components every Monero integration is built from, and the three main integration patterns.