GitHub - hhanh00/zwallet: Zcash and Ycash light shielded wallet it is showing zwallet, not “Ywallet”. Is this the correct one? @hanh
1 Like
I had “ Sweep” the amount to the new wallet of the other computer with version 1.14.0. I tried to transfer to Transparent wallet and same error occurred. Where is the problem? Can I used the seed phrase of ywallet to Swep the funds to other one , which is working or change the server somehow like you said to complete this transfer? @hanh @Shawn
That is correct, it was a naming issue. You can also try Zkool which is the successor to Ywallet.
Is the fix live on PlayStore now?
Hi all,
I’m running into an issue while trying to rerun one of my demos, and it appears to be related to the NU6.1 upgrade.
When I attempt to broadcast a transaction in YWallet (desktop, Linux), I get a consensus-branch-ID mismatch error. I encountered something similar previously when moving from NU5 → NU6 in my own code. Updating my code to dynamically fetch the branch ID resolved it at the time.
Now NU6.1 is active, and I suspect that my desktop YWallet is still using the older branch ID.
I tried installing YWallet 1.14.0 using the Flatpak instructions from:
-
YWallet installation page
-
Zwallet github release page
However:
After installing 1.14.0 (Flatpak), the app does not launch at all. I had to reinstall my older 1.8.1+556 Flatpak, which still runs but of course it doesn’t support NU6.1, so broadcasting fails.
Is the 1.14.0 Flatpak build expected to work on Linux yet, or is it currently mobile-only?
Has anyone been able to launch the Flatpak or AppImage version on desktop after the NU6.1 update?
Environment
OS: Linux (Flatpak)
Working version: 1.8.1+556
Broken version: 1.14.0 Flatpak (fails to start)
Just confirmation on whether the 1.14.0 desktop build is fully released and functional.
Happy to provide logs or run any commands if it helps.
Thanks!
There was an issues with during the Ubuntu 24 upgrade and some people reported the same issue. You can try zkool as well
I am using Ubuntu 22. Does YWallet 1.14.0 not support Ubuntu 22?
It should work, but like I said, some people did experience issues with Linux. All of the other platforms should work as well. Internally, Zkool is the same as Ywallet and where developmental support will continue.
zkool is a complete rewrite of the wallet. None of the code is the same.
1 Like
Any ideas how to solve this problem for Ubuntu 22.04.5 LTS @hanh ?
The appimage should work fine.
1 Like
@hanh I tried running the Ywallet 1.14.0 AppImage on Ubuntu 22.04.5 LTS, and it fails to launch with this error:
/tmp/.mount_YwalleXXXXXX/ywallet: symbol lookup error:
/tmp/.mount_YwalleXXXXXX/ywallet: undefined symbol: g_once_init_enter_pointer
My GLib version is:
libglib2.0-0 2.72.4-0ubuntu2.6 (Ubuntu 22.04 default)
From what I found, the missing symbol g_once_init_enter_pointer only exists in GLib 2.80+, so the AppImage seems to be built against a newer GLib than what Ubuntu 22.04 ships.
Just sharing the output in case this helps diagnose the issue.
1 Like
it is for 24.04 lts
Hey team, I’m having issues with Ywallet. I keep having this error when sending funds. I guess these are the old funds from Coinbase mining
I tried to send to sapling and orchard wallet, both fails with the below error.
Interesting! This error would indicate that you are trying to spend coinbase outputs or mining rewards to a transparent address. Zip213 dictates (in some words) that the first tx made for all transparent mining rewards is to a shielded address and not another transparent address. If you first “shield” these funds, which means send them to your own shielded address, then they can be spent however you’d like. This has nothing to do with the wallet, it’s baked into the consensus rules and there is no getting around it. ZIP 213: Shielded Coinbase
1 Like
Thank you for the info! So instead of getting shielded address from other wallets, I should be sending to my own shielded address, right? It should work!
1 Like
Correct, that should fix your issue.
It doesn’t matter if the shielded address is yours or not (the protocol has no way of knowing that), but all the funds must be shielded. In your case, you probably have some transparent change.
2 Likes