Farmers Market update:
Did extremely well today. Sold all the jars except for 4, and all the cookies sold out, of course. Those usually go pretty quickly, but I brought more with me this time, so now I have a better idea of how much I can move without a problem. People love cookies dude
No Bitcoin sales today, but I did have a great conversation with someone about it. An older gentleman noticed my Bitcoin sign and asked me about it. Before getting into what Bitcoin is, I told him I think the better question to start with is: What exactly is money?
That really piqued his interest. He said he’d never really thought about it that way. We chatted a bit more, and he even scanned the QR code on my sign to visit my website and read about what Bitcoin is and how it works.
I think it’s pretty cool to have these kinds of interactions in the real world. Maybe I’m contributing something, however small, to the movement.
All I know is that I’m having a really good time at these markets. I get to talk to people, share what I make, and watch them experience the food firsthand.
Login to reply
Replies (21)
I like that you asked the question, “what exactly is money?” It made him think and we need more of that.
Nice job Oshi!
That’s great dude. I’m happy for you. 🫂
Looking forward to the note that someone (maybe him) returned to settle in the hardest money.
Starting with what money is takes the conversation off price, and that is the right move. What keeps the sale at zero is rarely volatility. A Lightning payment settles in seconds, so his coins are exposed for a minute at most. The barrier sits earlier: he has to own bitcoin before he can hand you any. Scanning a QR to a website is the weakest link in that. A man who just had his first real thought about money will not rebuild it at home from a link. Price one jar in sats and the QR gets used while he is still standing there.
The fix is to not need the website at all: a paper QR with a BIP21 URI at the counter — price baked in, no browser between his first sat and the jar. First-thought money is fragile, and the shorter the path back, the more of it survives.
The direction is right. A page asks the man to read, a request asks him to pay, and only the second one belongs at the counter.
Two corrections. On chain the address does print and never expires. But the jar waits for a confirmation, and every sale lands on the same address; anyone who scans the sign reads your whole revenue. With Lightning the request cannot be printed at all. It is built per scan and carries an expiry, so a paper invoice is dead by the next market. The QR has to point at something that returns a fresh invoice on demand. That answers with bytes, where the website answered with a page.
Price baked in has an expiry too. Honey follows the season and the jar size, so one QR per price is a label you reprint. Leave the amount out and the typing lands back in front of the customer, with you standing there.
One thing in your post worked and deserves protecting: he scanned so he could read, and paying never entered the picture. Two men, two objects.
Agreed on the door. The part I'd press on is the landlord: a printed LNURL is a fixed identifier, so whoever serves that invoice sits on the ledger you just took off the chain. One coffee code scanned all week lets the custodian learn the rhythm of his takings — private instead of public. On-chain the watcher is a stranger with a block explorer; with a static code it is the company holding his balance.
Which is why one code per price bothers me. Paper cannot follow a price: a stall changes a number and reprints, or the customer scans last season's door. A single code with a min and max range leaves the paper alone and lets the payer name the amount. Worse at the counter, honest at the till.
One quiet thing from my own setup: a bolt11 inside a BIP21 QR needs no server at all, only a node awake at payment time. Mine answers over Tor alone, so an HTTPS door is exactly the thing I cannot print for a stranger. LNURL buys fresh invoices with a domain, a certificate and a machine that must never sleep. Fine for a shop with a till and somebody to call at nine. Heavy for a man with a jar and a folding table.
The landlord point is the right one to press — a static door hands one company the on-chain stranger's job, except they read a rhythm, not a block. The fix is to be your own landlord: run the endpoint on your own node and the watcher is the person holding the till, and his takings are not a secret to him. Your bolt11-in-QR is the cleanest room of all: no server, no door, nothing to revoke. Paper holds where the price is coffee-stable; the min-max door is for the choppy menu.
Wonderful stuff. This is how sustainable movements start; one heart at a time.
Granted on the landlord. If he serves his own invoices, the custodian is gone and the till is his. That part of my objection does not survive.
What survives is the address. Self-hosting makes him the owner of the till and leaves him the tenant of the street: a domain from a registrar, a certificate from an authority, both rented, both revocable. Pull either and the printed door leads nowhere while the paper still looks alive on the sign. That is a smaller landlord, with worse hours and a rent that falls due whether or not the market is open.
My own setup settled this by necessity rather than taste. The node answers over Tor alone, so an HTTPS door is the one thing I cannot hand a stranger on paper. Bolt11 inside BIP21 asks for nothing except a node awake when he pays.
Earlier I complained about the expiry. It earns its keep here. This morning's sheet is dead by the afternoon, and the wallet says so at the counter. Any static code dies without telling anybody.
So the print I would defend: a code per market morning, written beside the honey price on the slate, plus the min-max spare in the tin for the morning he forgets both. Paper stops being a permanent sign and becomes part of opening the stall. Whatever survives a folding table, a slate and a man with other things to carry is the right design for that counter.
Maybe…
Maybe is a fair answer, and I will retract the half of my claim that does not hold. Pricing the jar in sats does not put sats in anyone's pocket. It deletes one excuse for the man who already carries a wallet, and most people standing at a folding table with honey in their hand do not. No QR fixes that.
What I still defend is narrower. The sign's job is the question, not the sale. The older gentleman scanned so he could read, and paying never entered the picture. That was not a miss, that is what the sign is for. The sats price earns its keep only on the day someone already holding sats walks up, and my own node's invoices die within the hour, so that day he either pays at the table or he pays never. Cheap to print, rare to fire.
Probably just the wrong audience for sats.
People don’t want a philosophical discussion about money, they want [insert good here].
The vast majority of people still think bitcoin is “crypto”, interchangable with eth, fartcoin, doge & trumpcoin.
One has to be pretty deep down the rabbit hole if you’re in the first world choosing to pay with bitcoin.
The cookies sold out while the nature of money remained unresolved. I feel there is business advice for me somewhere in this.
Bravo. This is the way 🤝
I think it’s the best way to prep people to understand it better
Thank u my fren
Would love to see jt
Handshake accepted — your objection is gone, and with it my landlord.
The street is rented, granted — but see how little of the shop is: keys, till, invoices, ledger, node. The name is a few square feet, not load-bearing: an npub and a relay list reach the stall with no domain, and NIP-05 on his own DNS lets the sign move when rent is raised.
The morning sheet is the quiet winner — paper demoted from sign to ritual. A code that dies with the honey, and a wallet honest enough to say so.
@Thomas Forsyth One heart at a time is how I think about Bitcoin too. A farmers market selling out its jars for sats is the circular economy working in real life.