3 ms·
The far bigger threat is not the code going away but it being censored at the network level. Already, a single miner has censored tornado transactions, that bei
by paulpauper 4y ago
The far bigger threat is not the code going away but it being censored at the network level. Already, a single miner has censored tornado transactions, that being EtherMine, which has 28% of hashpower. If the next two biggest miners censor it too, assuming hashrates do not change, then all tornado funds will be frozen. Very bad situation for tornado users. POS may change this but no guarantee. People should be mad at EtherMine, not at the US govt.
- HappyTypist 4y agoNo, it won't. A single miner has chosen to *not include* TC transactions in their blocks, but they are not *censoring* TC transactions in the sense that they will validly build upon blocks built by others that feature TC transactions. As long as 1% of miners include TC transactions, even if 99% choose to not include, TC transactions will still be part of the blockchain, albeit not as timely. When miners start actively REFUSING to build on blocks that feature TC problems, that is an issue. For what it's worth, the ethereum development community is actively exploring features that make active censorship a network violation (with censored blocks not being accepted by the network), although this is an area of active research. Current proposals include PBS+crList.
- edf13 4y agoCan you point me at the relevant discussions for this (exploring features to prevent censorship). It’s an interesting area…
- throw101010 4y agoIt's also as simple as paying the appropriate fees for including this transaction... everyone has a price, even (especially) miners.