Skip to content

Conversation

@fluidvanadium
Copy link
Contributor

@fluidvanadium fluidvanadium commented Oct 9, 2025

Why:

The interface to zingolib is scattered over many modules. I wanted to re-imagine what the interface could look like.

What:

The sum of assumptions necessary to create a wallet with zingolib is contained in code here.
The only change made to the zingolib package so far is the correction of a chain_from_str function.

Tests:

So far, this creates a ZingoWallet.
And tests that it reports syncking a chain.
Notably, this test does not involve customized test behavior. It only uses the interface methods presented in zcash_wallet_interface.

Testnet Benchmarks are dependent on the network, so this leaves something to be desired for benchmarks.

TODO: nextest profile

@fluidvanadium fluidvanadium requested a review from dorianvp October 9, 2025 07:23
@fluidvanadium fluidvanadium changed the title Migrate test framework to zingo_wallet interface Migrate scenarios framework to zingo_wallet interface Oct 9, 2025
impl zcash_wallet_interface::Wallet for ZingoWallet {
fn user_agent_id() -> zcash_wallet_interface::UserAgentId {
const AGENT_NAME: &str = "zingo_wallet";
const VERSION: &str = "0.0.1";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I advocated the removal of the foo.0 accessor.

@fluidvanadium fluidvanadium marked this pull request as draft January 8, 2026 01:59
@fluidvanadium fluidvanadium marked this pull request as ready for review January 16, 2026 06:42
@fluidvanadium fluidvanadium changed the title WALLET_INTERFACE: live testnet syncs zwi syncs, benchmarks Jan 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants