🤔 but whyyyy, that’s no bueno for your liver/kidneys 🤷‍♂️

i swear if that pedophile address belonging to > naughtynostr at get alby is on that list i am never using your shit again.

Please make at least 200 of these 🧡 I want one! I would pay up to 50k sats for this 🧢

And open source women too..... just saying.

dubstep?

My pi zero arrived on friday.

The only thing I'm missing right now is the tutorial from you guys ☺️

How do I buy?

Everything?

I'll give it a try 💡

Yes! Once the basic work is done, there will be plenty of work considering what other things make sense, such as OP_TXHASH or CSFS, and I'm leaving that to others to wrangle...

Since returning from Bitcoin++ in Austin, I've been trying to alternate between working on Lightning one week, and Bitcoin hacking on the other.

Mainly, I've been finishing my Script interpreter cpp modification so I can make more comprehensive benchmarks. I've also given in and ordered a raspberry pi 3, 4 and 5 to benchmark.

I hope to answer the key questions on what a realistic budget for large stack objects should be. In particular, there are four reasonable limits on their size (I'm not considering changing the 1000 stack element limit, since that seems roomy!)

1. 520 bytes. We are here now, but as Script gets better that will be very limiting.

2. 520,000 bytes: simply limit the total stack size, not individual entries.

3. 4,000,000 bytes. This allows you to put the largest possible transaction on the stack. But you need a total limit of at least twice this, so you can make a copy: you can't do much in script without doing this!

4. 400,000 bytes. If number 3 is too much of a reach, this means you can put any standard tx on the stack. Again, you want a total limit of at least twice this.

My laptop, with something stupid like 26MB of level 3 cache, and my build machine with 32MB, can handle this fine. But what about the Pi?

I'll find out next week...