Fórum Zcash Community Forum

HI. need help. I have ledger nano s with zec. Zec T1. I cant to move it. And i lost my 24 world. do you now how i can move it?

In short: four claims in the 7 September update did not hold as written. Two were fixed the same day it went up, one is closed since, and one is still open and says why. Since then the larger change is that a device now checks the payment is the one the quorum approved, not just that it signs what it recomputed, which is proven on mainnet with change. Nineteen verifiable mainnet transactions, up from sixteen. Everything below is the detail behind those sentences, including what is merged and not yet deployed, and what is still not claimed. Corrections to the 7 September update, and what has landed since Four claims in that post did not hold as written. All four are addressed below with their current status, and then what came after. “Both the helper and the relay now run a worker pool with a bounded body read.” True of the relay only. The helper read request bodies with no ceiling at all, so one POST could make it buffer without limit, on the service every vault’s balance, proposal and send goes through. The asymmetry had been filed on 23 August, in an issue whose own body reads “the relay and bridge already cap at 2 MiB; the helper does not” , and it was open while the release notes said otherwise. Fixed in v0.4.0. The ceiling lives in one crate both servers read, and a test refuses a body read that has none. A unit test could not have caught it: the cap worked and its tests passed the whole time. The rule was never “does it work”, it was “does every server call it”. “The ex

This is wrong “It is equivalent to a “coinbase coin” (a freshly mined coin)—a pristine asset.”, on each pool you can see the funds going in and funds going out, similar to tornadocash it is all on chain data and timing and amounts can with statistics find a high probability where funds are based on a lot of things also including metadata such as transactions broadcasted with certain ip address, so it’s not the same as a freshly mined coin, in fact it’s closer to a mixing service like tornado cash, the only difference is, is that you can transfer in between the pool which you cannot with tornado cash. But funds from shielded pool treated as high risk and many exchanges will block it and ask for source of funds.

Wholly cow $1380 am I dreaming

I’m excited about this event but sad that I am going to miss it by a day. With Zcon the week before I’m flying from Cancun Oct 31st to India, but I land the night of November 1st.

For anyone in this boat, I was able to recover via Zkool + Ledger. Happy to help anyone through it.

Any chance you need any help with a launch? More than happy to contribute with dev resources and network. I truly believe it’s a great idea

Paradigm advocating for the DevFund wasn’t in the cards… but here we are. The DevFund, with all the aspects that need improvement or adaptation, is one of Zcash’s strengths. We need this strength to ensure Zcash reaches every corner of the world. x.com Matt Huang @matthuang A few thoughts on ZCash (disclosure: Paradigm is an investor in ZEC and ZODL): - All blockchain ecosystems struggle with long-term funding, especially of public goods, and an inflation-funded developer fund is an elegant mechanism to do so. How this fund is allocated is a fair 5:30 PM - 16 Sep 2026 510 59

Had a really good call with the ZecHub team today about Gleyo. We talked about where Gleyo is today, what we’re building toward, and how it could support different Zcash communities. One thing I really appreciated was how much feedback they gave us. We discussed things like making Gleyo’s roadmap more public, where we see the platform going over the next few years, and how Gleyo can become more than just a quest platform. They also shared some of their experience from using Crew3/Zealy in the early days, which was particularly interesting for us. The conversation wasn’t just me talking either. The Gleyo core team was there, and we all had the opportunity to answer questions and share our thoughts. I really enjoyed that part of the conversation. There’s also a possibility of ZecHub running a campaign on Gleyo, so I’m looking forward to seeing where that goes. Big thanks to the ZecHub team for taking the time to speak with us and for the honest feedback. One step at a time. Build → learn → adapt → repeat. And honestly, after conversations like this, I can’t help but feel like Zcash is going to become much bigger soon. There’s just a feeling that more things are starting to connect. Communities are experimenting with new ways to grow, projects are building, developers are working on integrations, and more people are starting to pay attention. I don’t know exactly what the next few years will look like, but I’m excited to be building in the ecosystem and seeing where it goes. One

Really enjoyed reading this update a lot is happening and it’s great seeing everyone continuing to build. That 4.0 while doing all this too Keep pushing, one step at a time

@Lowo88 Thank you for taking those 3 modules at the maiden Zcash Privacy Developers Residency , and we hope to have you again in the future.

wbfun: I want to host my own node and use zcash-cli to manage my wallets 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: 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. 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. 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