Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 79. (Read 284956 times)
June 22, 2014, 01:53:47 AM
https://slm.blockquarry.com is back up and running.
June 22, 2014, 12:32:34 AM
One of my wallets (with around 4000 burnt coins) loads up and syncs fine. However, the moment i unlock it (its encrypted) for minting, it freezes, almost completely. Its still responsive every 4-5 minutes, cpu usage 40 - 100%.
Debug log - this is where it freezes :
SlimCoinAfterBurner():
Smallest Hash is 0000013b33000000000000000000000000000000000000000000000000000001
by tx 97aa4319ba3f2a9e935472b4c19be369968bde9aea34cecc3e7b9b62639d3a79
with Block height 9596, transaction depth 1, vout depth 1
PoB Tartget is 000000022c9a0000000000000000000000000000000000000000000000000000
nBurnBits=1d022c9a, nEffectiveBurnCoins=98769964598 (formatted 98769.964598)
Debug log - this is where it freezes :
SlimCoinAfterBurner():
Smallest Hash is 0000013b33000000000000000000000000000000000000000000000000000001
by tx 97aa4319ba3f2a9e935472b4c19be369968bde9aea34cecc3e7b9b62639d3a79
with Block height 9596, transaction depth 1, vout depth 1
PoB Tartget is 000000022c9a0000000000000000000000000000000000000000000000000000
nBurnBits=1d022c9a, nEffectiveBurnCoins=98769964598 (formatted 98769.964598)
June 22, 2014, 12:31:25 AM
Why is there no difference on my E3-1230V2 use-T4-T8 and speed?
June 22, 2014, 12:07:02 AM
Finally slimcoinpool not getting all the blocks 
Now who's the one instamining.
June 22, 2014, 12:05:13 AM
Client Upgrade for Relaunch and Better Network Propagation
This update finally fixes the network propagation issue. So far, I have done a little testing and it works amazingly! It was a very small bug that I did not notice at first, but now is fixed.
Source Code: https://github.com/slimcoin/slimcoin
Binaries: https://github.com/slimcoin/slicmoin-executable
Once you have updated the wallet
If you are past block 15935, there is no need to delete the files.
Delete your addr.dat, blk0001.dat, and blkindex.dat files in the .slimcoin directory. NOT your wallet.dat file. Add the addnodes on the OP (I will update it) to your slimcoin.conf file and start up the new client. You will have all of your coins before and including block 15935.
If it seems to you that you are missing coins after the update
The first time you start up, run the client with the -rescan flag. That will salvage burnt coins and make them effective again. Also, one it is started, send the rpc command checkwallet. If the output says something about X amount of coins, that means those coins were staked, but then a fork was encountered and they were left on the old fork. If that happens, simple run the repairwallet command and you will salvage those coins back into your wallet so to speak.
This update finally fixes the network propagation issue. So far, I have done a little testing and it works amazingly! It was a very small bug that I did not notice at first, but now is fixed.
Source Code: https://github.com/slimcoin/slimcoin
Binaries: https://github.com/slimcoin/slicmoin-executable
Once you have updated the wallet
If you are past block 15935, there is no need to delete the files.
Delete your addr.dat, blk0001.dat, and blkindex.dat files in the .slimcoin directory. NOT your wallet.dat file. Add the addnodes on the OP (I will update it) to your slimcoin.conf file and start up the new client. You will have all of your coins before and including block 15935.
If it seems to you that you are missing coins after the update
The first time you start up, run the client with the -rescan flag. That will salvage burnt coins and make them effective again. Also, one it is started, send the rpc command checkwallet. If the output says something about X amount of coins, that means those coins were staked, but then a fork was encountered and they were left on the old fork. If that happens, simple run the repairwallet command and you will salvage those coins back into your wallet so to speak.
I updated few hours ago, and i am now at block 16373, do i have to delete the files in conf folder?
or i just update the qt?
I saw:
If you are past block 15935, there is no need to delete the files.
thanks in advance
June 21, 2014, 11:59:45 PM
stake What does it mean?
June 21, 2014, 11:59:34 PM
can mint by burn blocks found by an encrypt wallet？
June 21, 2014, 11:51:19 PM
Why are blocks flying so fast ?
June 21, 2014, 11:46:00 PM
Finally slimcoinpool not getting all the blocks
June 21, 2014, 11:38:03 PM
How is the update working so far?
Working great, no more lag when propagating blocks.
Compile slimminer from here : https://github.com/slimcoin/slimminer
June 21, 2014, 11:35:00 PM
How is the update working so far?
Working great, no more lag when propagating blocks.
June 21, 2014, 11:25:21 PM
How is the update working so far?
Working great, no more lag when propagating blocks.
June 21, 2014, 11:23:51 PM
Nice 200 block instamine...
June 21, 2014, 11:19:05 PM
My nodes are up again.
addnode=144.76.139.103:10001
addnode=144.76.139.104:10001
addnode=144.76.139.105:10001
addnode=144.76.139.106:10001
addnode=144.76.139.107:10001
addnode=144.76.139.108:10001
addnode=144.76.139.109:10001
addnode=144.76.139.110:10001
addnode=144.76.139.111:10001
addnode=144.76.139.103:10001
addnode=144.76.139.104:10001
addnode=144.76.139.105:10001
addnode=144.76.139.106:10001
addnode=144.76.139.107:10001
addnode=144.76.139.108:10001
addnode=144.76.139.109:10001
addnode=144.76.139.110:10001
addnode=144.76.139.111:10001
Keep port 10000 please.
I've changed them already
they are all synced now June 21, 2014, 11:18:17 PM
My nodes are up again.
addnode=144.76.139.103:10001
addnode=144.76.139.104:10001
addnode=144.76.139.105:10001
addnode=144.76.139.106:10001
addnode=144.76.139.107:10001
addnode=144.76.139.108:10001
addnode=144.76.139.109:10001
addnode=144.76.139.110:10001
addnode=144.76.139.111:10001
addnode=144.76.139.103:10001
addnode=144.76.139.104:10001
addnode=144.76.139.105:10001
addnode=144.76.139.106:10001
addnode=144.76.139.107:10001
addnode=144.76.139.108:10001
addnode=144.76.139.109:10001
addnode=144.76.139.110:10001
addnode=144.76.139.111:10001
Keep port 10000 please.
June 21, 2014, 11:15:46 PM
My nodes are up again.
addnode=144.76.139.103:10001
addnode=144.76.139.104:10001
addnode=144.76.139.105:10001
addnode=144.76.139.106:10001
addnode=144.76.139.107:10001
addnode=144.76.139.108:10001
addnode=144.76.139.109:10001
addnode=144.76.139.110:10001
addnode=144.76.139.111:10001
addnode=144.76.139.103:10001
addnode=144.76.139.104:10001
addnode=144.76.139.105:10001
addnode=144.76.139.106:10001
addnode=144.76.139.107:10001
addnode=144.76.139.108:10001
addnode=144.76.139.109:10001
addnode=144.76.139.110:10001
addnode=144.76.139.111:10001
June 21, 2014, 11:12:22 PM
How is the update working so far?
June 21, 2014, 11:11:31 PM
June 21, 2014, 11:06:06 PM
Client Upgrade for Relaunch and Better Network Propagation
This update finally fixes the network propagation issue. So far, I have done a little testing and it works amazingly! It was a very small bug that I did not notice at first, but now is fixed.
Source Code: https://github.com/slimcoin/slimcoin
Binaries: https://github.com/slimcoin/slicmoin-executable
Once you have updated the wallet
If you are past block 15935, there is no need to delete the files.
Delete your addr.dat, blk0001.dat, and blkindex.dat files in the .slimcoin directory. NOT your wallet.dat file. Add the addnodes on the OP (I will update it) to your slimcoin.conf file and start up the new client. You will have all of your coins before and including block 15935.
If it seems to you that you are missing coins after the update
The first time you start up, run the client with the -rescan flag. That will salvage burnt coins and make them effective again. Also, one it is started, send the rpc command checkwallet. If the output says something about X amount of coins, that means those coins were staked, but then a fork was encountered and they were left on the old fork. If that happens, simple run the repairwallet command and you will salvage those coins back into your wallet so to speak.
This update finally fixes the network propagation issue. So far, I have done a little testing and it works amazingly! It was a very small bug that I did not notice at first, but now is fixed.
Source Code: https://github.com/slimcoin/slimcoin
Binaries: https://github.com/slimcoin/slicmoin-executable
Once you have updated the wallet
If you are past block 15935, there is no need to delete the files.
Delete your addr.dat, blk0001.dat, and blkindex.dat files in the .slimcoin directory. NOT your wallet.dat file. Add the addnodes on the OP (I will update it) to your slimcoin.conf file and start up the new client. You will have all of your coins before and including block 15935.
If it seems to you that you are missing coins after the update
The first time you start up, run the client with the -rescan flag. That will salvage burnt coins and make them effective again. Also, one it is started, send the rpc command checkwallet. If the output says something about X amount of coins, that means those coins were staked, but then a fork was encountered and they were left on the old fork. If that happens, simple run the repairwallet command and you will salvage those coins back into your wallet so to speak.
June 21, 2014, 11:02:32 PM
the network is actually looking pretty healthy once synced
Jump to: