pull down to refresh
0 sats \ 0 replies \ @kruw 24 Apr \ on: The Fall of Ethereum bitcoin
Why is this topic posted in the 'Bitcoin' territory?...
Enabling coordination using the BTCPay Server coinjoin plugin was as easy as clicking a checkbox, but it's no longer maintained. Running the coordinator packaged with Wasabi requires command line knowledge, which I struggled with at first. The lead dev has plans to make it an easier experience.
Test software and provide feedback, senior devs aren't able to view their software with the same perspective as new users. Identify the "lowest hanging fruit" that bothers you and search the project's github repo to see if it's already been addressed.
Ethereum is the shittiest because it should have died completely when Vitalik hard forked the entire chain to censor one smart contract.
But the results for the developing world are already veering into catastrophic territory: Only 18% of Mexicans, 13% of Brazilians, and 8% of Indonesians are still coping.
This data doesn't add up, guessing at random would achieve the correct answer 25% of the time.
Definitely @supertestnet
Yes, but connection info was updated to https://coinjoin.kruw.io/
Recipient needs to share their signed UTXO with the sender to finalize the payjoin transaction. Hence, payjoin cannot be used with untrusted senders.
This is a solved problem: The receiver doesn't give any UTXO information out until the payjoin sender has already provided a regular presigned payment as collateral.
Since the spender has already forfeited their coins (without learning any of the merchant's inputs), the receiver can simply reject the payjoin request and take the customer's money as a normal payment without revealing any information to them, causing the attacker to lose all their money.
@1440000bytes is a Monero retard with a terrible track record of purposely publishing false information about coinjoins.
Bitcoin is here to abolish democratic governance, not support it. Democracy is when the parasites overwhelm the productive host population and leech taxes from them.
Bitcoin fixes this because there is no voting allowed. Proof of Work is all that is allowed. The productive are not vulnerable to the opinions of democratic parasites: The only have to work harder than the democratic parasites to defend the chain from 51% attacks.
If you know someone's address, presumably it is not empty
Dust attackers only target empty addresses that have already spent their coins.
If it is empty, presumably it will never be reused.
That's the point: Dust attackers purposely refill it so it will be reused by a clumsy victim.
❌ This is the flaw with Full-Agg for protocols like CoinJoin or PayJoin, Full-Agg introduces complexity.
Coinjoins are already interactive, so there's no new complexity introduced.
You are unfairly targeting innocent Bitcoiners who want to protect their privacy. A coinjoin transaction combines inputs from multiple Bitcoin users. This means your policy of censoring every transaction participant causes unnecessary collateral damage.
The coinjoin coordinator running on my node accepts 2,500+ new BTC and confirms 20,000 BTC in total volume each month. It accepts exactly zero ETH.