How do they enhance coinjoins?
I'm fully stocked on Cheezy dibbles. I'm prepared for Elon to drop the big bomb about Fort Knox not having the gold.
https://nostr.download/7682beea26483e3564b3cd6959f337ac3d3f22378567084a93c5ce0e217e1555.webp
...The USA defaulted on their gold contracts back in 1971. The amount of gold you are "auditing" the Fort to check for is literally zero.
We are faced with the problems of loss of privacy, creeping computerization, massive databases, more centralization - and Chaum offers a completely different direction to go in, one which puts power into the hands of individuals rather than governments and corporations. The computer can be used as a tool to liberate and protect people, rather than to control them. - Hal Finney
The vote was unanimous, 69 to ZERO.
Abolish democracy.
Peach GroupHug⦠A batching service that does not require coordination
We processed the biggest Peach GroupHug release transaction of our history by batching 106 PSBTs like itβs nothing ππ
https://mempool.space/tx/eaff84bbf480f83bfa67fd286955c82777cba42e5b4395ddcf1a6daa1265de5b
How does it work?
1 bucket with as many participants as possible. The batch happens earliest after 24 hours and the minimum fee rate used by the bucket is the half hour fee.
The mining fees used are the half hour fee at the time when the seller confirms the payment. The more participants in a batch, the more you will save, since the peach fee output effectively gets shared among all participants.
Check our FOSS code
https://github.com/Peach2Peach/groupHug/tree/6f1cb023c972eec1fc73989e39a53378313d7394
Learn more:
"Grouphug" is basically a huge payjoin that collects Peach's fee - nostr:nevent1qqs2ce5kfcdsy872qzr6tg5jwn408p5545apcv2muezehe3vwv89xlspz9mhxue69uhkummnw3ezuamfdejj7q3q5369wu3wzzar5fclhecyqfv683x69n6nhlg7rxqnsg2dydgxflpqxpqqqqqqzsvxw3t
Why do these numbers make you "pretty confident"? Everyone else who is looking at their node can see that your censorship strategy backfired, making OCEAN the least profitable pool to mine with: nostr:nevent1qqsykkral0a5u04hqr2tapaxwgfkssstew2uw3n59e0qflz7lfhqutqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqtnhnut6pdympg26g2z0x3vs2f5kswuvf3hxgju8qtkdkxddr34vpsgqqqqqqszgcj88
It should be clear that approach failed by now, your pool is simply getting outcompeted.
It's a soft fotk. Here's the code to do it: https://github.com/rot13maxi/bitcoin-purifier
OCEAN controls less than 1% of the hashpower. It's safe to conclude their censorship project failed, as expected.
Not if your fork had 51% of the hashpower, the Bitcoin Pure chain would reorg the Bitcoin Core chain.
Yes, even empty blocks are valid and reorgs are valid blocks as well. However, these blocks are not economically competitive in the long run (unless you have a massive short position on Bitcoin...)
Txs with invalid signatures will create an invalid block, so I would say they are "rejected" rather than "censored".
The sample size of the picture is small, so the skew might not be that bad over time. However, the OCEAN's failure to attract >1% of the total hashpower is a revealing fact about the market's preferences.
Then why don't you fork the network to stop the harm?... People seem to be very confused and running Bitcoin Knots instead of Bitcoin Purifier, which actually enforces the censorship they intend - https://github.com/rot13maxi/bitcoin-purifier
Censorship hurts miners in both the short term and the long term.
If there are transactions that actually harm the network (such as those causing excessively long block validation times), those must be made invalid with a soft fork.
This goose metaphor is a steelman for why the block size limit shouldn't be increased, it doesn't support the conclusion that miners should censor Bitcoin transactions.
Yet another solid rant by nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4spzdmhxue69uhhwmm59e6hg7r09ehkuef0s9jd25.
Spam must be dealt with, not encouraged.
"Dealt with" is a euphemism for "Censored". Bitcoin is a free market engine that kills off censoring attackers:
That was fake news, which was verified by this bounty: https://x.com/ob_hodl/status/1300429481711153152
Roughly ~40 users participate in each coinjoin round I coordinate for nostr:nprofile1qqsf80gvdu7vhtj88z9srtrvuzevqyc3fh9yczxkufcj6nlhzsz68scpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqg0waehxw309aek7mr0vdhjumnvmxmjyh users. Tough times for Monero users.
Btw there's no way I can determine the true number of users - even as the coinjoin coordinator. This is just an esimate from on the amount of inputs in each coinjoin tx based on standard client behavior.
Roughly ~40 users participate in each coinjoin round I coordinate for nostr:nprofile1qqsf80gvdu7vhtj88z9srtrvuzevqyc3fh9yczxkufcj6nlhzsz68scpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqg0waehxw309aek7mr0vdhjumnvmxmjyh users. Tough times for Monero users.
