In episode 18 @AaronvanW and I discuss the Erebus eclipse attack: https://nadobtc.libsyn.com/erebus-attacks-and-how-to-stop-them-with-asmap-nado-18
But Spotify has “way more advertiser demand for [SAI] than inventory to satisfy it,” said Jay Richman, head of global ads business and platform at Spotify
Should read: “We can’t covert enough of our customers to use our podcast player”
I’m not eve sure they’ll take JRE RSS feeds offline come Dec 1st
I definitely didn't expect the extent to which they're going to not take down things in the future just because they received a DMCA notice:
Native segwit (bech32) (p2wpkh) (BIP84) wallets are the default in Joinmarket, as of just now, i.e. it is in master branch. Release soon.
This means that if you start the software today you will create those wallets and use the joinmarket bot pit for those wallets and create coinjoins with them, by default; you can set `native=false` in the config if you want, however. See docs/ directory for details.
Please publicize this where you can for users' plausible deniability when starting new bots.
@anita I'm trying to connect directly to your tribe node, but it doesn't seem to be publicly reachable. According to 1ml it's at email@example.com:9735
In episode 17 @AaronvanW and I talk about eclipse attacks on #bitcoin nodes: http://nadobtc.btc.libsynpro.com/bitcoin-eclipse-attacks-and-how-to-stop-them-nado-17
I managed to get it running against my own Lnd node using sphinx-relay. It's still rather tedious, so I find myself watching debug logs and manually managing channels so the podcasters get their minutely sats. But it's very promising.
The Van Wirdum Sjorsnado now also shows up in the Podcast Index: https://podcastindex.org/podcast/1329688
New chaincode podcast out, with Murch.
Little addendum on the calendar servers, as Peter Todd pointed out on the bird side, there's multiple and they're run by different people. Some of them even take lightning donations.
In episode 16 @AaronvanW and I explain OpenTimeStamps and how it played a small role in the US election, because of a signed email about coffee:
At PR review club I learned about BIP-50 where a change from BerkeleyDB to LevelDB unintentionally caused a chain split because LevelDB could handle blocks w more to inputs.
Incidents like these explain why core development is so conservative but as a developer, I do find it comforting that even the best projects make mistakes. A rite of passage for every young engineer is to accidentally break prod (for me this was at an AdTech company so maybe it was actually a good thing?)
Ruben @RubenSomsen joined @AaronvanW and me again to explain utreexo, a way to sync nodes with extremely little RAM, at the expense over more bandwidth: https://nadobtc.libsyn.com/-utreexo-w-ruben-somsen-nado-15
In episode 14 @AaronvanW and I explain Assume-UTXO, as well as some earlier performance improvements like headers-first and assumevalid.
Episode 12 with @AaronvanW and @RubenSomsen: https://nadobtc.libsyn.com/the-perpetual-one-way-peg-nado-12