The transcript of @lukedashjr at LA BitDevs on the SegWit/PSBT vulnerability is up. https://diyhpl.us/wiki/transcripts/la-bitdevs/2020-06-18-luke-dashjr-segwit-psbt-vulnerability/
politics, anti-racism
This past month or so has made it absolutely clear there is systemic #racism, and that it is now considered socially acceptable to be racist and discriminate openly.
But it's already illegal. So the question is, when will the government prosecute? Or is this anti-"white" racism the new norm in #America?
Thanks to @[email protected] for merging my BIP 8 improvements and adding me as a co-champion.
Hopefully just in time for finishing it up for deploying #Taproot to #Bitcoin!
https://github.com/bitcoin/bips/blob/master/bip-0008.mediawiki
The ordination of Rev. Mr. Luke Petrizzi begins... THIS is Catholicism. [email protected]@twitter.com
https://youtu.be/Qwnk4Ymc9KM?list=PLHMNwr4DRvzlVG07QEXFRbyMPXMKFi73V
How mining is supposed to work...
I hear bcashers are having a schism over whether to hardfork every 6 months or every 9 months.
Going to have to side with the 6monthers:
If you make it every 9 months, then babies conceived celebrating hardfork N will put the women in the hospital for delivery right when HF N+1 is activating, reducing manpower by half if something goes wrong...
/s
#Bitcoin Knots 0.20.0.knots20200614 released! 🎉
The Defense Distributed Liberator ported to a 7656 character script for the OpenSCAD compiler and printed on a T-shirt (or if you prefer, a hoodie) https://teespring.com/liberator
"On Bitcoin transaction sizes" by Dr. Alec Virtu https://link.medium.com/vKksrO2Ck7
The technology does not exist today to verify an implementation is faithful to a specification.
Due to the nature of consensus systems, it is necessarily the implementation that is authoritative.
To compete with Core, fork the consensus code.
Anything less is likely buggy.
@[email protected] wrote:
> Why hasn’t the Bitcoin community formalized the consensus rules of the bitcoin protocol into a formal spec?
> The cynical view is to prevent competition with Core
I am a community-paid #Bitcoin developer working on Bitcoin Core and many other parts of the ecosystem.
You can help fund my public Bitcoin work by:
1) Sending me bitcoins - contact me for a per-transaction/unique address!
2) GitHub Sponsors: https://github.com/sponsors/luke-jr
3) Patreon: https://www.patreon.com/LukeDashjr?utm_medium=social&utm_source=mastodon
Due to keyserver reliability issues, I have updated my #PGP key hosted at https://luke.dashjr.org/myself/luke-jr.asc to the latest version (and just extended expiration by another year).
Please ensure it matches the key you already have, and/or otherwise verify my key fingerprint from at least a few sources!
For reference, fingerprint should be E463A93F5F3117EEDE6C7316BD02942421F4889F
Interesting... Broke immigrant brothers manage to acquire 75 rentals in a year:
https://www.businessinsider.com/a-step-by-step-guide-on-how-to-be-a-successful-landlord-2020-6
The severity of this may be exaggerated:
Since this vulnerability can only be exploited by tricking the user to sign twice, there's a fundamental unfixable attack here anyway:
If they can trick you to sign twice, they can probably also get you to send the full amount twice too.
Bug in #Segwit, which can be a security vulnerability for hardware wallets and similar.
#Bitcoin isn't vulnerable itself, but users of Segwit wallets should ensure they upgrade if affected, before *sending* any new transactions.
(The solution is to not use a new technical-internals feature Segwit introduced.)
Faithful lay Roman #Catholic* convert, husband, father of 7 children, and #Bitcoin Core developer
INTP
* I completely disavow and condemn the pedos who currently control Vatican City. They are NOT Catholics. (Catholics have been required to reject them as heretics, since long before the pedo news broke.)
#PGP key fingerprint (do not trust this alone!): E463A93F5F3117EEDE6C7316BD02942421F4889F