Post your technical support queries here

Sovright had a tool I think was intended specifically for zecwallet light recovery (?) so hopefully that works for you

A lot of the zecwallet light recovery functionality was in Ywallet, which will no longer transact, but it will work for account recovery to verify which seed is correct.https://ywallet.app/

Could also give Zingo PC another try. it was modeled a lot after zecwallet light and now supports multi-account, presumably under a single seed, also presumably in the same way that zecwallet light worked, though i’m not for sure.

1 Like

What’s the best course of action for me? I feel like i’m spinning my wheels here…

Are you confident that the transactions did not occur before that block height? Because if they did then they will not show up if you set that number as the starting height to begin the search.

I am confident. A friend introduced me to zcash May 2021. I even wrote the birthday down. I just went with a slightly earlier birthday to be safe.

Did Argos find your wallets?

Not yet. Argos says like 1 to 2 days for scan to complete.

Yeah. Argos uses the basic librustzcash sync engine instead of hyperdrive or vizor’s faster synch engine.

Please be patient and report back.

idk man. I get the dreaded feeling my zcash is gone…I hope not. I got layed off recently and could use the money in the wallet.

If the wallet started up but would not connect to a server, then you can select another in the settings. Here is a list of servers https://nodus.alexxiy.top/ , zecrocks being the main ones used.

1 Like

Zallet beta.3: recommended workflow for importing and recovering a legacy Sapling key?

I’m testing recovery of a legacy zcashd wallet in an isolated, read-only environment. The wallet contains one legacy Sapling extended spending key, and Zebra is fully synchronized.

With Zallet v0.1.0-beta.3:

  1. migrate-zcashd-wallet --no-scan stores the Sapling key as a standalone key.
  2. A historical scan reaches the chain tip, but no Sapling received notes become associated with the imported key/account.
  3. In a completely fresh Zallet database, z_importkey <key> no <2021-era birthday height> repeatedly closes the RPC connection (reported by the client as RemoteDisconnected) before any account/key row is committed.
  4. I reproduced this with both zallet-zebra and zallet-zaino. The service log repeatedly reports non-finalized state change stream ended unexpectedly while wallet initialization/synchronization is active.

What is the currently supported procedure for:

  • importing a legacy Sapling extended spending key;
  • rescanning from a known birthday height; and
  • verifying received notes, nullifiers, spends, and current balance?

Is this expected to require beta.4/current main, or is there a configuration or startup-order workaround that avoids this synchronization/RPC blocking behavior?

I also found Zallet issue #582, which suggests imported Sapling keys may not yet be connected to the spending path. After balance discovery, what is the recommended safe recovery path for funds controlled by such an imported key?

No transaction construction or broadcasting is being attempted; this is balance recovery and read-only verification only.

Zkool supports sapling key import. Easiest and fastest would be to export the key if you dont already have it and import it into the light wallet.
Latest zebra has functionality added to it so you can connect a light wallet directly to the full node (though I have not actually attempted this yet, its on the list!). Zkool already had an option in the settings to connect to a full node anyways (called ā€˜Light Node’ at the top of the page), so you could sync all of this locally sans lightwalletd if you wanted. (I know this question is specifically about zallet but zkool is the fastest and easiest way to recover a sapling account)

2 posts were merged into an existing topic: Zashi Is Becoming Zodl

I know I posted about this earlier but I would be grateful if an honest person could help me get into my wallet. They can take an appropriate fee for their time. Does anybody know how to get in touch with current team for zcash?

What wallet and version is it? And what seems to be preventing you from getting into it?

What happened with the Argos scan?

1 Like

how do I get in touch with zooko or those that work directly with the software?

That could be an issue, ZecWallet software has been obsolete since @adityapk00 stopped maintaining it around 2023.

1 Like

I don’t know where else to post, since I can’t create topics (most likely due to my account’s age), so I’ll reply here.

I want to get started with Zcash, however I’m not interested in most of the existing wallets. I want to host my own node and use zcash-cli to manage my wallets. I did get zcashd and zcash-cli working with each other, but I’m having a tough time understanding how Zebra fits into this. I tried running Zebra using the default zebrad.toml, which I generated with zebrad generate >> ~/.cache/zebra/zebrad.toml and then run zebra with zebrad -v -c zebrad.toml from the ~/.cache/zebra/ directory.

Zebra runs, but I can’t connect to it with zcash-cli. It just throws this error:

error: Could not locate RPC credentials. No authentication cookie could be found, and no rpcpassword is set in the configuration file.

I see the options for an rpcuser and rpcpassword in the zcashd config file, but I don’t see those options in Zebra with the zebrad.toml file only containing the option for cookies. In the latter instance, I also don’t know what file the cookie file is. Do I just create a file in ~/.cache/zebra called .cookie and generate a base64 cookie?

I’m stuck and completely confused as to what to do in order to get this working. I also don’t fully understand the relationship between Zebra and Zcashd. Is Zebra intended to be a full replacement of Zcashd? Does Zebra have any support for zcash-cli? Is zcash-cli fully deprecated just as Zcashd is? Do I need to install separate software for json-rpc?

If anyone has a getting started guide, it would be greatly appreciate, because I can’t find a single one online at all and AI hasn’t been particularly helpful.

You may be looking for Zallet, the Zcashd replacement: GitHub - zcash/zallet: An RPC wallet designed to replace the deprecated `zcashd` embedded wallet. Ā· GitHub

Since zcashd is depreciateed you have a few options:

  1. Zebra + Zallet (Official Command-Line / RPC Stack)

Node Validator: Zebra (zebrad), an independent Rust-based consensus full node maintained by the Zcash Foundation.

Wallet Layer: Zallet a Rust full-node RPC wallet developed by ECC as the official replacement for zcashd. It manages shielded and transparent keys, creates transactions, and interacts directly with a local Zebra node via JSON-RPC.

Best For: Server setups, automated workflows, power users, and developers requiring programmatic JSON-RPC wallet control.

  1. Local Zebra + lightwalletd + Graphical Wallet (Self-Sovereign Desktop Setup)

Architecture: Run zebrad as your local full node, paired with a locally hosted lightwalletd service.

Connected Wallet: Point a shielded desktop or mobile wallet (such as YWallet or Zashi) directly to your local endpoint (127.0.0.1:9067).

Best For: Users wanting a graphical UI (GUI) with complete self-sovereignty—validating all blocks locally without trusting external public lightwalletd servers.

  1. Z3 Infrastructure Stack (Zebra + Zaino + Zallet)

Overview: The unified ā€œZ3 stackā€ combines Zebra (node), Zaino (lightwalletd indexer replacement), and Zallet (wallet).

Key Feature: Native Tor integration out of the box for IP privacy during block synchronization and transaction broadcasting.

Best For: Privacy enthusiasts running dedicated node boxes or home servers requiring automated privacy guardrails.

(yes, this reply was partially AI assisted)