zcash has won. nobody cares for or uses trash crashnero (USELESS)
>>62208894bullish for xrp
>>62208894Strange marketing, moses.
>>62208894Random shit alts(not. Just zec) are pumping, probably top signal
If devs can build a backdoor, then they will build it. Apparently Zcash shielded addresses have full view keys as well, so I've to correct my article. Monero is not worse, but just as bad as ZEC if it introduces CARROT. And these full view keys are a huge weakness, not because "if they exist regulators are going to request them", but because "if devs can put a backdoor to steal them, then they will put the backdoor to steal them".Also by law, in US, they can put the backdoor and be forced to never admit it even in front of their boss. So you know Cake wallet? Vik's dev could be under a gag order to put a backdoor in the code that collects full view keys. And now you may say but hey, if they did that I'd see it in the code, the wallet is open source. Not really, because as long as the code is not reproducible then they can sneak that backdoor in the pre-compiled binaries, which are the ones 99% of people use. The backdoor would then be perfectly undetectable.As a reminder, Captain Dero used this trick to put an inflation vulnerability in Dero which he exploited to refund himself the entire 2M premine at the end of the 2021 bull cycle. How did he do that? In the first 10 months of mainnet Dero wasn't reproducible. The precompiled binaries had the bug, the ones compiled from source did not (because the source code was clean). The bug in the precompiled binaries allowed sending negative amount transactions. Only Captain knew about this bug. Inflation bugs are exploited right away so it's very risky to let them float, but Captain could afford it because it was present only in the precompiled binaries, so one had to go inspect binary code to find it. Moreover, he could also easily detect potential exploits simply by running a node compiled from source. So he waited up until the very end and in October 2022, he exploited his own bug, gave himself 2.2M coins, and then published reproducible code shortly after.
>>62209041He had to move to reproducible binaries quickly because anyone running a node compiled from source could have detected his transaction as well and could have gone looking for the bug to exploit it himself by decompiling the pre-compiled binaries.The lesson here is that as long as something like a full view key exists, and a user can share it, then devs will build non reproducible wallets with government backdoors to steal that full view key. But if the protocol doesn't allow this then the risk is non existent. If no full view key exists, then there is nothing to leak. That's why I personally wouldn't use any coin that has optional privacy or full view keys, because most likely 99% of people's wallets are transparent as they use precompiled binaries that probably have a backdoor put in there by some dev under a gag order. And those few ones that compile from source make no difference because they are a small minority whose flows can be extrapolated from the rest.
good things are happening in Zcashland. Tachyon is a game changer.
>>62208897
