Closed ghost closed 3 years ago
actually, this was a difficult problem even before EIP-1559—I realize now it's become even harder.
There is not any straightforward solution to this. it's a consequence of the fact that Anonymous Zether lives within Ethereum, but Ethereum doesn't support privacy. It will be a hard challenge for any implementer to come up with a solution to this.
make sense? let me know.
Yeah, thanks for your reply! Tornado.cash has Trusted setup. Anon ZETHer more attractive for me. About EIP-1559 agree, its problem for this concept, but we have Polygon, BSC). These networks are also more attractive in terms of gas costs and tx speed.
Tornado.cash has Trusted setup.
This is true, but it's a separate issue. That's about the actual protocol is constructed, whereas here we're talking about how to submit transactions from EOAs.
About EIP-1559 agree, its problem for this concept, but we have Polygon, BSC
Good point. You could try the miner fees trick on those systems.
Hey, in client.js:
const throwaway = web3.eth.accounts.create();
And this new acc sign transfer transaction then (as i understand because "gas linkability"):web3.eth.accounts.signTransaction(tx, throwaway.privateKey)
But in real network, where gasPrice != 0, how it can be?