Grant amendment update
Greetings, fellow Zcashers!
As our project grew, we built infrastructure needed to operate ZcashMe and ZcashNames and released components that can be useful outside our own applications.
So we’re updating our retrospective grant to include work that fell outside the original submission and was not covered by our recent Zcash Community Grant (still uncollected).
We did not increase the requested amount.
Here are the additions:
-
We built seer-sync, a standalone Rust chain-sync engine for applications that need to observe Zcash activity without implementing a wallet stack. crates.io: Rust Package Registry
Given a UIVK or UFVK, seer-sync streams compact blocks, trial-decrypts outputs, detects spends, recovers memos and outgoing notes, persists transaction state, tracks the chain tip, and recovers from reorgs. It supports Sapling, Orchard, and Ironwood and does not depend on zcash_client_backend or zcash_client_sqlite.
This means a wallet, payment processor, accounting system, explorer, or backend service can add Zcash chain synchronization without rebuilding that infrastructure from scratch or taking custody of spending keys.
-
We built a service that watches Zcash activity for multiple configured viewing keys and writes both mempool and confirmed transactions into Postgres automatically. GitHub - zcashme/zns-mempool · GitHub
A project can maintain a master table containing its viewing keys and destination tables. Zns-mempool routes transaction data into the corresponding tables as activity appears on the network. It does not require the project to operate its own lightwalletd.
-
We built zebra-indexer-proto, a Rust crate containing bindings for Zebra’s indexer gRPC interface. crates.io: Rust Package Registry
The crate vendors Zebra’s indexer protocol definitions and ships the generated Rust bindings directly, so developers can add Zebra indexer support with a normal Cargo dependency instead of copying protobuf files, maintaining generated code, installing protoc, or adding a protobuf generation pipeline to their own project.
Applications can now have an interface for building on Zebra’s indexer APIs while keeping their own build systems smaller. We actively maintain this
-
We built a “Sign in with Zcash” flow using OAuth2/OpenID Connect. GitHub - zcashme/zns-login: Zcash-based authentication: pay to log in · GitHub
Users can authenticate with a Zcash identity instead of relying on a conventional email-and-password account. Developers can integrate the same flow into web applications that already support OAuth!
We’re also integrating ZcashMe login with @paulbrigner’s PGPZ platform: Add ZcashMe membership verification by craftsoldier · Pull Request #72 · paulbrigner/pgpz-sites · GitHub
Together, this work reduces several barriers to building on Zcash. So thank you to everyone who supports ZcashMe and ZcashNames. It is an honor to contribute to the ecosystem.
By the way, did you know: since the original application, our waitlist crossed 9,000 names, and Barry Silbert and WallStreetBets both mentioned the project!
Barry Silbert:
WallStreetBets:
Special thanks to everyone who tests ZcashMe and ZcashNames, shares them, contributes code and gives us feedback along the way. We’re making privacy as normal as names.
ZM ZN,
Julian & Team