I have a golden rule:
If I stop believing in myself, I’ll lose.
Sometimes I forget about him, which is my main defeats.
Believe in yourself and you will win more often.
Good luck!
ok zcash guys its time 2 look an other coins like octra, nock and zama
remember: we have more opportunities onchain like ZEC but without cabal, zionist buddies lobby and BETTER TEKK.
sorry. you're still early tho.
Everyone's reading this as "zcash got exploited by an AI." That's not the story.
The story is in one line of their own post: because Orchard is private, there is no way to cryptographically prove whether the bug was ever used before they caught it.
A white-hat found it first. good. but the actual lesson isn't "AI breaks privacy" - it's that privacy built as a black box gives you a class of bug you can't audit after the fact.
And notice their fix: a new pool with turnstile accounting so anyone can verify the supply. They're not patching privacy. They're adding verifiability to it.
Everyone's fighting about ZK vs FHE. Then MPC. Then TEEs. Then which hybrid wins.
Wrong axis.
The cUSDC freeze last week proved it: Zama's encryption worked perfectly and the contract still froze. The crypto was never the problem. Where the value lived was.
Update: @octralabs will be deploying wrapped OCT and the native bridge on HyperEVM in preparation for listing on Hyperliquid spot markets. We aim to finalize the process this week. Perps will probably take longer and depend on spot volumes, Nova and the Hyperliquid community.
May took them away:
@bullx_io@fantasy_top_@syndicateio@EverclearOrg
and probably a few more we didn't even notice
No scam, no hack. The market just stopped paying for last cycle's narratives.
Metas come and go. Infrastructure with a real foundation stays.
Maybe it's time to look less at the losses and more at projects building an actually useful product.
@octra fits that frame.
The detail everyone will skip: the freeze even hit the right funds. Compliant protocol, targeted order - and they still got no notice and had to pause cUSDC/cUSDT/cWETH wholesale.
The encryption worked. The lever just sits on the base asset, not with them.
Confidential state /= settlement sovereignty.
Thanks to @zachxbt, we found the root cause and will be taking the appropriate actions to unblock the situation. Tldr; this has nothing to do with Zama, or privacy.
The issue stems from an address related to the Overnight Finance hack, which deposited over ~$12.5m USDC into our confidential USDC wrapper contract. Back when they did, their address wasn't on any sanctions list and was not flagged by our KYT tools. However, a court order yesterday night placed a restraining order on various wallets linked to the hacker.
Since there wasn't much utility yet for the cUSDC wrapper, there were very little funds in it, and as a result the vast majority (>99%) of funds in the cUSDC contract came from that single hacker's deposit. Because of this, the court order asked to freeze our wrapper contract to freeze the hacker's fund.
So the sanction was not against Zama, or against privacy. It was a classic restraining order as we see often in DeFi, and we should have been notified so we could have taken the appropriate actions on our side.
I want to be very clear about something: our posture has always been compliant confidentiality, and we will not tolerate any illicit behavior in our protocol. It's also really useless for hackers to try to use Zama to hide their trail as we are precisely not a mixer and we do not obfuscate the sender and recipient, only balances and amounts. Eg you can see the hacker's cUSDC transactions here: https://t.co/yFtdaz5ytU
We are in touch with the various people involved to resolve the situation asap. In the meantime, we will pause the cUSDC, cUSDT and cWETH contracts until we have finished our investigation, identified all addresses linked to this case and taken appropriate action.
I will share a more detailed post-mortem and how we plan to deal with such requests in the future.
"We've accelerated narratives enough. Let's accelerate the cypherpunk privacy reality."
Vitalik framed it. Wrote yesterday about where this actually lands - privacy is becoming default, and most people are watching the wrong layer.
Wallet layer with Kohaku, compute layer elsewhere. When the wallet layer goes default, the compute layer is the next pressure point. Where does it land?