Gabriel Eiger (OP)
Sr. Member
 Offline
Activity: 280
Merit: 250
Lead developer of Credits [CRE]
|
 |
April 10, 2015, 01:49:59 AM |
|
TORRENT WITH UP TO DATE BLOCKCHAIN DISTRIBUTED! There have been some serious problems with the initial synching of the blockchain for some. The problem with long initial sync times will be addressed soon in the coming releases of the client. To ease the transition period, an up to date working directory is distributed here to speed up installation and sync times. This should get sync times down to under half an hour once the torrent has been downloaded and unpacked. Torrent file with instructions can be found here: http://bitcredit-currency.org/viewtopic.php?f=18&t=517The torrent has been tested on two separate windows 64 bit stationary installations after uploading and downloading the torrent. !!!!NOTE!!! For some reason some files may come out as read only after extraction. To make sure that this does not cause problems, right click the Bitcredit working directory and select Properties. Deselect the Read only checkbox and click OK. Make sure that the update is applied recursively to the whole directory. !!!!NOTE!!! It is not recommended for use with any other operating system for the moment. If you have any questions, direct them here to get a quick reply. |
|
|
|
|
|
|
|
|
|
|
Once a transaction has 6 confirmations, it is extremely unlikely that an attacker without at least 50% of the network's computation power would be able to reverse it.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
Gabriel Eiger (OP)
Sr. Member
Offline
Activity: 280
Merit: 250
Lead developer of Credits [CRE]
|
|
April 10, 2015, 05:51:54 AM |
|
Any word on the working directory?
Everything should be in place now. See separate post. |
|
|
|
Gabriel Eiger (OP)
Sr. Member
Offline
Activity: 280
Merit: 250
Lead developer of Credits [CRE]
|
|
April 11, 2015, 01:52:49 PM |
|
Any word on the working directory?
Everything should be in place now. See separate post. Okay I got the torrent downloaded and synced up. Even found a couple blocks. I'm troubled by the 6400 blocks already mined when nobody was able to get the wallet working. Several users have been able to get the client started and have been mining from the beginning, for example MisO69, so block creation has been fairly quick from the start. It is at a slower pace now that the difficulty has adjusted accordingly. As is described in the post below, the distribution of coins is also S-shaped, meaning that the reward will be smaller in the beginning to reach a max in about two years. This is to give a fairer distribution by not giving early miners an unproportional amount of coins. I hope this lessens your concerns. http://bitcredit-currency.org/viewtopic.php?f=24&t=510 |
|
|
|
MRKLYE
Legendary
Offline
Activity: 1358
Merit: 1003
Designer - Developer
|
|
April 11, 2015, 03:05:28 PM |
|
Got it running!
|
|
|
|
MRKLYE
Legendary
Offline
Activity: 1358
Merit: 1003
Designer - Developer
|
|
April 11, 2015, 04:55:31 PM |
|
So, I've got the wallet synced fully now (from the torrent download) and have successfully mined my first block!
Very excited to see where this coin goes.
Gabriel has been very helpful in assisting me get the Bitcredit client going. A top notch coin developer!
|
|
|
|
MRKLYE
Legendary
Offline
Activity: 1358
Merit: 1003
Designer - Developer
|
|
April 11, 2015, 09:14:15 PM
Last edit: April 11, 2015, 10:41:17 PM by MRKLYE |
|
Having a bit of an error..
I restarted my client and tried to claim bitcoins for bitcredit..
Unfortunately the block that I found isn't appearing in my wallet now. :/
Did my 40 Bitcredit get wiped? :/
*edit: Seems I was mining on my own fork.. Wonderful.
*edit2: It appears that windows 8 is blocking my folders with the read only flag.. I can't seem to set it any other way.
|
|
|
|
shojayxt
Legendary
Offline
Activity: 896
Merit: 1001
|
|
April 11, 2015, 11:16:30 PM |
|
Having a bit of an error..
I restarted my client and tried to claim bitcoins for bitcredit..
Unfortunately the block that I found isn't appearing in my wallet now. :/
Did my 40 Bitcredit get wiped? :/
*edit: Seems I was mining on my own fork.. Wonderful.
*edit2: It appears that windows 8 is blocking my folders with the read only flag.. I can't seem to set it any other way.
Right click on the folder - Choose Properties - General - uncheck Read Only - click Apply Edit: It might say read only again after you do that but the permissions should be set correctly. I had the same issue. |
|
|
|
|
MRKLYE
Legendary
Offline
Activity: 1358
Merit: 1003
Designer - Developer
|
|
April 12, 2015, 03:09:43 AM |
|
Having a bit of trouble getting this baby fired back up. Log is as follows: 2015-04-12 03:05:14 Bitcoin version v0.9.1.4-gdaa6b7e-beta (Wed, 18 Mar 2015 12:28:57 +0100)
2015-04-12 03:05:14 Bitcredit version v0.9.1.4-gdaa6b7e-beta (Wed, 18 Mar 2015 12:28:57 +0100)
2015-04-12 03:05:14 Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
2015-04-12 03:05:14 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2015-04-12 03:05:14 Default data directory C:\Users\M R KLYE\AppData\Roaming\Bitcredit
2015-04-12 03:05:14 Using data directory C:\Users\M R KLYE\AppData\Roaming\Bitcredit
2015-04-12 03:05:14 Bitcoin using at most 125 connections
2015-04-12 03:05:14 Bitcredit using at most 125 connections
2015-04-12 03:05:14 Bitcoin using 4 threads for script verification
2015-04-12 03:05:14 Bitcredit using 4 threads for script verification
2015-04-12 03:05:14 Bitcoin: Using wallet bitcoin_wallet.dat
2015-04-12 03:05:14 init message: Bitcoin: Verifying wallet...
2015-04-12 03:05:14 CDBEnv::Open : LogDir=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_database ErrorFile=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_db.log
2015-04-12 03:05:14 Deposit: Using wallet deposit_wallet.dat
2015-04-12 03:05:14 init message: Deposit: Verifying wallet...
2015-04-12 03:05:14 CDBEnv::Open : LogDir=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\deposit_database ErrorFile=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\deposit_db.log
2015-04-12 03:05:14 Bitcredit: Using wallet bitcredit_wallet.dat
2015-04-12 03:05:14 init message: Bitcredit: Verifying wallet...
2015-04-12 03:05:14 CDBEnv::Open : LogDir=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_database ErrorFile=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_db.log
2015-04-12 03:05:14 Bound to [::]:8333
2015-04-12 03:05:14 Bound to 0.0.0.0:8333
2015-04-12 03:05:14 Bound to [::]:9333
2015-04-12 03:05:14 Bound to 0.0.0.0:9333
2015-04-12 03:05:14 init message: Bitcoin: Loading block index...
2015-04-12 03:05:14 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_blocks\index
2015-04-12 03:05:14 Opened LevelDB successfully
2015-04-12 03:05:14 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_chainstate
2015-04-12 03:05:18 Opened LevelDB successfully
2015-04-12 03:05:18 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_chainstatecla
2015-04-12 03:05:18 Opened LevelDB successfully
2015-04-12 03:05:22 Bitcoin: LoadBlockIndexDB(): last block file = 255
2015-04-12 03:05:22 Bitcoin: LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=23, size=7644917, heights=351700...351722, time=2015-04-11...2015-04-11)
2015-04-12 03:05:22 Bitcoin: Checking all blk files are present...
2015-04-12 03:05:23 Bitcoin: LoadBlockIndexDB(): transaction index disabled
2015-04-12 03:05:23 Bitcoin: LoadBlockIndexDB(): hashBestChain=0000000000000000135326495881aced3858dea042b0bf351fe29f1c03bd8a62 height=351722 date=2015-04-11 21:29:30 progress=0.999657
2015-04-12 03:05:23 init message: Bitcoin: Verifying blocks...
2015-04-12 03:05:23 Bitcoin: Verifying last 288 blocks at level 3
2015-04-12 03:06:36 Bitcoin: No coin database inconsistencies in last 209 blocks (155277 transactions)
2015-04-12 03:06:37 bitcoin block index 83461ms
2015-04-12 03:06:37 init message: Bitcredit: Loading block index...
2015-04-12 03:06:37 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_blocks\index
2015-04-12 03:06:37 Opened LevelDB successfully
2015-04-12 03:06:37 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_chainstate
2015-04-12 03:06:37 Opened LevelDB successfully
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): last block file = 0
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=6552, size=3753442, heights=0...6548, time=2015-03-06...2015-04-11)
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): transaction index disabled
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): hashBestChain=00000000983b1b95f3b177e948e48591c939c17e8764cb72008ee0cf21308a45 height=0 date=2015-03-06 18:04:48 progress=0.000000
2015-04-12 03:06:37 init message: Bitcredit: Verifying blocks...
2015-04-12 03:06:37 bitcredit block index 132ms
2015-04-12 03:06:37 init message: Loading bitcoin wallet...
2015-04-12 03:06:37 nFileVersion = 90100
2015-04-12 03:06:37 Keys: 101 plaintext, 0 encrypted, 101 w/ metadata, 101 total
2015-04-12 03:06:37 bitcoin wallet 156ms
2015-04-12 03:06:37 init message: Loading deposit wallet...
2015-04-12 03:06:37 nFileVersion = 90104
2015-04-12 03:06:37 Keys: 106 plaintext, 0 encrypted, 106 w/ metadata, 106 total
2015-04-12 03:06:38 deposit wallet 157ms
2015-04-12 03:06:38 init message: Loading bitcredit wallet...
2015-04-12 03:06:38 nFileVersion = 90104
2015-04-12 03:06:38 Keys: 125 plaintext, 0 encrypted, 125 w/ metadata, 125 total
2015-04-12 03:06:38 bitcredit wallet 166ms
2015-04-12 03:06:38 Wiping LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\.tmp\bitcoin_chainstatecla.tmp.1
2015-04-12 03:06:38 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\.tmp\bitcoin_chainstatecla.tmp.1
2015-04-12 03:06:38 Opened LevelDB successfully
2015-04-12 03:06:38 *** Error moving claim tip. Expected active bitcredit block: 0000000000000000000000000000000000000000000000000000000000000000, was: 00000000008e2ade84c6d9f695f1736c022645b3839e7906a572559d75a27c40
2015-04-12 03:06:45 *** ERROR: Bitcredit: ConnectBlock: Failed to move claim tip to 0000000000000000189a6d0d46b0364748c4c2249ba4a3cbb45db99abcbfd2a9
2015-04-12 03:06:45 ERROR: Bitcredit: ConnectTip() : ConnectBlock 000000005fc6f4b75a16b644bc1bd975ec71e7bdfab3144d84915d0efae490d2 failed
2015-04-12 03:06:45 Requesting shutdown
2015-04-12 03:06:45 Wiping LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\.tmp\bitcoin_chainstatecla.tmp.1
2015-04-12 03:06:45 init message: Loading bitcoin addresses...
2015-04-12 03:06:45 Loaded 13013 addresses from bitcoin_peers.dat 1430224109615ms
2015-04-12 03:06:45 init message: Loading bitcredit addresses...
2015-04-12 03:06:45 Loaded 86 addresses from bitcredit_peers.dat 1430224109568ms
2015-04-12 03:06:46 Running Shutdown in thread
2015-04-12 03:06:46 Initialization result: 0
2015-04-12 03:06:46 Shutdown : In progress...
2015-04-12 03:06:46 Stopping thread
2015-04-12 03:06:47 StopNode()
2015-04-12 03:06:54 Shutdown : done
2015-04-12 03:06:54 Shutdown finished
2015-04-12 03:06:54 Stopped thread What start up command do I use to fix this..? *edit: I used -reindex and it fired back up again.. and now to wait.. |
|
|
|
shojayxt
Legendary
Offline
Activity: 896
Merit: 1001
|
|
April 12, 2015, 03:43:58 AM |
|
Having a bit of trouble getting this baby fired back up. Log is as follows: 2015-04-12 03:05:14 Bitcoin version v0.9.1.4-gdaa6b7e-beta (Wed, 18 Mar 2015 12:28:57 +0100)
2015-04-12 03:05:14 Bitcredit version v0.9.1.4-gdaa6b7e-beta (Wed, 18 Mar 2015 12:28:57 +0100)
2015-04-12 03:05:14 Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
2015-04-12 03:05:14 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2015-04-12 03:05:14 Default data directory C:\Users\M R KLYE\AppData\Roaming\Bitcredit
2015-04-12 03:05:14 Using data directory C:\Users\M R KLYE\AppData\Roaming\Bitcredit
2015-04-12 03:05:14 Bitcoin using at most 125 connections
2015-04-12 03:05:14 Bitcredit using at most 125 connections
2015-04-12 03:05:14 Bitcoin using 4 threads for script verification
2015-04-12 03:05:14 Bitcredit using 4 threads for script verification
2015-04-12 03:05:14 Bitcoin: Using wallet bitcoin_wallet.dat
2015-04-12 03:05:14 init message: Bitcoin: Verifying wallet...
2015-04-12 03:05:14 CDBEnv::Open : LogDir=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_database ErrorFile=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_db.log
2015-04-12 03:05:14 Deposit: Using wallet deposit_wallet.dat
2015-04-12 03:05:14 init message: Deposit: Verifying wallet...
2015-04-12 03:05:14 CDBEnv::Open : LogDir=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\deposit_database ErrorFile=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\deposit_db.log
2015-04-12 03:05:14 Bitcredit: Using wallet bitcredit_wallet.dat
2015-04-12 03:05:14 init message: Bitcredit: Verifying wallet...
2015-04-12 03:05:14 CDBEnv::Open : LogDir=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_database ErrorFile=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_db.log
2015-04-12 03:05:14 Bound to [::]:8333
2015-04-12 03:05:14 Bound to 0.0.0.0:8333
2015-04-12 03:05:14 Bound to [::]:9333
2015-04-12 03:05:14 Bound to 0.0.0.0:9333
2015-04-12 03:05:14 init message: Bitcoin: Loading block index...
2015-04-12 03:05:14 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_blocks\index
2015-04-12 03:05:14 Opened LevelDB successfully
2015-04-12 03:05:14 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_chainstate
2015-04-12 03:05:18 Opened LevelDB successfully
2015-04-12 03:05:18 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_chainstatecla
2015-04-12 03:05:18 Opened LevelDB successfully
2015-04-12 03:05:22 Bitcoin: LoadBlockIndexDB(): last block file = 255
2015-04-12 03:05:22 Bitcoin: LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=23, size=7644917, heights=351700...351722, time=2015-04-11...2015-04-11)
2015-04-12 03:05:22 Bitcoin: Checking all blk files are present...
2015-04-12 03:05:23 Bitcoin: LoadBlockIndexDB(): transaction index disabled
2015-04-12 03:05:23 Bitcoin: LoadBlockIndexDB(): hashBestChain=0000000000000000135326495881aced3858dea042b0bf351fe29f1c03bd8a62 height=351722 date=2015-04-11 21:29:30 progress=0.999657
2015-04-12 03:05:23 init message: Bitcoin: Verifying blocks...
2015-04-12 03:05:23 Bitcoin: Verifying last 288 blocks at level 3
2015-04-12 03:06:36 Bitcoin: No coin database inconsistencies in last 209 blocks (155277 transactions)
2015-04-12 03:06:37 bitcoin block index 83461ms
2015-04-12 03:06:37 init message: Bitcredit: Loading block index...
2015-04-12 03:06:37 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_blocks\index
2015-04-12 03:06:37 Opened LevelDB successfully
2015-04-12 03:06:37 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_chainstate
2015-04-12 03:06:37 Opened LevelDB successfully
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): last block file = 0
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=6552, size=3753442, heights=0...6548, time=2015-03-06...2015-04-11)
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): transaction index disabled
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): hashBestChain=00000000983b1b95f3b177e948e48591c939c17e8764cb72008ee0cf21308a45 height=0 date=2015-03-06 18:04:48 progress=0.000000
2015-04-12 03:06:37 init message: Bitcredit: Verifying blocks...
2015-04-12 03:06:37 bitcredit block index 132ms
2015-04-12 03:06:37 init message: Loading bitcoin wallet...
2015-04-12 03:06:37 nFileVersion = 90100
2015-04-12 03:06:37 Keys: 101 plaintext, 0 encrypted, 101 w/ metadata, 101 total
2015-04-12 03:06:37 bitcoin wallet 156ms
2015-04-12 03:06:37 init message: Loading deposit wallet...
2015-04-12 03:06:37 nFileVersion = 90104
2015-04-12 03:06:37 Keys: 106 plaintext, 0 encrypted, 106 w/ metadata, 106 total
2015-04-12 03:06:38 deposit wallet 157ms
2015-04-12 03:06:38 init message: Loading bitcredit wallet...
2015-04-12 03:06:38 nFileVersion = 90104
2015-04-12 03:06:38 Keys: 125 plaintext, 0 encrypted, 125 w/ metadata, 125 total
2015-04-12 03:06:38 bitcredit wallet 166ms
2015-04-12 03:06:38 Wiping LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\.tmp\bitcoin_chainstatecla.tmp.1
2015-04-12 03:06:38 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\.tmp\bitcoin_chainstatecla.tmp.1
2015-04-12 03:06:38 Opened LevelDB successfully
2015-04-12 03:06:38 *** Error moving claim tip. Expected active bitcredit block: 0000000000000000000000000000000000000000000000000000000000000000, was: 00000000008e2ade84c6d9f695f1736c022645b3839e7906a572559d75a27c40
2015-04-12 03:06:45 *** ERROR: Bitcredit: ConnectBlock: Failed to move claim tip to 0000000000000000189a6d0d46b0364748c4c2249ba4a3cbb45db99abcbfd2a9
2015-04-12 03:06:45 ERROR: Bitcredit: ConnectTip() : ConnectBlock 000000005fc6f4b75a16b644bc1bd975ec71e7bdfab3144d84915d0efae490d2 failed
2015-04-12 03:06:45 Requesting shutdown
2015-04-12 03:06:45 Wiping LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\.tmp\bitcoin_chainstatecla.tmp.1
2015-04-12 03:06:45 init message: Loading bitcoin addresses...
2015-04-12 03:06:45 Loaded 13013 addresses from bitcoin_peers.dat 1430224109615ms
2015-04-12 03:06:45 init message: Loading bitcredit addresses...
2015-04-12 03:06:45 Loaded 86 addresses from bitcredit_peers.dat 1430224109568ms
2015-04-12 03:06:46 Running Shutdown in thread
2015-04-12 03:06:46 Initialization result: 0
2015-04-12 03:06:46 Shutdown : In progress...
2015-04-12 03:06:46 Stopping thread
2015-04-12 03:06:47 StopNode()
2015-04-12 03:06:54 Shutdown : done
2015-04-12 03:06:54 Shutdown finished
2015-04-12 03:06:54 Stopped thread What start up command do I use to fix this..? *edit: I used -reindex and it fired back up again.. and now to wait.. From: Quick initialisation from torrent file http://bitcredit-currency.org/viewtopic.php?f=18&t=517Start the Bitcredit-Qt client from the command line with the following command (assuming that you have already installed the executables in the directory shown): C:/bitcredit/Bitcredit-Qt.exe -checklevel=2 If you still have the torrent zip file it might be best to just start over from that after backing up your existing wallets until you get synced back up. That's just my suggestion. Make sure you go into the properties of the bitcredit directory and uncheck read only. Also the torrent file is two levels deep after unzipping so you need to make sure your getting to the bitcredit/bitcredit directory where the blockchain files are or else it will download everything. You can move it where it needs to go. |
|
|
|
|
MRKLYE
Legendary
Offline
Activity: 1358
Merit: 1003
Designer - Developer
|
|
April 12, 2015, 05:51:22 AM |
|
Trying to restart with -checklevel=2 now. Only 1 year 13 weeks left of re-indexing on the BTC blockchain.
Hopefully going to get the blockchains done downloading and synced tonight so I can have another whack at mining!
Will post back here when I get it going again. Strange that it wouldn't allow me to launch it without a reindex/checklevel.
I had to ctrl+alt+delete the Bitcredit client when I got to crazy with my CPU priority for mining.. I would be careful doing such again.
|
|
|
|
shojayxt
Legendary
Offline
Activity: 896
Merit: 1001
|
|
April 12, 2015, 06:22:00 AM |
|
Trying to restart with -checklevel=2 now. Only 1 year 13 weeks left of re-indexing on the BTC blockchain.
Hopefully going to get the blockchains done downloading and synced tonight so I can have another whack at mining!
Will post back here when I get it going again. Strange that it wouldn't allow me to launch it without a reindex/checklevel.
I had to ctrl+alt+delete the Bitcredit client when I got to crazy with my CPU priority for mining.. I would be careful doing such again.
Back up your wallet files before doing anything. I had that happen and I deleted everything in the bitcredit directory except the wallet files and copied the torrent files over to the bitcredit directory and started with Bitcredit-Qt.exe -checklevel=2. I found that once the blockchain data got funky it took longer than just starting with the torrent files Gabriel provided and using -checklevel=2. I don't know why some of us had problems and others didn't. Mine is working fine now but blocks are few and far between and the hashrate has gone up tenfold since yesterday. Apparently the torrent file download has helped quite a few people get started mining. |
|
|
|
|
MRKLYE
Legendary
Offline
Activity: 1358
Merit: 1003
Designer - Developer
|
|
April 12, 2015, 09:38:15 AM
Last edit: April 12, 2015, 12:53:54 PM by MRKLYE |
|
I am back up and mining after re-indexing the last hours away. Now to hit some sweet sweet CRE blocks. (2% of the network hash) *Edit: Woot got my first block! I used a deposit to get it though.  *Edit2: Annnd I crashed my computer trying to overclock it and corrupted the blockchain again. fml Be careful and ensure you close down the Bitcredit Client properly else you're gonna have a bad time.. |
|
|
|
Gabriel Eiger (OP)
Sr. Member
Offline
Activity: 280
Merit: 250
Lead developer of Credits [CRE]
|
|
April 12, 2015, 01:12:00 PM |
|
Gabriel, is there any plan to get a working block explorer so people will know if they are on the right fork? The way this coin has issues with syncing it seems that forking is something that could easily occur. Also, are there any official nodes to add to the .conf file to make sure people can sync? What are the plans going forward? You also need to release the source code as binaries only are likely preventing people from getting involved with this coin.
Good suggestions all of them. I'll give a longer answer in a few hours, but a quick summary, absolutely, a block explorer would be a good thing, there are a few official nodes, I'll list them a little later when I have the time. The source will be released soon but I'll continue that discussion when I have the time in a few hours. Thank you for the input. |
|
|
|
Gabriel Eiger (OP)
Sr. Member
Offline
Activity: 280
Merit: 250
Lead developer of Credits [CRE]
|
|
April 12, 2015, 01:17:02 PM |
|
Having a bit of trouble getting this baby fired back up. Log is as follows: 2015-04-12 03:05:14 Bitcoin version v0.9.1.4-gdaa6b7e-beta (Wed, 18 Mar 2015 12:28:57 +0100)
2015-04-12 03:05:14 Bitcredit version v0.9.1.4-gdaa6b7e-beta (Wed, 18 Mar 2015 12:28:57 +0100)
2015-04-12 03:05:14 Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
2015-04-12 03:05:14 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2015-04-12 03:05:14 Default data directory C:\Users\M R KLYE\AppData\Roaming\Bitcredit
2015-04-12 03:05:14 Using data directory C:\Users\M R KLYE\AppData\Roaming\Bitcredit
2015-04-12 03:05:14 Bitcoin using at most 125 connections
2015-04-12 03:05:14 Bitcredit using at most 125 connections
2015-04-12 03:05:14 Bitcoin using 4 threads for script verification
2015-04-12 03:05:14 Bitcredit using 4 threads for script verification
2015-04-12 03:05:14 Bitcoin: Using wallet bitcoin_wallet.dat
2015-04-12 03:05:14 init message: Bitcoin: Verifying wallet...
2015-04-12 03:05:14 CDBEnv::Open : LogDir=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_database ErrorFile=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_db.log
2015-04-12 03:05:14 Deposit: Using wallet deposit_wallet.dat
2015-04-12 03:05:14 init message: Deposit: Verifying wallet...
2015-04-12 03:05:14 CDBEnv::Open : LogDir=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\deposit_database ErrorFile=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\deposit_db.log
2015-04-12 03:05:14 Bitcredit: Using wallet bitcredit_wallet.dat
2015-04-12 03:05:14 init message: Bitcredit: Verifying wallet...
2015-04-12 03:05:14 CDBEnv::Open : LogDir=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_database ErrorFile=C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_db.log
2015-04-12 03:05:14 Bound to [::]:8333
2015-04-12 03:05:14 Bound to 0.0.0.0:8333
2015-04-12 03:05:14 Bound to [::]:9333
2015-04-12 03:05:14 Bound to 0.0.0.0:9333
2015-04-12 03:05:14 init message: Bitcoin: Loading block index...
2015-04-12 03:05:14 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_blocks\index
2015-04-12 03:05:14 Opened LevelDB successfully
2015-04-12 03:05:14 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_chainstate
2015-04-12 03:05:18 Opened LevelDB successfully
2015-04-12 03:05:18 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcoin_chainstatecla
2015-04-12 03:05:18 Opened LevelDB successfully
2015-04-12 03:05:22 Bitcoin: LoadBlockIndexDB(): last block file = 255
2015-04-12 03:05:22 Bitcoin: LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=23, size=7644917, heights=351700...351722, time=2015-04-11...2015-04-11)
2015-04-12 03:05:22 Bitcoin: Checking all blk files are present...
2015-04-12 03:05:23 Bitcoin: LoadBlockIndexDB(): transaction index disabled
2015-04-12 03:05:23 Bitcoin: LoadBlockIndexDB(): hashBestChain=0000000000000000135326495881aced3858dea042b0bf351fe29f1c03bd8a62 height=351722 date=2015-04-11 21:29:30 progress=0.999657
2015-04-12 03:05:23 init message: Bitcoin: Verifying blocks...
2015-04-12 03:05:23 Bitcoin: Verifying last 288 blocks at level 3
2015-04-12 03:06:36 Bitcoin: No coin database inconsistencies in last 209 blocks (155277 transactions)
2015-04-12 03:06:37 bitcoin block index 83461ms
2015-04-12 03:06:37 init message: Bitcredit: Loading block index...
2015-04-12 03:06:37 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_blocks\index
2015-04-12 03:06:37 Opened LevelDB successfully
2015-04-12 03:06:37 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\bitcredit_chainstate
2015-04-12 03:06:37 Opened LevelDB successfully
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): last block file = 0
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=6552, size=3753442, heights=0...6548, time=2015-03-06...2015-04-11)
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): transaction index disabled
2015-04-12 03:06:37 Bitcredit: LoadBlockIndexDB(): hashBestChain=00000000983b1b95f3b177e948e48591c939c17e8764cb72008ee0cf21308a45 height=0 date=2015-03-06 18:04:48 progress=0.000000
2015-04-12 03:06:37 init message: Bitcredit: Verifying blocks...
2015-04-12 03:06:37 bitcredit block index 132ms
2015-04-12 03:06:37 init message: Loading bitcoin wallet...
2015-04-12 03:06:37 nFileVersion = 90100
2015-04-12 03:06:37 Keys: 101 plaintext, 0 encrypted, 101 w/ metadata, 101 total
2015-04-12 03:06:37 bitcoin wallet 156ms
2015-04-12 03:06:37 init message: Loading deposit wallet...
2015-04-12 03:06:37 nFileVersion = 90104
2015-04-12 03:06:37 Keys: 106 plaintext, 0 encrypted, 106 w/ metadata, 106 total
2015-04-12 03:06:38 deposit wallet 157ms
2015-04-12 03:06:38 init message: Loading bitcredit wallet...
2015-04-12 03:06:38 nFileVersion = 90104
2015-04-12 03:06:38 Keys: 125 plaintext, 0 encrypted, 125 w/ metadata, 125 total
2015-04-12 03:06:38 bitcredit wallet 166ms
2015-04-12 03:06:38 Wiping LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\.tmp\bitcoin_chainstatecla.tmp.1
2015-04-12 03:06:38 Opening LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\.tmp\bitcoin_chainstatecla.tmp.1
2015-04-12 03:06:38 Opened LevelDB successfully
2015-04-12 03:06:38 *** Error moving claim tip. Expected active bitcredit block: 0000000000000000000000000000000000000000000000000000000000000000, was: 00000000008e2ade84c6d9f695f1736c022645b3839e7906a572559d75a27c40
2015-04-12 03:06:45 *** ERROR: Bitcredit: ConnectBlock: Failed to move claim tip to 0000000000000000189a6d0d46b0364748c4c2249ba4a3cbb45db99abcbfd2a9
2015-04-12 03:06:45 ERROR: Bitcredit: ConnectTip() : ConnectBlock 000000005fc6f4b75a16b644bc1bd975ec71e7bdfab3144d84915d0efae490d2 failed
2015-04-12 03:06:45 Requesting shutdown
2015-04-12 03:06:45 Wiping LevelDB in C:\Users\M R KLYE\AppData\Roaming\Bitcredit\.tmp\bitcoin_chainstatecla.tmp.1
2015-04-12 03:06:45 init message: Loading bitcoin addresses...
2015-04-12 03:06:45 Loaded 13013 addresses from bitcoin_peers.dat 1430224109615ms
2015-04-12 03:06:45 init message: Loading bitcredit addresses...
2015-04-12 03:06:45 Loaded 86 addresses from bitcredit_peers.dat 1430224109568ms
2015-04-12 03:06:46 Running Shutdown in thread
2015-04-12 03:06:46 Initialization result: 0
2015-04-12 03:06:46 Shutdown : In progress...
2015-04-12 03:06:46 Stopping thread
2015-04-12 03:06:47 StopNode()
2015-04-12 03:06:54 Shutdown : done
2015-04-12 03:06:54 Shutdown finished
2015-04-12 03:06:54 Stopped thread What start up command do I use to fix this..? *edit: I used -reindex and it fired back up again.. and now to wait.. If you see output like the one below (which where in your log sample) it means that the chainstate indexing the state between Bitcredit and Bitcoin has been corrupted. That is not a good thing and is usually an irrecoverable error that only can be fixed by a -reindex or by removing the Bitcredit blockchain and have it downloaded again. We can see that it has been happening quite some times after the initial release. This is rather troublesome and really needs to be addressed soon. A quick release of the source code might help getting more eyes on the code. 2015-04-12 03:06:38 *** Error moving claim tip. Expected active bitcredit block: 0000000000000000000000000000000000000000000000000000000000000000, was: 00000000008e2ade84c6d9f695f1736c022645b3839e7906a572559d75a27c40 2015-04-12 03:06:45 *** ERROR: Bitcredit: ConnectBlock: Failed to move claim tip to 0000000000000000189a6d0d46b0364748c4c2249ba4a3cbb45db99abcbfd2a9 2015-04-12 03:06:45 ERROR: Bitcredit: ConnectTip() : ConnectBlock 000000005fc6f4b75a16b644bc1bd975ec71e7bdfab3144d84915d0efae490d2 failed |
|
|
|
MRKLYE
Legendary
Offline
Activity: 1358
Merit: 1003
Designer - Developer
|
|
April 12, 2015, 01:30:02 PM |
|
I figured as much Gab. This is my 3rd or 4th re-indexing due to having my blockchains implode (due to my own stupidity). Releasing the source code would likely help with bug squashing on your end. Lots of smart neck beards around these parts. I'd go ahead and release the source code if you feel it's right.. Or don't.. I'd like the mining difficulty to stay low so I can get more Bitcredit! |
|
|
|
Gabriel Eiger (OP)
Sr. Member
Offline
Activity: 280
Merit: 250
Lead developer of Credits [CRE]
|
|
April 12, 2015, 01:34:52 PM |
|
I figured as much Gab. This is my 3rd or 4th re-indexing due to having my blockchains implode (due to my own stupidity). Releasing the source code would likely help with bug squashing on your end. Lots of smart neck beards around these parts. I'd go ahead and release the source code if you feel it's right.. Or don't.. I'd like the mining difficulty to stay low so I can get more Bitcredit! In your case it is probably easier to just restart from the torrent that you downloaded, instead of reindexing. Just make sure that you make a security copy of bitcredit_wallet.dat and deposit_wallet.dat and add them to the new working directory before you restart. |
|
|
|
MRKLYE
Legendary
Offline
Activity: 1358
Merit: 1003
Designer - Developer
|
|
April 12, 2015, 01:39:49 PM |
|
I figured as much Gab. This is my 3rd or 4th re-indexing due to having my blockchains implode (due to my own stupidity). Releasing the source code would likely help with bug squashing on your end. Lots of smart neck beards around these parts. I'd go ahead and release the source code if you feel it's right.. Or don't.. I'd like the mining difficulty to stay low so I can get more Bitcredit! In your case it is probably easier to just restart from the torrent that you downloaded, instead of reindexing. Just make sure that you make a security copy of bitcredit_wallet.dat and deposit_wallet.dat and add them to the new working directory before you restart. I have my wallet backed up. Between the CRE you gave me and the block I mined last night feeling pretty awesome! Hell of a battle to get the thing running but being an early adopter of the first soft sidechain coin is pretty damn neat. |
|
|
|
Gabriel Eiger (OP)
Sr. Member
Offline
Activity: 280
Merit: 250
Lead developer of Credits [CRE]
|
|
April 12, 2015, 04:18:53 PM |
|
I figured as much Gab. This is my 3rd or 4th re-indexing due to having my blockchains implode (due to my own stupidity). Releasing the source code would likely help with bug squashing on your end. Lots of smart neck beards around these parts. I'd go ahead and release the source code if you feel it's right.. Or don't.. I'd like the mining difficulty to stay low so I can get more Bitcredit! In your case it is probably easier to just restart from the torrent that you downloaded, instead of reindexing. Just make sure that you make a security copy of bitcredit_wallet.dat and deposit_wallet.dat and add them to the new working directory before you restart. I have my wallet backed up. Between the CRE you gave me and the block I mined last night feeling pretty awesome! Hell of a battle to get the thing running but being an early adopter of the first soft sidechain coin is pretty damn neat. Sounds good. Keep it up. |
|
|
|
MRKLYE
Legendary
Offline
Activity: 1358
Merit: 1003
Designer - Developer
|
|
April 12, 2015, 04:39:54 PM |
|
I figured as much Gab. This is my 3rd or 4th re-indexing due to having my blockchains implode (due to my own stupidity). Releasing the source code would likely help with bug squashing on your end. Lots of smart neck beards around these parts. I'd go ahead and release the source code if you feel it's right.. Or don't.. I'd like the mining difficulty to stay low so I can get more Bitcredit! In your case it is probably easier to just restart from the torrent that you downloaded, instead of reindexing. Just make sure that you make a security copy of bitcredit_wallet.dat and deposit_wallet.dat and add them to the new working directory before you restart. I have my wallet backed up. Between the CRE you gave me and the block I mined last night feeling pretty awesome! Hell of a battle to get the thing running but being an early adopter of the first soft sidechain coin is pretty damn neat. Sounds good. Keep it up. I'm back up and running strong, Got my poor little A8-4500 pumping heat trying to smash blocks. I have a question though. At this point in the game does my having active miner deposits waiting make it more likely for me to get a block? Keep up the great work on the coin, Something innovative in a slew of cloned coins is refreshing and your support with getting us up and going is A+. When you are ready to release the source code I think more people may come on board. The torrent download route makes it quite accessible and fast to start now as well, Thank you for that. Offering my help to anyone who has problems getting the client going. I've become quiet good at wrecking and fixing Bitcredit. |
|
|
|
Gabriel Eiger (OP)
Sr. Member
Offline
Activity: 280
Merit: 250
Lead developer of Credits [CRE]
|
|
April 12, 2015, 04:46:27 PM |
|
I figured as much Gab. This is my 3rd or 4th re-indexing due to having my blockchains implode (due to my own stupidity). Releasing the source code would likely help with bug squashing on your end. Lots of smart neck beards around these parts. I'd go ahead and release the source code if you feel it's right.. Or don't.. I'd like the mining difficulty to stay low so I can get more Bitcredit! In your case it is probably easier to just restart from the torrent that you downloaded, instead of reindexing. Just make sure that you make a security copy of bitcredit_wallet.dat and deposit_wallet.dat and add them to the new working directory before you restart. I have my wallet backed up. Between the CRE you gave me and the block I mined last night feeling pretty awesome! Hell of a battle to get the thing running but being an early adopter of the first soft sidechain coin is pretty damn neat. Sounds good. Keep it up. I'm back up and running strong, Got my poor little A8-4500 pumping heat trying to smash blocks. I have a question though. At this point in the game does my having active miner deposits waiting make it more likely for me to get a block? Keep up the great work on the coin, Something innovative in a slew of cloned coins is refreshing and your support with getting us up and going is A+. When you are ready to release the source code I think more people may come on board. The torrent download route makes it quite accessible and fast to start now as well, Thank you for that. Offering my help to anyone who has problems getting the client going. I've become quiet good at wrecking and fixing Bitcredit. Just a tip, now that you have it running - the number at the end of the setgenerate command - "setgenerate true x" should correspond to the number of physical cores in your machine. In your case, that means "setgenerate true 2". |
|
|
|
|
