@ZmnSCPxj Coindesk [1] says this and I'm wondering if the quote is correct. I just want to make sure I'm not propagating invalid blocks of text.
Background: I'm writing a few paragraphs about pseudonymous development at https://rosenbaum.se/btcphil/ and I think you're an interesting example.
RT @knutsvanholm
#Bitcoin Alles durch 21 millionen
♾️/21M
@volker_btc @KonsensusN @JeffBooth @FractalEncrypt
Jetzt im Deutch!
Kauft hier bitte! 👇
https://konsensus.network/product/bitcoin-alles-durch-21-millionen/?ref=knutsvanholm
Looking for the code fix for this bug (CVE-2010-5141), but can't find version 0.3.5 which is stated to be the version with the fix.
What commit represents 0.3.5?
There's no tag for it, nor are there any traces of that version in the history of setup.nsi or serialize.h.
https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2010-5141
As far as I can tell there were at least 2 different patents on point compression in elliptic curves (that's the thing that lets us have a public key which isn't ridiculously large, like 64-65 bytes, by basically just treating the X coordinate as public key, and fudging Y). One by Vanstone and etc. expiring 2014 and another actually owned by Hewlett Packard which expired in 2018. It looks like they both used clever mathematical tricks to remove the need for even one bit.
(1/2)
So Chris Larsen of Ripple is attacking #Bitcoin with every organization that will sell out to him.
At least we know that @Greenpeace is a political mercenary.
@harding But this only applies if there are enough txs in the mempool. If mempool is empty, fee-sniping always makes sense. On the other hand, if mempool is empty, fees are probably so low that sniping doesn't matter and it's better to turn the miner off anyway.
Reading about two countermeasures against fee sniping in this great article by @harding https://bitcoinops.org/en/topics/fee-sniping/
Couldn't a third measure be for wallets to discourage fee overpaying? If the fees are more homogeneous, fee sniping makes less sense.
Eg: "You're trying to pay 10x more in fees than what's required to get into the next two blocks. Should I change the fee to 3x to discourage miner misbehavior"
Trying to sort out the terms: security
-assumption
-guarantee
-model
@lopp writes "Every security model has two main parts: assumptions and guarantees. If the assumptions used as inputs hold true, then so should the guarantees that are output by the model."
y'all agree?
Lopp's article: https://blog.lopp.net/bitcoins-security-model-a-deep-dive/
From what I understand, AOPP doesn't work for general BTC addresses. It requires a single key address. Exchanges thus force users into certain wallet policies. Have they even looked at BIP322?
https://gitlab.com/aopp/address-ownership-proof-protocol/-/tree/master
https://github.com/bitcoin/bips/blob/master/bip-0322.mediawiki
@mullvadnet Got help on Twitter from ajtowns https://twitter.com/ajtowns/status/1484238854995742725?s=20
IRC/VPN issue: Why can't I connect to libera using HexChat on debian 11 when connected to @mullvadnet VPN? The following cycles every 10s. It works fine if I disconnect from Mullvad. Is it "Couldn't look up your hostname"? If so, what can I do about it?
I solved @robot__dreams first Bitcoin-flavored cryptography challenge (https://gist.github.com/robot-dreams/669c13bc724fdeb9af8460c9b64d5665) with the help of @kalle Schnorr Basics explainer (https://popeller.io/schnorr-basics).
Here's a write-up (and spoiler).
As a follow-up on my Schnorr Basics post, I just published a walk-through of the MuSig2 protocol for Schnorr multi-signatures.
With illustrations to make it look less intimidating!
More moronic behaviour from the Binance casino:
https://bitcoin.stackexchange.com/a/111441
Give them a taproot withdrawal address, they *literally change the address*, just changing the segwit version from 1 to 0, (valid because P2WSH length) because ... lol?
People sometimes say 'why do you care if the exchange does shitcoins?'. This is why. They just burned ~7.5K of this guy's money. He'll probably get it back because they're so rich they don't care, but he'll have to argue with them first.
Customer "support": https://ibb.co/tZq4txt
Address where the permanently destroyed money went:
https://mempool.space/address/bc1qfdjlc5p92pxzvacgc5nhn3vgtt54e98472ymxgtejaa0ttdx8lkqgy3xdq
In 2017/2018 I got very militant about calling Coinbase traitors and incompetent and scumbags and so on; they all out attacked Bitcoin.
This kind of behaviour is a bit different: it only indicates they care so little that one dumbass decision from one noob backend engineer ('oh, if I replace p with q, it works!!') is the level of attention they pay to Bitcoin.
Bitcoin. Opinions expressed are someone else's. Author of Grokking Bitcoin https://www.manning.com/books/grokking-bitcoin