Hi! I've been mining Leviarcoin for a few days before the hardfork and since the 0.1.3 and 0.1.4 updates, I simply cannot access my wallet.
I think I've literally tried everything, from re-installing the software (saved original files), isolating individual wallet, tx, save, reset, etc. files, but I get the same error: that my password is wrong despite it being correct. The original wallet cannot sync to the blockchain for some reason when loaded.
Could any of my files have been corrupted? Have a few thousand leviarcoins mined that I'd prefer not to lose forever...
Any help/advice would be appreciated.
Bests,
- Furni
Some additional things:
- I did attempt to transfer coins during the downtime resulting from the hardfork when things. Things were reverted back to 25000 from the old blockchain to the new blockchain. Could this be making my wallet data wrong/corrupt?
- Is there a way to check wallet balance (I understand XLC is privacy-driven) via the web/blockchain ie., bitcoin/ethereum?
- Additional info from daemon file:
"2018-Jan-11 10:42:42.268823 INFO [protocol] SYNCHRONIZATION started
2018-Jan-11 10:42:43.083995 WARNING [node_server] [81.170.236.241:18001 OUT] error during write: TcpConnection::write, WSAGetOverlappedResult failed, result=10054, An existing connection was forcibly closed by the remote host.
2018-Jan-11 10:42:43.083995 WARNING [node_server] [81.170.236.241:18001 OUT] Exception in connectionHandler: TcpConnection::read, WSAGetOverlappedResult failed, result=10054, An existing connection was forcibly closed by the remote host.
2018-Jan-11 10:42:55.517954 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:42:55.882164 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:42:56.265358 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:42:56.601272 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:42:56.930889 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:42:57.231470 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:43:21.590230 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:43:21.827471 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:43:22.053717 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:43:22.276033 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:43:22.504941 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:43:22.710446 INFO [protocol] [208.66.208.38:18001 OUT] Tx verification failed
2018-Jan-11 10:43:30.175498 INFO [protocol] [81.170.236.241:18001 OUT] Sync data returned unknown top block: 250002 -> 250063 [61 blocks (0 days) behind]
2018-Jan-11 10:43:30.175498 INFO [protocol] SYNCHRONIZATION started
2018-Jan-11 10:43:31.097993 WARNING [node_server] [81.170.236.241:18001 OUT] error during write: TcpConnection::write, WSAGetOverlappedResult failed, result=10054, An existing connection was forcibly closed by the remote host.
2018-Jan-11 10:43:31.097993 WARNING [node_server] [81.170.236.241:18001 OUT] Exception in connectionHandler: TcpConnection::read, WSAGetOverlappedResult failed, result=10054, An existing connection was forcibly closed by the remote host.
2018-Jan-11 10:43:43.023124 INFO [protocol] [109.124.249.199:18001 OUT] Sync data returned unknown top block: 250002 -> 250063 [61 blocks (0 days) behind]
2018-Jan-11 10:43:43.023124 INFO [protocol] SYNCHRONIZATION started
2018-Jan-11 10:43:52.106284 WARNING [Core] Failed to validate block 9809b64ffd04a68e51a30e2ed34bd5f964ff7bacf1561ee17b9203e56a7df227: Wrong block version
2018-Jan-11 10:43:58.336062 INFO [protocol] [89.36.214.54:18001 OUT] Tx verification failed
2018-Jan-11 10:43:58.536564 INFO [protocol] [89.36.214.54:18001 OUT] Tx verification failed
2018-Jan-11 10:44:09.822942 INFO [protocol] [109.124.249.199:18001 OUT] Sync data returned unknown top block: 250002 -> 250063 [61 blocks (0 days) behind]
2018-Jan-11 10:44:09.822942 INFO [protocol] SYNCHRONIZATION started"