Any news, when optiminer.pl pool we be live again?
I did not find an other pool.

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.

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

Great news!!!

NEW ccminer by djm34 with M7 support (windows binaries and sources):
CCminer for nvidia by Djm34

I pushed the source to github: https://github.com/Optiminer/hodlminer-wolf
It contains SHA512 for both AVX and AVX2 but chooses one or the other at compile time. Ideally, it would detect at runtime which is supported and use the corresponding one.

I get about 370 hash/s on my core i7-4770S.

@truckythin
with 9000hps you need days for a block of one steem power.... balance can be seen in steem page or with list_my_accounts if you imported you key

It'll say "Proof of work found" or something very much like that, then about 2 hours later when you reach the front of the queue it will say "Generated block" and you will get your reward.

application.cpp:439          hash rate: 9426 hps  target: 31 queue: 110 estimated time to produce: 39....
application.cpp:439           handle_block         ] Got 2 transactions from network on block 3645...
witness.cpp:426               on_applied_block     ] hash rate: 9837 hps  target: 31 queue: 110 estimated time to produce: 39...
application.cpp:439           handle_block         ] Got 3 transactions from network on block 36459....

In a sense it is. Steem power is mineable with a cpu, but not Steem tokens. Steem power can be converted into the currency though over 2 years of weekly payments.

getblocktemplate

CreateNewBlock(): TestBlockValidity failed (code -1)

sure there is, the wallet itself has a built in miner. GUI wallet even has menu items for turning it on/off