Avatar
Alex
6a46242f4d73c14e114d95e1336439f5b91189571dd9c2d4fa418db018cb8ef5
Working on Core Lightning

So bitcoin payments seem to be take-out kiosk only at the moment (or at least the servers have yet to be trained on offering them tableside.)

No worries though, an employee was more than happy to accept my bitcoin and settle the bill for me.

It's kind of wild how busy this Steak n Shake is. It was nice to be greeted by a guy in a Satoshi shirt too.

That's awesome! What talk was this? I was also curious in 2011, but didn't get off my butt until 8 years ago. I think I have Andreas to thank for really changing my perspective and realizing I needed to be involved. We didn't have the Anita Posch Show back then. 😂

We did it! The Bitcoin network is currently being secured by 1.1 zettahash! Who else is contributing?

My ollama chat context is getting too long, and I've got to start a new one, but there's so much history it really feels like I'm killing an innie. 😢

I've been waiting a long time for that BOLT12 tattoo. Maybe next week?

We had fun encountering this particular fee environment scenario in Core Lightning for the first time. The minimum acceptable feerate could end up the same as the proposed feerate (typically they are relatively far apart.) Then if one node increased by a single sat it would disable the channel and force a disconnect due to feerate disagreement. We now ensure a minimum offset (by the feerate proposer) to account for the next_block_feerate == min_relay_feerate situation.

Replying to Avatar Aaron

Learned a little more how the legacy credit card system works and got a good bit of motivation to hasten my family's move to a full Bitcoin standard.

We go to the local farmers market every week and we had noticed that sometimes if we went to a shop after our farmers market run, our credit card would decline despite having plenty of available balance. This continued happening and got so bad that our card had become unusable. I eventually got fed up enough that I called the bank to find out what is going on.

Turns out that when we make many payments in quick succession to many different vendors, it triggers the banks fraud detection. So each week we would go to the market and our card would get suspended. Someone from the bank would then need to manually review our txs, see that it is the same farmers market pattern and then restore our card. Apparently due to black friday sales, they have been swamped with fraud detections, so they have been slower at restoring cards, making our card unusable. The bank said that essentially this process is going to happen every time we go to the farmers market. I am honestly shocked at how rudimentary their fraud detection algorithms must be. Surely not too hard to see that the pattern of txs matches the same pattern at the same time, every week.

I had no idea how much manual work was going in to keeping our card working. Obviously Bitcoin fixes this and really reiterates how much of a step improvement Bitcoin is compared to the legacy system.

The only reason we use a credit card over a debit card is that in the case of it getting compromised, then the bank is on the hook for stolen funds, which i my experience makes them much more responsive.

We are going to stop being lazy and just get out cash each week from now on. Much better privacy and better for the merchants. Long term I really want to start getting paid in Bitcoin and then hopefully find some good tools for interacting with the legacy system. Really need to orange pill my local farmers, but that is proving difficult after already trying multiple times.

I tipped my Uber driver last week by having him download phoenix. I'd say it was a pretty good onboarding experience - you can get the sense of it right off the bat. This mempool environment may change the calculus though.

Will be interested to hear your approach at the farmers' market.