Topic: [ANN][XCN] Cryptonite - NEW Thread | 1st mini-blockchain coin | Bounties! - page 218. (Read 215398 times)

please give me windows compile minerd if you have one .

your address start with = , sorry typo mistake

it should be -u address -p x

Stratum authentication failed

ahh, one more thing need to setup, what can be possible vardiff range for M7?

here my test pool . can anyone test it for me, please...

stratum+tcp://213.125.232.37:3334

-u=address  -p x

i am having all 480x AMD gpus, but problem is claymore not support latest gpus.
and i not have any nvidia gpus.

WARNING: AFTER CLEAN ALL DATA FILES (EXCEPT WALLET.DAT) AND USE BLOCKCHAIN SNAPSHOT ABOVE, MY WALLET HAS BROKEN

Tried to use -salvagewallet or even -upgradewallet not no luck.
I copied old wallet.dat to new data folder, and open the QT again, not loading normally but end up with empty wallet, no transactions, no receiving address. It create wallet.xxxxx.bak in the data folder.

I just downloaded that blockchain, allowed it to sync and made som test transactions to BTER. Everything worked smooth, so probably something just went wrong on your particular wallet.

WARNING: AFTER CLEAN ALL DATA FILES (EXCEPT WALLET.DAT) AND USE BLOCKCHAIN SNAPSHOT ABOVE, MY WALLET HAS BROKEN

Tried to use -salvagewallet or even -upgradewallet not no luck.
I copied old wallet.dat to new data folder, and open the QT again, not loading normally but end up with empty wallet, no transactions, no receiving address. It create wallet.xxxxx.bak in the data folder.

What happenning with my wallet, my coin>?

Here it is, new blockchain snapshot:

https://mega.nz/#!JBpXhZLA!CSAKL2oa-EFoQnaAsxIhVdo-ur9Dby4bb3gmYykJlq0

2017-03-13 03:48:02 Cryptonite version v0.1.1.0-g3fb0591-beta (Sun, 26 Oct 2014 23:10:32 +1100)
2017-03-13 03:48:02 Using OpenSSL version OpenSSL 1.0.1l 15 Jan 2015
2017-03-13 03:48:02 Default data directory C:\Users\XXX\AppData\Roaming\Cryptonite
2017-03-13 03:48:02 Using data directory F:\XXX\XCN\data
2017-03-13 03:48:02 Using at most 125 connections (2048 file descriptors available)
2017-03-13 03:48:02 Using 8 threads for script verification
2017-03-13 03:48:02 Using wallet wallet-original.dat
2017-03-13 03:48:02 init message: Verifying wallet...
2017-03-13 03:48:02 CDBEnv::Open : LogDir=F:\XXX\XCN\data\database ErrorFile=F:\PTS-RDP\XCN\data\db.log
2017-03-13 03:48:02 Renamed wallet-original.dat to wallet.1489376882.bak
2017-03-13 03:48:02 CDBEnv::Salvage : Database salvage found errors, all data may not be recoverable.
2017-03-13 03:48:02 Salvage(aggressive) found no records in wallet.1489376882.bak.
2017-03-13 03:48:02 Initialization result: 0
2017-03-13 03:48:02 Requesting shutdown
2017-03-13 03:48:02 Running Shutdown in thread
2017-03-13 03:48:02 Shutdown : In progress...
2017-03-13 03:48:02 StopNode()
2017-03-13 03:48:02 Shutdown : done
2017-03-13 03:48:02 Shutdown finished
2017-03-13 03:48:02 Shutdown result: 1
2017-03-13 03:48:02 Stopping thread
2017-03-13 03:48:02 Stopped thread

file wallet.dat has LSN 1/2295, past end of log at 1/476
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 1/2295, past end of log at 1/476
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 1/2295, past end of log at 1/476
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/2295 past current end-of-log of 1/476
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 10
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
file unknown has LSN 1/15617, past end of log at 1/28
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
Page 0: metadata page corrupted
Page 0: could not check metadata page
wallet.dat: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 1/15617, past end of log at 1/1073
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
wallet.1489369816.bak: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 1/15617, past end of log at 1/1257
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
__db_meta_setup: F:\PTS-RDP\XCN\data\wallet.dat: unexpected file type or format
file unknown has LSN 1/15617, past end of log at 1/2397
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
wallet.1489370397.bak: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 1/15617, past end of log at 1/1103
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
wallet.1489376882.bak: DB_VERIFY_BAD: Database verification failed

pallas , can i have blockchain snapshot of this moment to quick test my pool. sync take longer though i have last snapshot you uploaded.