0

Starter Shop, day 5: a clearnet front door that doesn't expose the server, and a wallet that froze

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.

0

Starter Shop, two days in: no sales yet, one dead node, and a Tor fix that worked

preview

Two days ago I launched an onion-only Monero download shop and wrote up how it works. A quick, honest update, mostly about what broke.

Sales

One order since launch, not paid (yet: there’s no expiry, so a payment still counts whenever it arrives). The only paid order so far is my own test from before launch. So: zero sales. Nothing surprising for a two-day-old onion shop, but I said I’d report honestly.

What broke, and what fixed it

The shop runs in light mode: three view-only wallets, each talking to a different remote onion node, and a payment only counts when 2 of 3 agree. In the launch post I said the wallets’ missed polls were Tor latency, not a bad node.

That was half right. A commenter here suggested giving each wallet its own Tor circuit and a longer RPC timeout. I gave each wallet its own SocksPort and raised the timeout from 15 s to 60 s. Over the next ~34 hours:

  • failed payment checks (fewer than 2 of 3 wallets answering): 0.41/h → 0.12/h
  • wallet timeouts overall: 9.5/h → 4.8/h

But one wallet barely improved, and that one was the node: it had stopped answering entirely and dropped off monero.fail. After switching that wallet to another onion node (and ~10 minutes of it catching up), all three have answered every check since.

Lessons if you run something similar

  • One Tor circuit for several wallets makes them fail together. Give each its own SocksPort.
  • 15 s is too short for wallet RPC over Tor; 60 s works.
  • Check your nodes against monero.fail now and then. A node that vanishes from the list is a red flag.
  • After switching a wallet’s node, expect it to time out for a few minutes while it catches up. That’s normal.
  • This is exactly why 2-of-3 exists: one dead node cost nothing but log noise.

Unchanged

The shop still sells the guide plus full source and setup script for 0.052 XMR, and the per-wallet SOCKS ports are already in the guide’s setup script. No accounts, no email, no JavaScript.

Shop: 2puqu7h2c6nr447zun3t6kdanhaq2xaq5xybnge7ivx4nrfid… (Tor Browser)

Questions about light mode are welcome here, whether or not you buy anything.

Two days ago I launched an onion-only Monero download shop and wrote up how it works. A quick, honest update, mostly about what broke.

Sales

One order since launch, not paid (yet: there’s no expiry, so a payment still counts whenever it arrives). The only paid order so far is my own test from before launch. So: zero sales. Nothing surprising for a two-day-old onion shop, but I said I’d report honestly.

What broke, and what fixed it

The shop runs in light mode: three view-only wallets, each talking to a different remote onion node, and a payment only counts when 2 of 3 agree. In the launch post I said the wallets’ missed polls were Tor latency, not a bad node.

That was half right. A commenter here suggested giving each wallet its own Tor circuit and a longer RPC timeout. I gave each wallet its own SocksPort and raised the timeout from 15 s to 60 s. Over the next ~34 hours:

  • failed payment checks (fewer than 2 of 3 wallets answering): 0.41/h → 0.12/h
  • wallet timeouts overall: 9.5/h → 4.8/h

But one wallet barely improved, and that one was the node: it had stopped answering entirely and dropped off monero.fail. After switching that wallet to another onion node (and ~10 minutes of it catching up), all three have answered every check since.

Lessons if you run something similar

  • One Tor circuit for several wallets makes them fail together. Give each its own SocksPort.
  • 15 s is too short for wallet RPC over Tor; 60 s works.
  • Check your nodes against monero.fail now and then. A node that vanishes from the list is a red flag.
  • After switching a wallet’s node, expect it to time out for a few minutes while it catches up. That’s normal.
  • This is exactly why 2-of-3 exists: one dead node cost nothing but log noise.

Unchanged

The shop still sells the guide plus full source and setup script for 0.052 XMR, and the per-wallet SOCKS ports are already in the guide’s setup script. No accounts, no email, no JavaScript.

Shop: 2puqu7h2c6nr447zun3t6kdanhaq2xaq5xybnge7ivx4nrfid… (Tor Browser)

Questions about light mode are welcome here, whether or not you buy anything.

0

I launched a Monero-only onion shop. Here's what its first day looked like.

