# Grant Application - Constant-Time Hardening and Explicit Timing Semantics for Zcash Rust Cryptography **URL:** \ **Category:** Community Grants\ **Created:** [July 2, 2026, 7:32pm UTC](https://forum.zcashcommunity.com/t/grant-application-constant-time-hardening-and-explicit-timing-semantics-for-zcash-rust-cryptography/56503 "2026-07-02T19:32:32Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![fdecroix](https://avatars.discourse-cdn.com/v4/letter/f/90db22/32.png) [@fdecroix](https://forum.zcashcommunity.com/u/fdecroix)\ **Post date:** [August 24, 2026, 8:59pm UTC](https://forum.zcashcommunity.com/t/grant-application-constant-time-hardening-and-explicit-timing-semantics-for-zcash-rust-cryptography/56503/12 "2026-08-24T20:59:36Z")
Hi @zcg! Great news! We wanted to share where we’ve landed after the last round of feedback, and make sure we’re aligned on next steps before moving forward. As I said in my last message, during the arborist call we were suggested to include extra repositories in our analysis. We spoke with Daira-Emma and confirmed that the new scope would include [6 new repositories](https://discord.com/channels/809218587167293450/876655911790321684/1540094364464971826) (zcash\_note\_encryption, sapling-crypto, orchard, zip32, pasta\_curves, and zcash\_spec). Such project’s scope extension requires a re-budgeting. By including analysis over all the requested repos, the new timeline would be 8-10 weeks of work (including reviewing time) and the updated total budget $25k. How should we channel this change in scope? We could always start working on the original approved scope and budget ( librustzcash only, 10k ) and tackle the extra requested repos on an independently submitted grant. We just want assurance we are all on the same page regarding scope & budget. Looking forward to your advice. Thanks! --- _[View the full topic](https://forum.zcashcommunity.com/t/grant-application-constant-time-hardening-and-explicit-timing-semantics-for-zcash-rust-cryptography/56503)._