Perhaps someone can do a writeup on the main source(s) of pain when it comes to Tor relay support. Fixing that (all over the place) might be a good grant topic? nostr:note1mwrm0hffg7pswdtuhmcjk9qeuf7m67j3jvj6chufcvhxzmfr2mpsefxl54

I'm looking forward. Lightning channels not* affected.

I plan to make an AssumeUTXO snapshot at whichever block eventually wins (and maybe one for the losing block to see if that's handled correctly).

* = unless there's some really poor reorg handling bug

I went on a nice three hour pleb walk today: https://www.meetup.com/nl-NL/bitcoin-lab-berlin/events/300026924/

"Please click on the entity that has NO fur"

- Deutsche Bahn captcha

Some caffeine #ClubMate #Berlin

Just tell them to install a 10 year old version of Bitcoin Core and keep their life savings in a hot wallet? If they refuse, you won the argument. If they don't refuse, they lose their stash and their opinion no longer matters :-)

If you're not too busy with ossification, consider checking if your node is accepting incoming connections. This sometimes works automatically via NAT-PMP, but may require manually forwarding port 8333.

Well, *everything* was excluded :-)

It's been almost two weeks since phoenixd was announced. Wen nostr:npub155m2k8ml8sqn8w4dhh689vdv0t2twa8dgvkpnzfggxf4wfughjsq2cdcvg integration?

https://phoenix.acinq.co/server

My understanding was that cyclists and other drivers are significantly less happy? Though it's not like human drivers in SF are amazing.

https://art19.com/shows/the-urbanist-agenda/episodes/9e713263-e5e3-4db2-b290-ed85b0b7e959

This attack reminds me of the Copay backdoor in an NPM sub-sub-sub-dependency. But this is next level. The partially lived in the code, added by "just some tests" commits - that didn't contain executable code.

They were then activated by something the rogue maintainer snuck into the release binaries. nostr:note159ur4n6p7nm88h6xes29klhtftg0wfkeljy3lf3nnzu2r9qaerhs3xugec

The github comments on the first commit say that this was a rogue maintainer who had behaved well for two years.

Impressive how this was caught within three weeks of the first malicious commit.

I don't get why nostr:npub18d4r6wanxkyrdfjdrjqzj2ukua5cas669ew2g5w7lf4a8te7awzqey6lt3 assigns 100% health to the block

https://mempool.space/block/0000000000000000000341cc26cda4af82cd25f7063c448772228cbf2836915b

It's completely filled with op_return stuff.

But it seems that they measure 'health' only by intentional exclusion.

The audit view is clear though:

About the invalid block, which put transactions in the wrong order: https://bitcoinexplainedpodcast.com/@nado/episodes/episode-84-marathon-pool-s-invalid-block-and-some-updates-about-the-show-azfmk

Aha, so that's probably what Marathon was trying to do last fall when they mined the invalid block (because who needs testnet): https://protos.com/you-can-now-mine-rather-than-inscribe-a-square-bitcoin-block-image/

https://twitter.com/provoost/status/1772945208587481556

Will at some point probably post here, but see my threads on X @provoost about the Pertsev trial that I attended today and yesterday.

I'm fairly sure I never did a podcast with Udi?

You mean the ECB is working on hiring a project manager for a proposal for a tender for a meta study... take your time :-)

'Zhimin Qian dreamt that the Dalai Lama would anoint her a reincarnated goddess and that she go on to become the Queen of Liberland, an unrecognised micronation on the Danube, where she would build the biggest Buddhist temple in Europe.'

(if you hit a paywall it may help to google the title and then follow the link there) nostr:note1lceskm8qq7885jqd84dfaen0dr8tygjsaujxd7z8dnn6483g2d2s86h6aa

This goes into more detail: https://protos.com/takeaway-worker-guilty-of-laundering-billions-with-bitcoin/

Leuker kunnen we het niet maken, wel makkelijker: https://www.belastingdienst.nl/wps/wcm/connect/bldcontentnl/belastingdienst/zakelijk/overige_belastingen/belastingen_op_milieugrondslag/tarieven_milieubelastingen/tabellen_tarieven_milieubelastingen