93.1% Gut Feeling. 6.9% FA. I ate gut gut fruit and now I have a knack for spotting next big thing in crypto before it skyrockets | 21K followers on Insta | NFA
If you weren't living under a rock, u must have heard that @Injective_ Protocol recently raised a whopping $150M despite being in a bear market. Here's a thread detailing my in-depth analysis of injective and why I believe it will soon rank among the top Layer 1 Blockchains.
🧵
@llamaonthebrink > The Zcash bug is a win for the “unauditable supply” argument against full base layer privacy by many Bitcoiners.
Wrong. Formal verification is coming and will allow us to have a mathematical guarantee that there are no bugs in the ZK circuits.
Zcash FIXED an inflation bug & you are all panicking...
Stop overreacting! What matters is that the good guys caught it first: ZEC's team is competent!
It was always known this could happen; it even happened before
Privacy is too worthy a cause to get dragged down by ignorance
Zcash has unparalleled cryptographers, security engineers, and security researchers. And the community is heavily focused on continuous improvement and hardening the network. That's why it engages world class security researchers to look for bugs. And that's why the recent potential exploit was found. It wasn't by accident and it's a vote of confidence, not a cause for alarm. When it comes to any L1, there will be bugs. What's important is that there are world class researchers focused on hardening the network and staying ahead of the bad guys. This has always been and always will be the dynamic of building software that is secure. Onward.
There will be bugs.
Pretending otherwise, is delusional. Software security at its core is a never-ending race between the good guys and the bad guys. The good guys always have to stay at least one step ahead of the bad guys. AI doesn't change this game of cat and mouse, it just accelerates it.
Every piece of software has to run this race. There's no escaping it and there's no better team in the world to run this race than the team working on Zcash. Onward.
Finding a bug isn't a security failure. Not looking is.
Zcash has a team of world-class security engineers and cryptographers working on it 24/7.
In the AI era, every protocol will face this test. Most aren't prepared.
since this comes up every few months, a refresher:
- first, there *is* a way to prove the bug wasn't exploited, more on this below
- the fundamental tradeoff in a strict privacy pool is that if there's a bug, it could be utilized without immediate detection. this is the same for almost all privacy protocols without audit keys and with circuits
- it's similar to any other crypto bug, like defi, in that something could be exploited and moved to a different chain. there are bugs lurking all over defi, blockchains, and all software at all times. the difference is that given the privacy, it's obviously harder to detect timely
- note that this has always been the case with any of these things (and zcash isn't unique here, the other notable privacy project you're thinking of also has the risk of counterfeit bugs), so nothing is "new" except for the fact that understandably not everyone knows the technical tradeoffs
- in zcash, you have guardrails to detect this so the supply would never increase past 21M *but* the ppl in that pool would get shafted unless there's social consensus, which would admittedly be messy
- recently, the zcash core teams have been increasingly using advanced tools and hiring external security firms to audit themselves to keep improving security
- this is also why it's harder than it sounds to just add privacy to an L1 or L2 (without audit keys) because you want a high concentration of security researchers and cryptographers looking at this at all times. it's also why "dino" projects are interesting because they've survived this long.
- now with this new effort, one of these was a hit and the team immediately patched the bug they found
- you can be reasonably sure that it wasn't exploited given a number of signals, but you can't definitively prove it unless either:
i) the turnstile is triggered
ii) the wallets start pointing to a new pool to migrate (there have been 3 such migrations in the past for example) which would then prove this
luckily, there has been work on creating a new pool that's provably sound, formally verified, and quantum proof this whole time with @TachyonZcash (which is also how I first got introduced to zcash)
so once that migration is done, you will have full certainty
@solidintel_x no, you just completely made that up?
no it is not down in any way. almost certainly you connected to a bad node.
this is completely false. source: actual dev
you can now use your zec to cast private votes on protocol features
1 zec = 1 vote
coordination without central authority, enabled by encrypted money, zcash is a bastion of crypto's truest ideals
and we have a shit ton more cool stuff coming
my favorite way to use crypto as my bank recently:
i) shield zec in @zodl_app
ii) use crosspay (uses near intents) to do txns in stables on Solana when needed
a private swiss vault you can spend from
zcash x near x solana, the dream team