### Terms and Conditions
- [x] I agree to the [Grant Agreement](https://9ba4718…c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471_6ff6db4095fd4c4ba21babec361e927e.pdf) terms if funded
- [x] I agree to provide KYC information if funded above $50,000 USD
- [x] I agree to disclose conflicts of interest
- [x] I understand this program funds completed work only, and that the work must be verified and accepted by its intended users or their representatives before a Coinholder vote
- [x] I accept the applicable open-source contribution requirements
- [x] I understand grants are valued in USD but paid in Shielded ZEC
### Application Owners (@octocat, @octocat1)
@Zk-nd3r
### Organization or Individual Name
Frontier Compute LLC
### Additional Team Members
```team-members.yaml
None. I am submitting this through Frontier Compute LLC.
```
### How did you learn about the Lockbox: Coinholder Retroactive Grants Program?
Zcash Community Forum and Frontier Compute's existing participation in the Coinholder Retroactive Grants process.
### Requested Grant Amount (USD)
$123,750
### Category
Research & Development
### Project Summary
I found concrete security failures in Zcash infrastructure and wallet code, disclosed them responsibly, stayed with the work through remediation, and verified what merged and shipped. This application claims only accepted, public, merged or released outcomes. Private, open, rejected, disputed, and partially unresolved work is excluded.
### Project Description
I am Skander, founder of Frontier Compute. This was not a drive-by bug report. The operating loop was: define the security property, find and validate the failure path, report it privately, help make the required control precise, track remediation through review and merge, verify release ancestry, and re-read the fixed code for residual risk.
I am applying for one completed security-remediation pack because the work was run as one operation across infrastructure and wallet surfaces.
#### 1. Accepted and shipped lightwalletd work - $43,750
- [GHSA-9p9r-mggr-8q9g](https://github.com/zcash/lightwalletd/security/advisories/GHSA-9p9r-mggr-8q9g): a slow or non-reading `GetMempoolTx` client could hold the shared mempool mutex across streaming sends and block concurrent calls. I am the sole accepted reporter. The advisory is public and the fix shipped in lightwalletd 0.5.2. Valuation: $18,750.
- [GHSA-x4m7-3gpp-xc36](https://github.com/zcash/lightwalletd/security/advisories/GHSA-x4m7-3gpp-xc36): unauthenticated transparent-address RPC paths could force resource exhaustion. I authored and maintained the Frontier Compute report and preserve every additional public credit. This application claims only the two accepted paths fixed and released in lightwalletd 0.5.0. The remaining materialize-before-filter residual is expressly excluded. Valuation: $25,000, two-thirds of the former $37,500 Supporting Infrastructure High reference band.
These former ZCG bands are valuation benchmarks only, following the transparent benchmark approach used by other Q3 security applications. They are not evidence of an existing award.
#### 2. Accepted and merged ZODL mobile-wallet remediation - $80,000
I delivered coordinated security reports covering transaction-review integrity, account and session binding, secret-export surfaces, and swap validation. ZODL maintainers independently implemented and reviewed the fixes. I am claiming my research, responsible disclosure, control specification, adversarial verification, and fix-to-release tracking-not authorship of their patches.
This application relies only on the following public, approved, merged work and public release evidence:
- [zodl-android #2299 - Swap Security Hardening](https://github.com/zodl-inc/zodl-android/pull/2299), approved and merged 9 June 2026.
- [zodl-android #2317 - Security hardening](https://github.com/zodl-inc/zodl-android/pull/2317), approved and merged 12 June 2026.
- [zodl-ios #1825 - remove hidden debug seed export without authentication](https://github.com/zodl-inc/zodl-ios/pull/1825), approved and merged 16 June 2026.
- [zodl-ios #1849 - fail closed on multi-recipient ZIP-321 payment requests](https://github.com/zodl-inc/zodl-ios/pull/1849), approved and merged 26 June 2026.
- [zodl-ios #1851 - enforce account/signing boundaries and end stale Flexa sessions](https://github.com/zodl-inc/zodl-ios/pull/1851), approved and merged 26 June 2026.
- [zodl-android 3.8.1-2027](https://github.com/zodl-inc/zodl-android/releases/tag/3.8.1-2027), public release evidence for the relevant Android merge ancestry.
I ask ZODL, as the intended user and remediation owner, to confirm the report-to-fix linkage during review. Any item ZODL does not confirm must be removed from the funded scope rather than inferred in my favour.
#### Explicit exclusions
- No private advisory identifier, exploit detail, unreleased report, or confidential inventory is included.
- No open, draft, rejected, disputed, or unmerged work is valued.
- The unfixed `x4m7` residual is excluded.
- I do not claim maintainer-authored patches as my code.
- I do not claim an award, receivable, or payment that does not exist.
### Technical Approach (how you did it)
1. Define the property that must not fail: fund safety, review-to-signing equivalence, account binding, secret handling, availability, or bounded resource use.
2. Trace attacker-controlled inputs through validation, proposal, signing, streaming, and backend-RPC paths.
3. Reproduce locally or create regression-shaped evidence without stressing public services.
4. Disclose through controlled maintainer channels.
5. Map accepted work to exact public pull requests, review state, merge state, tests, and release ancestry.
6. Re-read the post-fix code and exclude every unresolved residual from the completed claim.
AI-assisted source analysis was part of the workflow. Human judgment controlled target selection, validation, severity restraint, disclosure, evidence admission, and remediation verification. Model output was never treated as proof by itself.
### Time Period of Work Completion
April 2026 through July 2026.
### Total Budget (USD)
$123,750
### Budget Breakdown
- Compensation: $123,750 - retroactive, outcome-based valuation of completed security research, responsible disclosure, control specification, regression evidence, and release verification.
- Technology/Software: $0 separately claimed.
- Infrastructure/Hosting: $0 separately claimed.
- Services/Contractors: $0 separately claimed.
- Other: $0.
- Total: $123,750.
### Previous Funding
No
### Previous Funding Details
Frontier Compute has not received Coinholder Retroactive Grants funding for this work. The separate ZAP1 application concerns unrelated attestation protocol and verification tooling.
### Other Funding Sources
Yes
### Other Funding Sources Details
Some public lightwalletd findings entered the former ZCG vulnerability process and may still be reviewed there. As of submission, I have no primary evidence of an award, receivable, or payment for any work claimed here.
I will not double collect. Any later ZCG bounty or other payment attributable to the same finding will be disclosed and deducted dollar-for-dollar before disbursement. If another route fully compensates an item, I will withdraw that item. This filing does not waive existing bounty eligibility.
### Success Metrics
- Two public lightwalletd advisories with accepted Frontier Compute reporter credit.
- Sole accepted reporter credit and a released 0.5.2 fix for GHSA-9p9r-mggr-8q9g.
- Only the two released `x4m7` paths claimed; the live residual excluded.
- Five approved and merged public ZODL security-hardening pull requests.
- Public Android release evidence.
- Zero private finding identifiers or unpublished exploit details disclosed.
- Dollar-for-dollar deduction or withdrawal prevents double recovery.
### Proof of completion
- [GHSA-9p9r-mggr-8q9g](https://github.com/zcash/lightwalletd/security/advisories/GHSA-9p9r-mggr-8q9g)
- [GHSA-x4m7-3gpp-xc36](https://github.com/zcash/lightwalletd/security/advisories/GHSA-x4m7-3gpp-xc36)
- [zodl-android #2299](https://github.com/zodl-inc/zodl-android/pull/2299)
- [zodl-android #2317](https://github.com/zodl-inc/zodl-android/pull/2317)
- [zodl-ios #1825](https://github.com/zodl-inc/zodl-ios/pull/1825)
- [zodl-ios #1849](https://github.com/zodl-inc/zodl-ios/pull/1849)
- [zodl-ios #1851](https://github.com/zodl-inc/zodl-ios/pull/1851)
- [lightwalletd 0.5.0](https://github.com/zcash/lightwalletd/releases/tag/0.5.0)
- [lightwalletd 0.5.2](https://github.com/zcash/lightwalletd/releases/tag/0.5.2)
- [zodl-android 3.8.1-2027](https://github.com/zodl-inc/zodl-android/releases/tag/3.8.1-2027)
### Conflict of Interest Disclosure
Frontier Compute LLC and I would receive this grant. I am the reporter and applicant, not the author of maintainer-written patches. The unrelated ZAP1 application is separate. Potential ZCG overlap is disclosed and fenced through dollar-for-dollar deduction or withdrawal.
### Community Forum Posting
- [x] I understand this application must be mirrored on the Zcash Community Forum for review and voting.