Bitcoin Core 0.19.0(.1) was released!
Release notes: https://bitcoincore.org/en/releases/0.19.0.1/
Testnet blocks have been arriving at a crazy pace during the last ~36 hours. More than one block per minute and lots of stale ones: https://tbtc.bitaps.com
In case you ever need to rename a variable across multiple (e.g. 10) git commits:
git rebase -i HEAD~10 --exec 'git diff --name-only --diff-filter=AMC HEAD~ | xargs sed -i "s/BEFORE/AFTER/g"; git commit -a --amend --no-edit'
To edit commit messages:
git filter-branch -f --msg-filter 'sed -e "s/BEFORE/AFTER/g"' HEAD~10..HEAD
I needed this for (and dozens of commits on top later): https://github.com/bitcoin/bitcoin/pull/15382#discussion_r341094876
Practice your Dutch: https://youtube.com/watch?v=MDoIaMZIqZM
I added my own answer, though it seems to be wrong.
@sjors lol I was going to make the exact same post you just did on twitter; Laura Shin's just released podcast with Joerg Platzer placed an ad for cyphertrace (ridiculous dystopian 'crypto must be clean' drivel with robotic inhuman voice to match) right in the middle of Joerg explaining that fungibility and privacy are essential properties of money 😂
Banks are reverse ransomware.
Ransomware locks you out of your data and requires a payment to release it.
Banks lock you out of your money and require your private data to release it.
In both cases, there is no guarantee that they will honour their side of the contract, and sometimes, they just don't.
Today I learned far more about IPv6 than I wanted. It turns out my Bitcoin DNS seed (along with few others) was not reachable for nodes with only an IPv6 address. That's fixed now.
Though the people affected can't read this post anyway, because my Mastodon instance isn't reachable either :-)
This is my new Mastodon profile. I will boost it from my old one, firstname.lastname@example.org
Thanks @orionwl for hosting this :)
(I consider mastodon.social to be anti-free speech, hence the move).
[ann] Bitcoin Core 0.18.1 Released!
I'm decentralizing my income a bit by launching my own LibrePatron instance. It's best seen as a way to bribe my priorities; although I have sufficient paid work, I find that it distracts me from open source Bitcoin development.
All proceeds pass through recklessly experimental software, such as my hardware wallet related pull request(s). That means I catch bugs before you do!
3: Much more famous and so not as interesting of a recommendation, but I'm right now finishing listening to this interview with Poelstra; it's one of the better ones he's done, I commend the hosts for letting him just go at it in detail ( the first section is all about miniscript and super interesting, then it broadens to other stuff, also I get a mention, blink and you'll miss it 😂 ):
3/3 (unless I think of more!)
Rockstar @FelixWeis@twitter.com buying bitcoin via Lightning at an ATM. #LightningHackdayHK at @email@example.com
I wanted something bigger to run my node on. Is it overkill? Yes! Do you really need that much CPU cooling for a server? Maybe.
Before: Khadas VIM2 Max with 256 GB SD card for blockdir, which ran out of space a week ago. It was also just unstable: randomly declaring blocks invalid and crashing, especially when connected to network cable. https://www.khadas.com/vim
After: Intel i5, 32 GB RAM, 512 GB SSD (using PCIe connector at the bottom of the motherboard). Case: Thermaltake Core V1
I gave an updated presentation at Advancing Bitcoin last month: https://vimeo.com/316634495
HWI (works with Bitcoin Core 0.18.0 which is still pending release): https://github.com/bitcoin-core/HWI
For anyone interested, this is a very thorough writeup of the CVE-2018-17144 bug, including links to the relevant code: