As for now I am no longer able to synch SWEEP wallet on laptop (only desktop). There won't be much trade on zapple for the simple fact there isn't a functional wallet.
I mean, at least give us a faster beta wallet, give us some hope.
I mean, at least give us a faster beta wallet, give us some hope.
The wallet itself IS working, and working well ...
Your sync issue is NOT a wallet related issue. It is a network issue. So deciphering what it is that is causing this sync issue is what should be focused on, not so much that Zapple won't have trade for one reason or another.
Zapple wallet is synced and running fine. Citrine Wallet/Daemon is synced and running fine. My wallet is synced and running fine with more than 43 connections at any one time as can be seen below (with the balance removed) ...
Code:
{
"version" : "v1.3.0.0",
"protocolversion" : 80002,
"walletversion" : 60000,
"balance" : xxxxxxx,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 2309928,
"timeoffset" : -2298,
"moneysupply" : 763418270.99843526,
"connections" : 44,
"proxy" : "",
"ip" : "ew2m6nt6dkbz4oz2.onion",
"difficulty" : {
"proof-of-work" : 0.22012072,
"proof-of-stake" : 1.07780738
},
"testnet" : false,
"keypoololdest" : 1542105365,
"keypoolsize" : 101,
"paytxfee" : 0.00001000,
"mininput" : 0.00000000,
"errors" : ""
"version" : "v1.3.0.0",
"protocolversion" : 80002,
"walletversion" : 60000,
"balance" : xxxxxxx,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 2309928,
"timeoffset" : -2298,
"moneysupply" : 763418270.99843526,
"connections" : 44,
"proxy" : "",
"ip" : "ew2m6nt6dkbz4oz2.onion",
"difficulty" : {
"proof-of-work" : 0.22012072,
"proof-of-stake" : 1.07780738
},
"testnet" : false,
"keypoololdest" : 1542105365,
"keypoolsize" : 101,
"paytxfee" : 0.00001000,
"mininput" : 0.00000000,
"errors" : ""
So your assumption is not indicative of what is actually happening in the network, especially considering that my own desktop wallet has over 40 connections alone as of the time of writing this post, showing that there are quite a number of wallets open and staking readily. This can only mean there is an issue on your end, which we need to find and resolve. If you machine is Windows based, this could be a number of things, including FireWall, Malware and Virus Scanning interference, TOR port blocking, or a combination on any of those and others.
Check EVERYTHING on your system, router, proxy, etc. You find there is an issue somewhere there, as it is definitely not the network. We will remove TOR eventually as we believe this is the main cause of so much grief on a local level, especially when another app is using the TOR port, or TOR is blocked altogether.
Got all the nodes added to the SweepstakeCoin.conf file?
#crysx