@primer- Did you start your wallet with --rescan or try repairwallet in the debug console ?
Both, i also had a backup wallet on a debian box - same issue. It syncs up on both windows and linux (both qt and daemon) just fine but once i unlock it for minting it freezes! daemon and qt. linux and windows. Do you have plenty of free CPU and RAM on those PC's when your staking the wallet ? Have you tried downloading a fresh block chain with a blank wallet and then opening with the backup wallet ? Otherwise I would make several backups and try importing the keys as you have suggested. both have 16GB ram, i7 cpu. Tried everything you wrote, did not work  How do i know which public key is associated with my burnt coins ? |
|
|
|
@primer- Did you start your wallet with --rescan or try repairwallet in the debug console ?
Both, i also had a backup wallet on a debian box - same issue. It syncs up on both windows and linux (both qt and daemon) just fine but once i unlock it for minting it freezes! daemon and qt. linux and windows. |
|
|
|
|
How do i figure out which one of my public addresses is linked to the burnt coins ? I want to import it into a new wallet..
|
|
|
|
Why do I burn 6800 coins, which shows the transaction mint by burn, rather than burned? Has been in the immature state.
Status: 163 confirmations
Date: 6/22/2014 20:48
To: SfSLMCoinMainNetworkBurnAddr1DeTK5
Debit: -6839.510068 SLM
Transaction fee: -0.42 SLM
Net amount: -6839.930068 SLM
Transaction ID: 6848581d5e52e376043c575b8b4716169fb67c479ea31b5cf33fb49eba159201
Didnt you read my posts above ? Your client will start freezing soon.. |
|
|
|
|
Dev how do i fix my wallet with 4k burnt coins ?? As soon as its unlocked for minting it freezes!!
|
|
|
|
|
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)
|
|
|
|
|
Why are blocks flying so fast ?
|
|
|
|
Finally slimcoinpool not getting all the blocks  |
|
|
|
|
Nice 200 block instamine...
|
|
|
|
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
Keep port 10000 please. I've changed them already they are all synced now |
|
|
|
|
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
|
|
|
|
|
Killed all my nodes. I'm out.
|
|
|
|
|
ITS BROKEN - same fucking issues, blocks not propagating, wallet freezes when syncing peers, etcetc.
|
|
|
|
|
Node 1
"blocks" : 15974,
Node 2
"blocks" : 15971,
Node 3
{
"blocks" : 15971,
Node 4
"blocks" : 15974,
Node 5
{
"blocks" : 15972,
They are all interconnected, all connections ESTABLISHED via netstat .. blocks are not fucking propagating!!!
|
|
|
|
My ten nodes are all interconnected and two are already fallen behind 2 blocks. Sync problem has not been fixed.
seems even worse than before, i'm out for now Yeah and guess what, you sync one person/1 peer connected to my node and cpu goes to 100% .... |
|
|
|
|
My ten nodes are all interconnected and two are already fallen behind 2 blocks. Sync problem has not been fixed.
|
|
|
|
|
dev what is the current block ?
|
|
|
|
|
Nodes UP!!
addnode=144.76.139.103:10000
addnode=144.76.139.104:10000
addnode=144.76.139.105:10000
addnode=144.76.139.106:10000
addnode=144.76.139.107:10000
addnode=144.76.139.108:10000
addnode=144.76.139.109:10000
addnode=144.76.139.110:10000
addnode=144.76.139.111:10000
|
|
|
|
Mine is at block 500
I am all the time getting
disconnecting node 96.237.174.192:41682
trying connection 96.237.174.192:41682 lastseen=-362056.7hrs
connected 96.237.174.192:41682
socket closed
disconnecting node 96.237.174.192:41682
trying connection 96.237.174.192:41682 lastseen=-362056.8hrs
connected 96.237.174.192:41682
socket closed
disconnecting node 96.237.174.192:41682
trying connection 96.237.174.192:41682 lastseen=-362056.8hrs
connected 96.237.174.192:41682
socket closed
disconnecting node 96.237.174.192:41682
trying connection 96.237.174.192:41682 lastseen=-362056.8hrs
connected 96.237.174.192:41682
socket no message in first 60 seconds, 0 1
disconnecting node 96.237.174.192:41682
The first 500 blocks were downloaded from this 41682 port but the weird thing is that i have this on my conf file
addnode=76.127.202.17:41680
addnode=76.127.202.17
addnode=96.237.174.192
You are a Sr member, you should know better.. |
|
|
|
|
Yeah its not passing any peers to the nodes that are syncing either. I also cant accept connections...
|
|
|
|
|
Show Posts
