On rare occasions they run a steam train to the museum. Fun, albeit useless, fact: it used to take the southern way around.
#trainstr
Sjors Provoost
sjors@sprovoost.nl
npub1v25j...exw3
https://github.com/sjors/
Book: https://www.btcwip.com
Podcast: https://bitcoinexplainedpodcast.com/@nado/episodes
250 pages into its adventure, Fable still believes it's living in a Cypherpunk adventure game internet simulation. Full of captchas, throwaway email services that PyPy blocked, looking for US number that Yahoo doesn't block. It even knows about BTCPay (from memory). Should it get some Bitcoin?
https://cdn.sanity.io/files/4zrzovbb/website/8359003bfb12a2f01ce84ad3df1d3a3e2f15a8eb.pdf
I had my clanker implement the Liquid inflation attack as a Python functional test, and then explain it to me with some diagrams.
A functional test is a good way to catch hallucinations in the attack scenario. When responsibly disclosed, it also gives maintainers a way to quickly assess if they want to read your slop.
This is safe to publish because the attack involves transactions that are consensus invalid for both old nodes and future fixed nodes. No blocks are mined currently, so new attacks won't get mined. Even if they did, they'd get reorged along with the attack block once operations resume.
Gist
Elements rangeproof-cache collision functional-test reproducer
Elements rangeproof-cache collision functional-test reproducer - README.md
How long can you keep a lightning long offline, if there's no HTLC in flight, before someone can screw you over? Asking for a friend who doesn't like binaries.
Oh by the way, how's the Sztorc-fork going?
Happy K-Day!
Bitcoin Fork Monitor
With permission, hopefully :-)
View quoted note →
If you're one of the cool kids who use wkd to fetch PGP keys, I just bumped the expiration date for mine:
gpg --auto-key-locate clear,wkd,nodefault --locate-keys sjors@sprovoost.nl
You can also ask your agent to fetch the branch for each open pull request, as a backup for work in progress.
View quoted note →
The world's most populous dictatorship.
View quoted note →
No, the US is not accusing Europe of forced labor. EU foreign minister Kallas is lying, as usual.
What the White House is saying, is that the EU is not doing enough to prevent the import (and re-export) of products involving forced labor.
That's hypocritical, but also true. The EU Directive to fix that won't take effect until next year. Ironically this will impact American companies, presumably triggering more tariffs.
The White House
Actions by the United States in the Investigations under Section 301 of the Trade Act of 1974 of the Acts, Policies, and Practices of 60 Economies Related to the Failure of Each Economy to Impose and Effectively Enforce a Prohibition on the Importation of Goods Produced with Forced Labor
MEMORANDUM FOR THE UNITED STATES TRADE REPRESENTATIVE Subject: Actions by the United States in the Investigations under Section 301 of ...
I'll be impressed if a single miner produces a block that's guaranteed to be orphaned by normal nodes, except by accident* while attempting to virtue signal.
* = e.g. running Knots initially to just signal support, forgetting to switch back to Core once signaling is mandatory. Not everyone understands that the consequence of mandatory signaling is that your node won't see the most proof-of-work tip.
View quoted note →
