GM! 🧡

👀

2025 is shaping up to be the flattest year ever for Bitcoin.

Just zapped you back 100 sats. It shows sent from my wallet but doesn’t show on your note. Did you get it?

Try again. I just changed mine to my Rizful address. I’ll zap it back.

Unsure what the issue is. Several others have zapped successfully. You’re the 3rd person who said they couldn’t zap me, and all 3 were using Amethyst. 🤷‍♂️

⚡️📈 NEW - Zcash just hit $500

⚡️🚨 ALERT - AWS is down again for the second Monday in a row

Looks like half of the internet is struggling again…

yea, it’s pretty bad

An Android app that toggles airplane mode when the device is put to sleep and woke up.

Why do people on Twitter do this every 25 seconds? 😂

She said yes

A guy at btc++ Istanbul had an interesting project. He downloads the blockchain without checking for doublespending. After he has all the data, he does a doublespend check by running an efficient sorting algorithm called MergeSort, which, in his implementation, takes all "input" utxos and "output" utxos, sorts them alphabetically via txid_vout, and removes duplicates. Those are always outputs created in one tx and spent in another

The result is a list only containing unspent outputs, i.e. the result is the utxo set, and this procedure gives him a sync speedup of slightly over 50%. It also does not seem to require storing an "intermediate" utxo set *during* ibd

I wonder if is wise to do ibd with that method, and then apply the utreexo accumulator procedure to the utxo set once it gets created at the end of ibd. The result would be, you only need the full utxo set once during the lifetime of your node: you need it at the end of ibd, and only to construct the utreexo accumulator. After that, you don't need the utxo set, unless you want to help others sync the same way

You can just do things.

The hard decisions I’ve got to make in life…

#coffeechain

I just tried to swype "fuck banks" but the keyboard output "Gucci babies." 🤔

i spent 27k sats to vibe a site to track a 5555 sats prize 😂