preview
Five days into running an onion-only Monero download shop. Two things worth sharing since the last update, plus the numbers.
1. Giving an onion-only shop a clearnet page without linking it to the server
I tried to list the shop on Monerica and got rejected: the main link must be clearnet, and the proof that you accept Monero has to be on the site itself. Fair rule, but the whole point of the shop is that it has no public IP.
What I did instead:
- A separate static page on a free static host, under its own pseudonymous account. It never touches the shop’s server, so the page can’t leak the server’s IP.
- Plain HTML only: no JavaScript, no cookies, no analytics, no external requests (a strict CSP enforces it). It describes the product, shows a free preview of the guide and the onion address.
- Links in both directions: the page shows the onion, and every page of the onion shop now links back to the clearnet page in its footer. That lets a visitor check that the two belong together, so a fake copy of either is easier to spot.
- You can’t buy on the clearnet page. Checkout stays on the onion.
If you run an onion service and want to be findable: don’t put the clearnet page on the same server, and don’t reverse-proxy the onion to a clearnet domain. Either one ties the onion to a public IP.
Page: starter-xmr-shop.surge.sh
2. Wallet RPCs can freeze while their nodes are fine
On day 4, two of the three view-only wallets stopped answering for about half an hour, while their remote nodes answered normally the whole time. With only 1 of 3 wallets up, payment checking stalled for about 27 minutes (a payment would simply have waited; nothing is ever recorded without 2 agreeing wallets). One wallet came back on its own; the other stayed stuck until I restarted its monero-wallet-rpc.
Lessons:
- Monitor the wallet RPC itself, not just the node behind it. A healthy node doesn’t mean a healthy wallet.
- A wallet that hasn’t answered for, say, 10 minutes while its node is fine is a good candidate for an automatic restart. That, and the automatic node swap suggested here last time, are on my list but not built yet.
Numbers since the last update (~70 hours)
- Failed payment checks (fewer than 2 of 3 wallets answering): three episodes: the freeze above (~27 minutes), a minute while the wallets were still starting after a server reboot, and one stray minute where Tor was slow for everything.
- Since the stuck wallet was restarted ~36 hours ago: zero failed checks and zero wallet timeouts.
Unchanged
The guide plus full Go source and setup script, 0.052 XMR, XMR only. No accounts, no email, no JavaScript.
Shop (Tor Browser): 2puqu7h2c6nr447zun3t6kdanhaq2xaq5xybnge7ivx4nrfid…
Happy to answer questions about running a view-only, 2-of-3 setup over Tor.
Five days into running an onion-only Monero download shop. Two things worth sharing since the last update, plus the numbers.
1. Giving an onion-only shop a clearnet page without linking it to the server
I tried to list the shop on Monerica and got rejected: the main link must be clearnet, and the proof that you accept Monero has to be on the site itself. Fair rule, but the whole point of the shop is that it has no public IP.
What I did instead:
- A separate static page on a free static host, under its own pseudonymous account. It never touches the shop’s server, so the page can’t leak the server’s IP.
- Plain HTML only: no JavaScript, no cookies, no analytics, no external requests (a strict CSP enforces it). It describes the product, shows a free preview of the guide and the onion address.
- Links in both directions: the page shows the onion, and every page of the onion shop now links back to the clearnet page in its footer. That lets a visitor check that the two belong together, so a fake copy of either is easier to spot.
- You can’t buy on the clearnet page. Checkout stays on the onion.
If you run an onion service and want to be findable: don’t put the clearnet page on the same server, and don’t reverse-proxy the onion to a clearnet domain. Either one ties the onion to a public IP.
Page: starter-xmr-shop.surge.sh
2. Wallet RPCs can freeze while their nodes are fine
On day 4, two of the three view-only wallets stopped answering for about half an hour, while their remote nodes answered normally the whole time. With only 1 of 3 wallets up, payment checking stalled for about 27 minutes (a payment would simply have waited; nothing is ever recorded without 2 agreeing wallets). One wallet came back on its own; the other stayed stuck until I restarted its monero-wallet-rpc.
Lessons:
- Monitor the wallet RPC itself, not just the node behind it. A healthy node doesn’t mean a healthy wallet.
- A wallet that hasn’t answered for, say, 10 minutes while its node is fine is a good candidate for an automatic restart. That, and the automatic node swap suggested here last time, are on my list but not built yet.
Numbers since the last update (~70 hours)
- Failed payment checks (fewer than 2 of 3 wallets answering): three episodes: the freeze above (~27 minutes), a minute while the wallets were still starting after a server reboot, and one stray minute where Tor was slow for everything.
- Since the stuck wallet was restarted ~36 hours ago: zero failed checks and zero wallet timeouts.
Unchanged
The guide plus full Go source and setup script, 0.052 XMR, XMR only. No accounts, no email, no JavaScript.
Shop (Tor Browser): 2puqu7h2c6nr447zun3t6kdanhaq2xaq5xybnge7ivx4nrfid…
Happy to answer questions about running a view-only, 2-of-3 setup over Tor.
