Who’s packin 👀

If you don't have it, download Wallet of Satoshi, go to Receive => Lightning address. Copy the XXXXX@walletofsatoshi.com email-like address. Open Damus, go to Profile => Edit and paste the address in the field "Bitcoin Lightning Tips". You're all set now now. In order to zap, use a client like snort.social or iris.to and click zap icon on posts.

About to record working title “Demystifying and Understanding Bitcoin Core Development” with some awesome guests.

Do you guys have any questions that would help you understand what’s going on, how its done, FUD, etc…?

I’m seeing lots of notes about how the average pleb can’t, or won’t set up their own non-custodial lightning node. I’m calling BS.

I’m an average pleb without a technical background. I set up my bitcoin node, lightning node and a couple of channels. It was a weekend project, and a lot of fun.

The best part was I didn’t do it alone. The team at Start9 was incredible, and through their Telegram channel they walked me through any issues I ran into ( #[0] , #[1] , #[2] )

#[3] , #[4] , #[5] , and the rest of the #Nodestrich crew were incredibly helpful in getting my lightning channels up and running with lots of inbound liquidity. I highly encourage you to reach out to any one of them if you’re thinking about starting your own non-custodial lightning node.

Give me your thoughts below. Are you an average pleb node-runner or do you plan to be? Do you think non-custodial lightning will take off or is it too complicated?

✌️⚡️

“bruh, did you see my reply”

“nah fam, fees be crazy, it probably got evicted”

lol, you can only see new events on your feed every 10 mins , after a block is mined

or even modular. seems like a good design is to separate storage from relay so operators can choose their own backend

Because I am developing the relay software in two steps…

IMO the most important part is being able to accept events and send them to subscribed clients. Storage can be a completely separate process, and will be developed in a second phase.

But in a nutshell, for now, you’re right. Still could be useful when relays are overloaded… a readonly one could stand up to the pressure as it has way less work to do.

gm builders!

I am in the process of deploying an instance of the brand new relay implementation I am working on…

As we speak, it dosn’t store anything… it just relays events and forgets about them instantly. It should evolve quickly and catch up with missing functionalities as time goes by as I am working full time on it.

I will soon need some traffic to stress test it a little. Let’s keep in touch if you’re interested in giving a hand by adding it to your relays list.

I’m not sure that one exists - maybe you could write one?

Link please!!!

Looking forward to reading this:

I’m not sure that one exists - maybe you could write one?

There is a relay that requires a pubkey to have a PoW minimum of N - I forget the threshold and url.

It’s difficult as I think PoW to $ calculations are hard. And then server ROI vs deplete phone battery ROI to generate a PoW gives asymmetry.

Which is why I liked PoW aggregation - sum of your PoW over time. But a spammer persistent enough can also build free PoW due to randomness or they can spend.

It may end up more of an indicator rather than a single value truth test.

Same here

Reverse sear, finished in cast iron skillet.

30 day dry aged Kansas City strip. It’s what’s for dinner.