Shameless plug for a three year old podcast episode: https://podcast.sprovoost.nl/@nado/episodes/utreexo-w-ruben-somsen-nado-15
Note that it's already more than 4x more expensive to use this method of data publication:
* it doesn't get the 4x witness discount
* there can only be 1000 bare multisig outputs in a block, which the Bitcoin Core mining algorithm handles by treating each sigop as if it's 20 bytes
You could maybe encourage miners to bump -bytesperblock to 50, but there's no perfect number there. Finding the economically optimal block given two constraints is very hard.
Shameless plug for a three year old podcast episode: https://podcast.sprovoost.nl/@nado/episodes/utreexo-w-ruben-somsen-nado-15
My five sats on the proposed disabling of bare multisig in relay policy. I don't believe it's useful for Bitcoin Core to do this, because there is strong financial incentive for users of bare multisig to convince node runners to keep it on.
If enough nodes keep relaying them, these transactions will reach miners just fine. So it won't slow down UTXO set growth at all. In that case it's better for all node runners to know what's about to appear in a block (for better fee estimation and maybe to detect pinning attacks if you use lightning).
This is more or less the same dynamic as Peter Todd's attempt to make full RBF a fait accompli, but in reverse. If he succeeds in getting enough relay and mining of full RBF, there's no point in Bitcoin Core holding on to -mempoolfullrbf=false by default.
If you really want to stop these transactions, a soft fork is the only way. But I'm not sure if that's worth it. Perhaps this energy is better spent on developing Utreexo, which makes the entire problem go away (and creates a few new ones, but hey, such is life).
Or even from Nostr: https://gitlab.com/soapbox-pub/mostr
(except if their instance admin bans the bridge, then you'll have to run one yourself)
#WeAreAllFediverseAdjacent
RSS is easier to use and more robust, but not interactive.
Or even from Nostr: https://gitlab.com/soapbox-pub/mostr
(except if their instance admin bans the bridge, then you'll have to run one yourself)
#WeAreAllFediverseAdjacent
I still use it occasionally for friends and family. It's closed otherwise and I only get follow requests from crypto celebrity impersonator bots.
You didn't even need to be randomly suspended!
Relevant for your multisig setup: https://www.youtube.com/watch?v=hiwaxlttWow
And more pools with the same checkboxes isn't going to help.
And therein lies a very serious problem. Too much hash power in Checkboxistan.
I'm not worried about Foundry knowing about their own miners, but I am worried about a pattern of US miners seemingly feeling the need to use a KYC pool.
But then I've always been in favor of keeping US hash rate below 10% and cynically applaud the likes of senator Warren whenever they come up with another economic suicide plan with that effect.
We do, but in this case we just need miners to use a different pool.
"bright future under the compliance" - Antpool nostr:note1fkqfuhn3tr9l7d3czcuslf3vays2f2y6znls4kwhyg4hyllu5dkqkeftcg
They called it a "bright future under the compliance" on Twitter.
Ah yes, a book about #bitcoin. Can't have that!
cc nostr:npub1dc84762hpnp0y4jcvjcgwt8l7sepng93j3hg63hfm80ph6kt82eqktjwqd
What could this dangerous package be?
