Thanks again for the feedback. I’ll give that a go and see if I can get it to work. BTW, I’m going to post your windows port to another forum I use. Cheers.
thanks! the more exposure the better
Can this be used to mine to from flypool…?
No, if you turn on mining in the zcash.conf file it just solo mines…in a future release I’m possibly going to integrate 3rd party mining software, but this just has the default build-in zcash CPU miner
I mean can i use the address to send mining amounts to from flypool. Or will it overload like my nano s?
oh for that, yeah, it will be fine!
Thanks…still waiting to hear back from Ledger nano s about getting the private keys to try and install on zcash4win.
Later
Hi,
I want to export my private keys…I found the option to do that on my nano s. How would I import them to zcash4win? Any help is appreciated.
Try the “Wallet” menu in top left of the screen when Zcash4win running and there are various import/export options there.
Yeah, depending on how many keys the Nano S exported, its going to be import one private key or import private keys you’ll want to select
Tried running the wallet just now, but I keep getting the following error message (the numbers under “input string” change as the error periodically repeats itself):
Not really sure how to get the daemon running, or what I would need to do.
Awesome to see a windows wallet being worked on though!
It appears this problem goes away once the ZCash daemon has reached the current block height (61743 currently). You can run it without the GUI client from the command line using .\zcashd.exe -daemon=0 -showmetrics=1, for instance.
The problem is that the GUI wallet receives a number from zcash-cli but not with a dot decimal separator but a comma. It would help to diagnose the problem if you start the GUI wallet from a command prompt and attach the log after the issue occurs. What are the language/country/number format setting of your Windows system?
Please try to see if it will go away if you change the Windows decimal symbol to be a decimal dot:
Haven’t gotten any errors since I switched the decimal format, so that appears to have fixed the issue.
Alternatively, Veikkoeeva mentioned block height, and even though synchronization on my computer was at 2% when I last had the wallet open, it was at 49% when I re-opened it. Does that process keep running in the background, regardless of the wallet being open? (sorry if that’s a dumb question)
The zcashd.exe
process runs only when the GUI is running as well … under “normal” circumstances.
…in a future release I’m possibly going to integrate 3rd party mining software, but this just has the default build-in zcash CPU miner
That would be crazy - im searching for months for a solution solo mining with gpu directly on node.
Claymore and genoil connect to the node but cant get work.
Waiting for this update
Anyway thank you for your work @ Windows port - all runs fine.
Is there a way to bind zcash4win.exe to other ip than localhost ?
My zcash.conf:
addnode=mainnet.z.cash
rpcbind=192.168.1.117
rpcallowip=192.168.1.78
rpcallowip=192.168.1.117
rpcallowip=192.168.1.211
rpcallowip=127.0.0.1
rpcuser=xxx
rpcpassword=xxx
daemon=1
server=1
listen=1
gen=1
genproclimit=16
equihashsolver=tromp
best regards & Donation coming soon
Gary
Yes! From the zcash.conf example file, which I think has all the possible options in it:
# Bind to given address and always listen on it. Use [host]:port notation for IPv6
#bind=<addr>
Here’s a link to the whole thing on github:
https://raw.githubusercontent.com/zcash/zcash/da864da5ce9d7a1ee697769446133aa4ee35846e/contrib/debian/examples/zcash.conf
@vaklinov If this is a bug in zcash-cli or the RPC interface rather than the GUI wallet, can you open a ticket about it please? The RPC output should always be using “.” for decimals.
I suspect that this is a problem with zcash-cli returning comma as decimal separator, but without the log from the user this is not so clear. I will test later this week on Windows again myself - with changed locale settings. This happens on a Windows system with the build by @anon47418038 so it may be related to the C/C++ runtime library used… not necessarily a bug in zcash.
Yeah I haven’t messed about with the locale settings on one of my Windows systems yet to see if this is an issue with zcash-cli.exe or the Swing Wallet, but it is reproducible, as I’ve had at least 3 reports of this via various channels (forum, chat, email, etc).