# Zbeam: Verifiable Data Access and Server Routing for Zcash Wallets

**URL:** <https://forum.zcashcommunity.com/t/zbeam-verifiable-data-access-and-server-routing-for-zcash-wallets/58418>\
**Category:** Community Grants\
**Created:** [October 21, 2026, 4:28pm UTC](https://forum.zcashcommunity.com/t/zbeam-verifiable-data-access-and-server-routing-for-zcash-wallets/58418 "2026-10-21T16:28:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chigozzdev](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/chigozzdev/32/49586_2.png) [@chigozzdev](https://forum.zcashcommunity.com/u/chigozzdev)\
**Post date:** [October 21, 2026, 4:28pm UTC](https://forum.zcashcommunity.com/t/zbeam-verifiable-data-access-and-server-routing-for-zcash-wallets/58418/1 "2026-10-21T16:28:01Z")

</div>

Hi everyone, I’m Chigozie, an independent developer.

I’m working on a Zcash infrastructure project called **Zbeam** , and I’d appreciate feedback from wallet developers and infrastructure operators before finalizing the architecture and grant proposal.

The idea is to let wallets discover independently operated servers, verify the shielded scan data they receive, and switch providers when a server fails or returns invalid data. Wallets would continue scanning locally.

The planned approach is:

- **Chain verification:** use FlyClient to check chain work and history commitments. These checks are probabilistic, so the security parameters, bootstrap assumptions and network requirements would be explicit. Freshness would be checked separately.
- **Missing or altered data:** for supported transaction versions and shielded pools, check the returned transactions against counts committed in the chain. Verify transaction membership and reject duplicates. Reconstruct transaction identifiers from complete compact scan data and the additional hashes and fields supplied by the provider. Check ordering and full coverage of the requested range before updating wallet state.
- **Provider switching:** keep a verified checkpoint containing the block hash and corresponding wallet scan state. Resume from that checkpoint with another provider. If the chain has reorganized, reconcile the reorg before advancing wallet state.

I’ll document the proof format, starting-state checks and chain-acceptance assumptions as part of the architecture work and seek technical review. I’d particularly welcome criticism of the completeness checks.

I’d like to understand:

1. What problems do you currently encounter with server reliability, provider selection or verifying returned data?
2. Which parts of this are already handled well, and where are there gaps worth addressing?
3. What would Zbeam need to demonstrate before you would consider testing it?

@elviric @hanh, I’d appreciate your perspective from building Zucchini and Zkool. Would any part of this address a problem you currently face?

I’m also interested in hearing from anyone working on similar infrastructure, so I can understand where Zbeam could contribute.

GitHub: [https://github.com/chigozzdevv](https://github.com/chigozzdevv)
