My wish: I want to be able to import my really old wallet (my “dogfood” wallet from when I worked at ECC) into my phone so that I can spend the funds in there. I can probably get access to those funds on a PC using zcashd, but so far I’ve been procrastinating doing that, and no mobile wallet I’ve tried has worked; I’ve only ever gotten to like 2% syncing progress.
The spam attack is the reason syncing that wallet takes so long, but even assuming no more spam attacks happen and Zcash usage remains consistent, everyone else is eventually going to have this same problem importing their wallet. Imagine someone creates a new wallet today, uses it for 5 years, then they get a new phone and try to import their wallet into their new phone. They’re going to run into the same issue I’m having now.
Please keep the spirit of the thread on topic. The idea is to have actionable things that external or existing developers of the ecosystem could find as suitable projects or products.
I ran into a similar issue, I have a zcashd wallet I created around NU5 that I haven’t been able to access because every time I would start zcashd, it would trigger a full re-scan.
I decided to recover it in Zenith with the seed phrase and the exercise pointed out a number of places where the wallet scanning could be optimized, we’ll be releasing a new version with these optimizations once the changes are complete. We want to make sure people can use their wallets for years and recover them if needed.
I would like zcash to be a full-fledged bank. The ability to store coins and earn interest just by owning and holding them, like a savings account at a traditional bank.
more improvements to ZSA to enable the implementation of stablecoin (private stablecoin) in order to be the first private stablecoin. I believe that in the not too distant future there will be a demand for privacy, those who have real money would love to make anonymous transactions and with currency that does not have much volatility
I would like to see NFT with privacy, within the Zcash ecosystem. I’m totally unaware of the technical implementation of this, and I don’t know if it’s possible, but it would be great, as Zcash would not only attract privacy enthusiasts, but artists and content creators.
The combination of ZSAs and ZIP 231 memos will give several different options for implementing Zcash NFT capabilities, with options for both (limited, on-chain) private and (unlimited, off-chain) public NFT data.
Multiple desktop-compatible wallet to quickly sync + Multiple hardware wallet to securely store private key = never stuck in the wallet, always sync smoothly, securely self-custody
I still haven’t found in crypto a well crafted, easy to use and secure dead man’s switch to transmit your seed phrases to people of your chosing should something happen to you.
I have always wanted to see Least Authority’s Private Periodic Payment Protocol(P4) idea come to fruition in Zcash. Not sure if it’s still relevant/possible using this concept/their prior work or if there is a better way to get to the above described subscription UX. Either way I’m also on the same page about this being a banger feature.
I have a very small ask that would serve a lot of use cases but isn’t actually ZEC-specific at all: I want Zcash to have a wallet app that can categorize specific transactions in a GNUCash (Intuit QuickBooks/Microsoft Money) style income or expense double-booking accounting scheme.
Edge Wallet can do this (see Bitcoin Accounting Made Easy - Edge ) but Edge doesn’t support rotating addresses for Zcash wallets (i.e., it will not auto-rotate your Sapling or Orchard address after you use it to receive a payment). Zashi supports rotating addresses but its transaction metadata scheme is limited to only a free-form text field of limited length.
In my use case (see the workshops I am running for Zcash education initiatives reaching vulnerable populations, Supporting Financial Privacy Education for At-Risk Communities - #9 by fabacab ), one of the single most frequently asked questions I get is “how do I know which transaction is for what?” While having built-in “contact lists” to label addresses is useful for that side of the question, the other half, having a built-in way to categorize income and expenditures, is still largely missing from most cryptocurrency client applications, which creates far more friction for adoption than I believe most people are currently recognizing.
Hi @pacu, I’m asking you this question because you are the OP, but don’t feel like you are responsible for doing the work or anything… Is there a follow up to this list? I see a wide range of scope and complexity from items that are done already to massive undertakings. It would be great to know how the community can help moving forward.
Yes, I periodically update this site. ZecDev Community Billboard Then, when I meet a development team interested in getting into Zcash development, I point them to this wishlist board as inspiration material.
How could we make this even more approachable and actionable? I’d love to keep improving it
There could be a short use case scenario associated with each item. For example, what does the tab splitting feature mean? Is it for the payers or payees? Is it equally splitting? Is it in USD or ZEC? etc. That would help understanding the scope of the work.