I have about 10 times now mate, the hole thing cuz i aint got a single coin yet so i dont need to keep the .dat
its strange it syncs for a bout 3 mins at 3845 all all seems fine but then slips out again back to 3845 of 3999 stuck sync
deleted whole Bloodcoin folder (except wallet.dat if you have coins) ? using wallet 2.2 ? work good here... now on block 3846
|
|
|
try to delete everything except wallet.dat and restart wallet
|
|
|
trying to solo mine until pools update...
|
|
|
pushed to github checkpoint at block 3842 pools please update, and resync blockchain compiling wallet for Windows now
|
|
|
Has yobit updated their wallet, yet?
still waiting for them
|
|
|
waiting for suprnova to update wallet
suprnova already updated also http://blood.idcray.com/ updated (good pool !) waiting for yobit there are many open wallet still with old version please update your wallets waiting for block 4060+ to see if retarget works good on main net
|
|
|
I got confirmation from idcray and from suprnova, they updated to the latest wallet version. I am still waiting to get Yobit confirmation
everyone update your wallet ! if the fork will go well after block 4000, every 60 blocks, retarget to faster block times...(lower difficulty)
we are now at block 3278
|
|
|
salvagewallet just gives me this
 Method not found (code -32601)
What can i do as i dont want to loose my coins
-salvagewallet is a command line argument, not an rpc command so can add it to the .exe but its not recommended, only if you have to. because it will delete all the account infomation while keeping only the private keys
|
|
|
how to import privkey of the old wallet ? is there way to export privkey from the old wallet ?
maybe try to backup wallet.dat, delete blockchain database and chainstate and run the wallet with -salvagewallet -rescan ? if i undertand it suppose to remove account info, and save only private keys i hope we can solve this
|
|
|
i'm testing the fork on local network I am going now to a special event IRL. later publish new wallet source for pools + Yobit and will compile new wallets
|
|
|
i've sent some coins to YoBit, the first time , the smaller amount went well, but another tx, after many hours still is unconfirmed, why ? Happened to me, what I did is I backed up my wallet.dat and delete all my bloodcoin folder in the roaming folder. Then run again the wallet, wait it to be fully synced then replaced the wallet.dat with my back up wallet.dat Edit: you will get your coins back from the unconfirmed transaction. Transaction doesn't exist in explorer. Resync wallet with deleted everything and replaced wallet.dat doesn't work, ends up in same situation. If fork incoming, wait first to recieve my coins back from unconfirmed tx Transaction ID: 3c8db291202d732da0eecca2f6a5e15d172601a051ab7957fb6858bb3b03be79 I see in the debug log of one of the nodes: ERROR: CTxMemPool::accept() : not enough fees 3c8db291202d732da0eecca2f6a5e15d172601a051ab7957fb6858bb3b03be79, 7200 < 21600 it will probably never clear? try to make a new complete wallet, set tx fee highter, import private key of the old wallet... and try to send again ?
|
|
|
Fork incoming... !
for Difficulty retarged update planning for block 6000 (maybe can be sooner.. 5000?) I will post a wallet update by tomorrow
I will contact pools and yobit for making sure that we are ready
|
|
|
i've sent some coins to YoBit, the first time , the smaller amount went well, but another tx, after many hours still is unconfirmed, why ? Happened to me, what I did is I backed up my wallet.dat and delete all my bloodcoin folder in the roaming folder. Then run again the wallet, wait it to be fully synced then replaced the wallet.dat with my back up wallet.dat logocreator please let us know if it worked
|
|
|
there is no POW coin immune to hashrate changes, and luck (except maybe FoldingCoin which is Work Unit based but using bitcoin Counterparty which can be slow TX too)
what have the luck? per day should be generated 3 * 60 * 24 = 4320 blocks. coin for 1.5 days only reached block 2300 that corresponds to one block per minute, rather than three. you are correct Block 2320 time: 1434611092 Block 2359 time: 1434614130 3038 seconds for 40 blocks I need to fix retarget and fork
|
|
|
is the block time 20 sec or 10 min ?
2291 2015-06-18 05:55:03
2292 2015-06-18 05:45:55
there is no POW coin immune to hashrate changes, and luck (except maybe FoldingCoin which is Work Unit based but using bitcoin Counterparty which can be slow TX too)
|
|
|
|