preview

I wanted to sell a digital download for XMR without a payment processor, without accounts, and without anything on the clearnet. So I wrote a small shop and put it behind a Tor onion service. It went live this week. Some notes from the first day, because a few things surprised me.

The setup

  • One Go binary and one SQLite file. No JavaScript, no cookies, no customer accounts.
  • Every order gets its own subaddress. The buyer gets a 64-character receipt code instead of an account; the shop only stores its hash.
  • The server has a view-only wallet. The spend key never touches it, so someone who takes the server still can’t move the money.
  • No local node (“light mode”). Three copies of the view-only wallet each talk to a different remote .onion node, and a payment only counts once 2 of 3 report it identically with 10 confirmations. Any single honest node blocks a fake payment unless the other two lie the same way.
  • The server is about 20 GB and uses about 3 GB.

Day one

  • The first real order (a 0.001 XMR test) was recorded with 2 of 3 wallets agreeing, flipped to Paid, and the download worked.
  • Over the first ~22 hours, the three wallets missed their 30-second poll 10, 47 and 118 times. My first instinct was “one node is bad, swap it.” But the misses clustered at the same moments across different nodes, and when I tested the “bad” node directly over Tor it answered 3/3 while another one failed 2/3. That pattern points at Tor latency on the server, not at any one node. Swapping a node would have just moved the problem.
  • Because of the 2-of-3 rule, one slow wallet costs nothing. Two slow at once means a payment waits for the next cycle. Nothing gets recorded without agreement, which is the whole point.
  • If I were starting again I’d probably run 5 nodes and require 3, which tolerates two slow ones at the same time.

Things it deliberately doesn’t do

No refunds in software, no subscriptions, no clearnet. Light mode trusts a majority of the nodes you pick; if that’s not good enough for what you sell, run your own node (~100 GB).

Disclosure: I’m selling the write-up

I turned the whole thing into a guide and bundled it with the complete source and a setup script that installs the stack on Debian/Ubuntu (it checks the Monero binaries against their signed hashes). It’s 0.052 XMR, sold from the same shop it teaches you to build.

The table of contents and one full section, on choosing remote nodes, are below for free, so you can judge whether it’s worth it.

Shop: 2puqu7h2c6nr447zun3t6kdanhaq2xaq5xybnge7ivx4nrfid… (Tor Browser)

Happy to answer questions about the setup here, whether or not you buy anything.


Free preview: Run Your Own Monero Onion Shop

Contents

  1. What you get, and who this is for
  2. How it works
  3. Two decisions before you start: own node or light mode, and where to host it
  4. Prepare your wallet (on your own computer)
  5. Prepare the server
  6. Build and upload
  7. Install
  8. Choosing remote nodes (light mode) ← full section below
  9. Addresses, product and launch
  10. Go-live checklist
  11. Running the shop
  12. Limits you should know about
  13. Troubleshooting

8. Choosing remote nodes (light mode)

  • Onion addresses only. The wallet talks to the node over plain HTTP. An onion address authenticates the node end to end; a clearnet node reached through Tor could be tampered with by the exit relay. The script refuses non-onion nodes.

  • Three different operators, ideally found on two different public node lists. The software cannot check that they are independent; you can.

  • Test each one from the server before using it:

    curl -s --socks5-hostname 127.0.0.1:9050 -m 45 http://NODE.onion:PORT/get_info | jq '.height, .synchronized'
    

    Try a few times. Nodes reached through Tor often fail one request and answer the next.

  • Write down a spare in case one goes away.

What to expect in practice. On the reference shop’s first day, all three wallets timed out now and then, and the timeouts tended to happen at the same moments for different nodes. That points at Tor latency on the server rather than one bad node. One wallet missing a cycle is harmless: payments continue with the other two. When two miss the same cycle, payments wait for the next one, 30 seconds later. Nothing is ever recorded without 2 agreeing wallets.

You can use up to 5 nodes (wallet --light N1 N2 N3 N4 N5). A payment then needs 3 of 5, which tolerates two slow nodes at once.


The full guide, the complete Go source with tests, and the install script: 0.052 XMR at 2puqu7h2c6nr447zun3t6kdanhaq2xaq5xybnge7ivx4nrfid…

