really cool. tested it. recieve worked.
sending worked also, took quite some time to recieve on other end, but that might have been the blockchain itself.
calculating the transaction / sending step took super long - 45 seconds on macbook pro m1
dats much longer than on my phone, so maybe there is some optimization do be done?
on ywallet it takes a second or few max to calculate it.
another bug? clicking “view txid” goes to https://zecblockexplorer.com/ and that is a wrong link or doesnt open for me
Where is the state of the app stored? I wanted to change lightwalletd servers after started syncing and I think the only way is to start again, but I can’t find where things are stored. I deleted ~/.config/Zingo PC but it doesn’t seem to work
In zingo-mobile in settings (Advanced mode) you can change the server to a testnet one, and you can do the same in the first screen in the top right menu icon as well if you try to open another wallet…
and Thanks for the tip, we will consider to include more servers in the list.
I guess I should open a github issue or send a PR. The way to make Zingo-PC faster is to compile the Rust/node binding (neon) with --release flag. i.e.:
In package.json change from this:
That explains why syncing is taking too long, good find.
I also experienced something weird. I left it open and sync got stuckaround ~70% IIRC. I had to reboot my PC and then it started from 0 again? I did the same thing but then it seems to have resumed from where it was. (I realized this report really isn’t that helpful…)
This is weird because the wallet is stored locally at least every 30 seconds with the progression of the syncing. Do you remember the block or the batch numbers before & after…? and what means from 0 again?
Thanks for the feedback, my questions are only for understanding and maybe fixing the problem. You can reach me out with a DM if you want to.
Many thanks! That’s cool! I tested the installation on my systems and on the version of the macbook with Intel CPU, Zingo PC impossible to run. The wallet is launched on M1 without any trouble.
Thanks fort the thanks! … but I think you did more work on this than me! I didn’t contribute much (beyond my unflagging enthusiasm)… and a few early test runs.