
CS @LehighU Engineering @TachyonZcash @penumbrazone
Joined November 2021
- Tweets879
- Following1.4K
- Followers912
- Likes5.7K
Time to vote! @zooko and I offer a compromise proposal (the "Future Dev and Legal Defense Fund") that I strongly encourage both ZCAP and Coinholders to support in this vote.
I am very concerned about the status quo. The bare minimum that ZEC holders should expect is that when ZCG is massively overfunded, we can at least pause sending it more money while the community has time to discuss its funding. They already have enough to fulfill their obligations for many years! This would be the prudent, fair, responsible, rational action for our community to take at the very least; especially since it does nothing to harm ZCG in the short term.
Even if you don't care much about this issue, my main concern is: should ZCAP vote to preserve the status quo despite a very reasonable compromise being on the table... it would raise serious questions about the fitness of ZCAP. We have much more important things to build and ship in the next years, which is precisely why I think our compromise is the best option for Zcash.
Zakura is dominating. There isn't a single level of the Zcash stack where it's not currently the leader in progress. Cryptography, security, performance, everything.
Enjoy the monthly recap:
NEW EPISODE - The Complete Zcash Roadmap
@Zcash co-founder @ebfull and Zcash protocol contributor @zkDragon break down what's next for $ZEC: scaling with Tachyon, preparing for quantum threats, and the future of private money.
The complete Zcash deep dive for everyone curious about where the project is headed.
CHAPTERS
---
0:00 Why Zcash Matters Now
07:53 AI Makes Privacy Urgent
11:20 The Zcash Development Roadmap
17:33 Privacy Without Compromises
25:26 Scaling Zcash With Tachyon
39:42 Private Wallets and Proof of Work
41:06 Zcash's Quantum Defense Roadmap
1:00:53 AI Threats and Formal Verification
1:12:53 Security Through Multiple Assumptions
1:19:37 Why Payments Come First
1:25:54 Funding Proof-of-Work Security
1:29:34 Governance and Coinholder Voting
1:34:53 ZEC Price and Protocol Threats
This month was security szn, especially prescient with the wave of attacks!
- protecting against the biggest wallet privacy leaks
- protecting the software supply chain
- cutting unneeded dependencies and surface area
- live mainnet nodes across compilers and architectures
- first of its kind p2p fuzzing and property testing
Margulus retweeted
Tachyon is fully supporting this proposal, authored by @ebfull and @zooko, regarding ZCG's funding stream and treasury. It asks ZCG to donate 50,000 ZEC to the NSM, and stop receiving funding, while leaving its program intact for many years.
teapawt.net/ebfull/status/21161881…
Margulus retweeted
Tachyon Group (led by Sean Bowe) and Shielded Labs just posted a proposal to end future funding of the Zcash Community Grants program and reduce its treasury. ⤵️
happy 10th birthday to zcash.
10 years of turning mathematical impossibilities into engineering realities.
against all odds, we’ve rekindled the fire that represents the very best of crypto.
joining one of the teams working to scale zcash has been one of the best decisions i’ve made. getting to work alongside brilliant cryptographers and engineers on problems that actually matter has reminded me why i fell in love with this industry in the first place.
not for the speculation, the noise, or the endless reinvention of finance, but for the possibility of building something fundamentally better for the world.
sovereign, encrypted, verifiable money at planetary scale.
10 years later, zcash is still chasing the original cypherpunk dream, onward anons!
Margulus retweeted
We're proud to announce the release of zkao version 3, the most powerful zkao update we've released so far. If you have a codebase that implements cryptography, now is the time to let zkao find bugs in it. Go to zkao.io to request access today.
Margulus retweeted
We condensed Tachyon’s design into a video that walks anyone familiar with Zcash’s protocol through each change.
Margulus retweeted
We’ve been sharing different parts of the Tachyon design for months.
Finally, we present to you a holistic deep dive!
- Birds-eye view of the “shielded core <> payment protocol” decoupling
- concrete design of evolving nullifiers, and new double-spending validation in consensus
- how syncing service obliviously sync non-membership of past nullifies without any privacy leakage (ie spend unlinkability)
Two subprotocols we explained in detail:
1. Quadratic-residue filters used to route/regroup pseudorandom values (tachygrams) into capped-sized buckets with distinct “QR profile” for cheap nonmembership test against a whole epoch without linear scan
2. a subsequence argument without using vector commitment: relax to a multiset argument about a set of indexed value, further relying on PCD to enforce contiguous indexes.
Benefit: no fixed range in advance, no RSA/Pairing for subvector proof, deadly simple IOP.
Margulus retweeted
Who verifies the formal verification?
Read about how we audited @TachyonZcash's Ironwood formalization and about common pitfalls for formal verification in general.
blog.zksecurity.xyz/posts/au…
Margulus retweeted
It is difficult to explain just how impressive this is. The Tachyon Project (@TachyonZcash) and @zksecurityXYZ have raised the bar for high-assurance software.
zakura.com/engineering/adver…
Zcash extends its lead in pursuing perfection using formal verification. In the future you won't audit code, you'll formally verify it and then audit the much smaller theorems.
(The future is now.)
We hired @zksecurityXYZ to audit Ironwood's formal verification. Rather than looking for security bugs, they tried to *add* bugs to see if the formal verification could catch them!
Here's our summary, along with the report:
zakura.com/engineering/adver…
Margulus retweeted
We had @zksecurityXYZ do mutation testing and fuzzing, except for our formal verification.
They tried to deliberately add counterfeiting bugs (using their massive corpus of ZK bugs) and watched as the formal proofs rejected them each time.
We hired @zksecurityXYZ to audit Ironwood's formal verification. Rather than looking for security bugs, they tried to *add* bugs to see if the formal verification could catch them!
Here's our summary, along with the report:
zakura.com/engineering/adver…
Margulus retweeted
We hired @zksecurityXYZ to audit Ironwood's formal verification. Rather than looking for security bugs, they tried to *add* bugs to see if the formal verification could catch them!
Here's our summary, along with the report:
zakura.com/engineering/adver…













