How should Zcash transaction fees work with 100M users? ft. @zkDragon 0:00 - The problem with crypto transaction fees 1:14 - Dynamic fees based on network demand 3:00 - How private transaction fees could work 3:45 - Fees at 50,000 TPS 4:49 - Should miners receive transaction fees?

Even better for everyone’s block processing!!

New Zakura Release: 1.5.0 Miners benefit especially from this release: faster block commits, steadier mining templates, less work during template construction, and better handling of edge cases. Experimental P2Pv2 also gets reliability improvements. zakura.com/announcements/zak…

We now have a dashboard breaking down every live mainnet block's execution time. Block processing time will be eliminated in @ZakuraZcash

$1600 burrito

Next Zakura release mines even empty blocks 5x faster!

Presenting "thus spoke zakura" A batteries included dev environment for zcash developers! - gets you started with a zcash dev environment in seconds with a single click - in built wallet, block explorer and faucet for testing - cheat codes to mine & faucet and much more 👇

@zkdragon is a world-class once-in-a-generation engineer. Zcash wouldn't be the same without him. Zcash is winning.

This CLAUDE.md file has served me really well for ensuring large projects don't quickly turn into slop: gist.github.com/defuse/da01a…

There's an entire "waiting" screen in Zcash wallets that users don't need to see anymore because it's so fast now. Try it out today only in @vizorwallet!

Dev Ojha (@zkDragon) and I discuss the NU7 coin-holder vote (activating Nov 5). 0:00 - Record high vote 0:35 - NSM issuance smoothing 1:52 - NSM reissuance start date 2:47 - Sprout deprecation 4:34 - Faster block times 4:46 - NU7 scope and readiness 5:35 - How voting works

“It is meaningfully different to be a Zcash user today than literally six weeks ago.” Dev Ojha (@zkDragon) joins me to discuss Zcash’s security and UX improvements since Ironwood went live: - A quantum-recoverable, formally verified shielded pool - Proving optimizations - Onboarding links from @vizorwallet - Ledger integration for shielded ZEC

A cautionary tale about the future of Open Source Software in the age of AI. From Cathedral to Bazaar to Archipelago. - I recount Eric Raymond’s explanation of OSS inventive structure as a reputation game within a gift culture. - then explained how effortless agentic coding uproots many symbiotic dynamics among hackers and maintainers. - explained how the taboo of forking is violated and a speculative phenomenon of first-mover disadvantage. - conclude with a warning of the forkdom future that we might head towards, a land of splintered open gardens. (Better reading experience on desktop for Tufte-style sidenote) alexxiong.com/writings/archi…

NU7 is coming! All of the Zcash development orgs have come to unanimous agreement about the contents and timeline of our next network upgrade, following the sentiment collection results earlier this week. Activation approximately November 5. Learn more: forum.zcashcommunity.com/t/n…

If you're new to Zcash take a look at zecstats.com. It's my passion project and IMO one of the most complete and beautiful websites about any cryptocurrency.

9.5 years after Bitcoin, finally Zcash's turn to be 'leet 1 ZEC = USD$1337

Apple's new "Reference Image" design suggests something Apple won't say out loud: they don't actually trust the iPhone's Secure Enclave that much. They're probably right, and that has implications both for other proposals to stop deepfakes and for privacy-preserving identity, if it ever gets beyond stopping kids from looking at porn. Reference Image is a mode in the iPhone camera where Apple's servers sign a photo as genuine. The phone sends the raw data, signed by its trusted hardware, to Apple's Private Cloud Compute (PCC) servers, which process it, apply edits, and sign the result. It hides who took the photo, though Apple appears to keep identifying data so it can revoke photos from hacked phones. But why involve Apple's servers at all? It costs money and adds risk for Apple, like demands to deanonymize journalists, so they really have to get Private Compute Right. Maybe Apple couldn't get the image pipeline running inside the Secure Enclave. I doubt it. They could have, or could have with some work. But iPhones get jailbroken, and keys can be extracted from the Secure Enclave. If your threat model includes nation states making deepfakes, assume they'll do it. So I think Apple is using PCC as a trusted man-in-the-middle: it sees everything, so it can try to block exploited devices, and adapt as they see what attackers do. The other thing that relies on secure hardware is privacy-preserving credentials. Google's zk-id proposal uses hardware device binding to prevent credential sharing, and you might want to verify biometrics at enrollment too. But if we start using this for privacy-preserving KYC in banking and cryptocurrency, or for proof of personhood and deepfake prevention on social media, attackers will try to steal credentials or buy and borrow legit accounts. Device binding is meant to stop this. Apple's design suggests they think it can't.

waited almost 2 years for this you can now shield your ZEC via ledger encrypt your money, grow the anonymity set, and win

Shielded ZEC support for Ledger hardware wallets is now live on Vizor desktop and mobile.