Hey Guys, i sent some T-ZEC to my Zashi Wallet to shield them, but somehow i am always getting Error ZSAPP0001, Downloaded File with sapling spending parameters isn’t valid.
Is it possible to fix without erasing my Wallet start from Scratch?
I somehow don’t understand what the exact problem is in here, as this wallets has already received shielded funds before.
Thanks
cc @andrea
…
To all the scammers here on the forum, please save me and yourself some time and stop these low effort scams.
Thanks for the notification, banned both.
Most of the time I catch them before they get to level 1 and able to send DMs, but occasionally they slip through.
Hi @silentZcollector,
could you please tell us which platform (iOS/Android)? If iOS, I might have an idea how to delete just the param files and let Zashi to re-download it again.
Otherwise, on iOS only, it’s also possible to delete just Zashi from an iPhone, the secrets will stay in the keychain so re-install triggers rescan of the chain without any worry of loosing the access to the funds.
I wonder what might happen that the file is invalid though
This happens to me too. It is an Iphone 13 with latest ios version.
tried to reinstall the app getting the same error.
Sorry for the late reply.
I am on IOS. If anyone at ECC is interested in finding a solution for this bug, i am more than happy to help.
i just imported my seed from zashi into ywallet and now i am facing something even stranger.
the little shielded amount that was on this wallet is showing up, but the t-ZEC that i have sent from ledger to zashi is not showing up on ywallet? (i can see it on Zashi)
anyone an idea what happened there?
You can swipe or tap the QR in Ywallet to see balances held in the other addresses, or combined. Are the balances still incorrect?
There is also the possibility that zashi is using addresse that Ywallet does not derive.
yes, still not correct, all the t-ZEC is missing.
You should first verify that the transparent addresses are same. If not (which I suspect), you could attempt importing the seed into zecwallet-cli which sounds weird and you need Linux but they will derive the same Orchard and Transparent addresses.
ledger rotates t address. You cannot just import a seed because ywallet does not support multiple taddresses. You have to sweep the funds using the More/Sweep function.
i did not import the seed from ledger to ywallet, i imported the seed from Zashi. and as far as i know zashi does not support multiple t-addresses either, right?
zashi sometimes uses a non zero address index.
did not know that, i hope someone from ECC can help me find a solution.
Like I mentioned, you can try to recover with zecwallet light cli. It shares the same address derivation method as zashi and allows you to generate trivial numbers of addresses but idk if that would be required. If so, you could restore from seed and just a little time before b-day either with no-sync or stop and restart with no-sync (this would allow some grace time, if required).
Zashi implements the specified behavior of ZIP 316. It is YWallet that is not compliant here, in that it does not inspect the transparent receiver of the default Unified Address to find funds.
Zashi additionally performs Bitcoin-style transparent address discovery, looking for funds in the first 10 addresses generated via HD derivation and then progressively scanning more addresses (up to 10 potentially not-yet-used addresses) every time newly received outputs are discovered. This is to provide a better user experience when importing a seed phrase from a transparent-only wallet, and it’s recommended that all wallets in the ecosystem take this approach.
For YWallet, if you want to use it you’ll have to do as @hanh says and use the Sweep function.
Admittedly I never paid too much attention to this issue given that I have never been affected by it, but it seems enough people are that I’d like to understand if there’s a path forward that would solve this recurrent problem.
@hanh I am assuming you are not following ZIP 316 for a specific reason?
edit: ok I suppose this is the answer:
What do you think should be done here so users are spared those issues going forward?
Zashi also scans the zero-index address (and always has), so there’s no question of invalidation of funds.
It scans addresses at indices 0..n, where n is 10 + the index of the greatest index at which transparent funds have previously been received (this is the aforementioned compatibility with transparent-only wallets that used Bitcoin-style address rotation).