I wanted to sell a digital download for XMR without a payment processor, without accounts, and without anything on the clearnet. So I wrote a small shop and put it behind a Tor onion service. It went live this week. Some notes from the first day, because a few things surprised me.

The setup

  • One Go binary and one SQLite file. No JavaScript, no cookies, no customer accounts.
  • Every order gets its own subaddress. The buyer gets a 64-character receipt code instead of an account; the shop only stores its hash.
  • The server has a view-only wallet. The spend key never touches it, so someone who takes the server still can’t move the money.
  • No local node (“light mode”). Three copies of the view-only wallet each talk to a different remote .onion node, and a payment only counts once 2 of 3 report it identically with 10 confirmations. Any single honest node blocks a fake payment unless the other two lie the same way.
  • The server is about 20 GB and uses about 3 GB.

Day one

  • The first real order (a 0.001 XMR test) was recorded with 2 of 3 wallets agreeing, flipped to Paid, and the download worked.
  • Over the first ~22 hours, the three wallets missed their 30-second poll 10, 47 and 118 times. My first instinct was “one node is bad, swap it.” But the misses clustered at the same moments across different nodes, and when I tested the “bad” node directly over Tor it answered 3/3 while another one failed 2/3. That pattern points at Tor latency on the server, not at any one node. Swapping a node would have just moved the problem.
  • Because of the 2-of-3 rule, one slow wallet costs nothing. Two slow at once means a payment waits for the next cycle. Nothing gets recorded without agreement, which is the whole point.
  • If I were starting again I’d probably run 5 nodes and require 3, which tolerates two slow ones at the same time.

Things it deliberately doesn’t do

No refunds in software, no subscriptions, no clearnet. Light mode trusts a majority of the nodes you pick; if that’s not good enough for what you sell, run your own node (~100 GB).

Disclosure: I’m selling the write-up

I turned the whole thing into a guide and bundled it with the complete source and a setup script that installs the stack on Debian/Ubuntu (it checks the Monero binaries against their signed hashes). It’s 0.052 XMR, sold from the same shop it teaches you to build.

The table of contents and one full section, on choosing remote nodes, are below for free, so you can judge whether it’s worth it.

Shop: 2puqu7h2c6nr447zun3t6kdanhaq2xaq5xybnge7ivx4nrfid… (Tor Browser)

Happy to answer questions about the setup here, whether or not you buy anything.


Free preview: Run Your Own Monero Onion Shop

Contents

  1. What you get, and who this is for
  2. How it works
  3. Two decisions before you start: own node or light mode, and where to host it
  4. Prepare your wallet (on your own computer)
  5. Prepare the server
  6. Build and upload
  7. Install
  8. Choosing remote nodes (light mode) ← full section below
  9. Addresses, product and launch
  10. Go-live checklist
  11. Running the shop
  12. Limits you should know about
  13. Troubleshooting

8. Choosing remote nodes (light mode)

  • Onion addresses only. The wallet talks to the node over plain HTTP. An onion address authenticates the node end to end; a clearnet node reached through Tor could be tampered with by the exit relay. The script refuses non-onion nodes.

  • Three different operators, ideally found on two different public node lists. The software cannot check that they are independent; you can.

  • Test each one from the server before using it:

    curl -s --socks5-hostname 127.0.0.1:9050 -m 45 http://NODE.onion:PORT/get_info | jq '.height, .synchronized'
    

    Try a few times. Nodes reached through Tor often fail one request and answer the next.

  • Write down a spare in case one goes away.

What to expect in practice. On the reference shop’s first day, all three wallets timed out now and then, and the timeouts tended to happen at the same moments for different nodes. That points at Tor latency on the server rather than one bad node. One wallet missing a cycle is harmless: payments continue with the other two. When two miss the same cycle, payments wait for the next one, 30 seconds later. Nothing is ever recorded without 2 agreeing wallets.

You can use up to 5 nodes (wallet --light N1 N2 N3 N4 N5). A payment then needs 3 of 5, which tolerates two slow nodes at once.


The full guide, the complete Go source with tests, and the install script: 0.052 XMR at 2puqu7h2c6nr447zun3t6kdanhaq2xaq5xybnge7ivx4nrfid…