[ANN][1000 SYNC] Proof of Stake now run by BLOCKCHAIN DEVELOPMENT COMPANY

[Soul_eater_123]

Is this another MsCollec scam?
Could someone please summarise?

MsCollec is no longer officially involved.  It's not a scam at all.  It's a very scarce coin with real assets backing it.

[1714679965]

1714679965

[1714679965]

1714679965

[1714679965]

1714679965

[1714679965]

1714679965

[1714679965]

1714679965

[Soul_eater_123]

Is this another MsCollec scam?
Could someone please summarise?

Also whilst I'm no fan of MsCollec - they have made some awful PR/communication blunders, that is not the same as a scam.  At no point has MsCollec been the perpetrator of a scam (as far as I know).

[youngwebs]

guys,

it seems like there is a bug in the new wallet (v1.0.3)

Code:

getblocks 86060 to 00000000000000000000 limit 500
  getblocks stopping at limit 86559 9944c10fd10724975dd1
getblocks 86346 to 00000000000000000000 limit 500
  getblocks stopping at limit 86845 c25de50d8f07581b4c82
getblocks 84560 to 8102e096edd46e2b2dab limit 500
  getblocks stopping at limit 85059 04c267ddee88d7fd2a07
getblocks 85060 to 00000000000000000000 limit 500
  getblocks stopping at limit 85559 4f42fd1dbc9ed0d75eae
getblocks 85060 to 00000000000000000000 limit 500
  getblocks stopping at limit 85559 4f42fd1dbc9ed0d75eae
getblocks 85866 to 00000000000000000000 limit 500
  getblocks stopping at limit 86365 8c550b0ae5fed2d80a73
getblocks 84560 to 8102e096edd46e2b2dab limit 500
  getblocks stopping at limit 85059 04c267ddee88d7fd2a07

and this repeated like thousands and thousands times.. it still syncs, but it's crippling my server with 85% CPU LOAD?
Anyone else seeing this behaviour?

[corsaro]

guys,

it seems like there is a bug in the new wallet (v1.0.3)

Code:

getblocks 86060 to 00000000000000000000 limit 500
  getblocks stopping at limit 86559 9944c10fd10724975dd1
getblocks 86346 to 00000000000000000000 limit 500
  getblocks stopping at limit 86845 c25de50d8f07581b4c82
getblocks 84560 to 8102e096edd46e2b2dab limit 500
  getblocks stopping at limit 85059 04c267ddee88d7fd2a07
getblocks 85060 to 00000000000000000000 limit 500
  getblocks stopping at limit 85559 4f42fd1dbc9ed0d75eae
getblocks 85060 to 00000000000000000000 limit 500
  getblocks stopping at limit 85559 4f42fd1dbc9ed0d75eae
getblocks 85866 to 00000000000000000000 limit 500
  getblocks stopping at limit 86365 8c550b0ae5fed2d80a73
getblocks 84560 to 8102e096edd46e2b2dab limit 500
  getblocks stopping at limit 85059 04c267ddee88d7fd2a07

and this repeated like thousands and thousands times.. it still syncs, but it's crippling my server with 85% CPU LOAD?
Anyone else seeing this behaviour?

CPU load on my server is 88%

Server features a very old CPU, AMD sempron at 1,81 Ghz.

[Soul_eater_123]

I'm sure there must be someone in the community who can help people with there wallet issues?

[corsaro]

I'm sure there must be someone in the community who can help people with there wallet issues?

anyway, consider that my server has a very old CPU, amd sempron at 1,81 Ghz.

on a more recent PC, using sync wallet 1.0.3 , cpu load is 2-3% like other similar crypto-coins wallets.
I think new sync wallet 1.0.3 is OK and working very fine

[mikeyfinn]

People dont realize that just because the earlier wallets still work (1.0.1, etc) they need to ONLY be using either 1.0.3.0 or 1.1.0.0. If you are NOT using one of these and the short new list of nodes, you are on the wrong fork and NOT getting stake....

[fairglu]

and this repeated like thousands and thousands times.. it still syncs, but it's crippling my server with 85% CPU LOAD?
Anyone else seeing this behaviour?

Yes, seeing it on the wallet used by the explorer (which holds no funds, and has "stake=0"), load isn't as high, but it's way higher than other wallets.

Lots of "getblocks stopping at limit" in the debug log.

[effort]

updated wallet and lost  .02  SYNC  i dont know what happened

what do you do ? normally its NOT possible that you lose something by updating

the only Thing is that you have staked on the old blockchain behind block 86400 - but .02 staking then you are a whale

show your wallet please

edited: it could not be stake - its too much

so what have you done ?

we were on a fork.

Now after mandatory wallet update everything is fine --> Windows: https://mega.co.nz/#!NhFh1YYb!dzynF480lycoTkZMex-Lw1kj00WVPzpOovh_Fa3xiMc

If having still problems after update, use this bootstrap file, it is on right blockchain
https://dl.dropboxusercontent.com/u/80376827/bootstrap.dat


https://dl.dropboxusercontent.com/u/80376827/Screenshot%202014-07-28%2023.54.53.png

importing bootstrap data will take a while (some minutes, be patient)

Besides, use these official nodes in Sync.conf
addnode=107.170.51.29
addnode=107.170.206.182
addnode=192.241.244.198

I have issues with the wallet anyway.
if updated to v1.0.3 then it has two Mined Status: conflicted, Debit: 0.00, Net amount: -0.02994215 and -0.0008487. (re-sync - problem is still there), (use of a bootstrap.dat = to complete disaster; the wallet can see the last Received Sync only, after bootstrap).
Btw, the first, out of three Mined, synchronized OK!

If I run v.1.0.2 it has confirmations and Mined are in Credit: +0.00025043 and +0.00000715. But the wallet doesn't synchronize anymore.

'Transaction IDs' are match in both of the cases.
Any ideas?

PS.
Please, SYNC, fix the wallet finally? It takes so much time to find a magical solution for it. It's a headache.

odd. I've had NO problems since just after the end of PoW phase, except for a corrupted wallet, and that was probably from me dicking around with Windows. Got that fixed, have since updated twice, no problems that didn't resolve themselves.

It seems the wallet just don't like some computers. It gave me headaches on my old windows machine, but not one on Linux or on my other windows machine.

You are luckier than me.
Maybe it has something to do with my Mac(?) But I doubt it.
v1.0.2 doesn't synchronize since v1.0.3 came out. Something happened to the Code?
My .conf has plenty of nodes:

server=1
listen=1
rpcuser=user
rpcpassword=pass
rpcport=24240
p2pport=24241
addnode=23.226.225.224
addnode=107.170.10.33
addnode=80.240.140.149
addnode=188.226.243.136
addnode=86.1.252.20
addnode=90.217.94.252
addnode=207.12.89.92
addnode=162.243.157.49
addnode=128.199.189.163
addnode=162.243.103.7
addnode=107.170.51.29
addnode=107.170.206.182
addnode=192.241.244.198
addnode=107.170.124.180
addnode=162.243.214.192
addnode=192.241.240.216
addnode=107.170.159.98
addnode=67.215.8.91

It will not sync because that is the wrong fork. Any coin that you see added via stake after the fork is basically a fake coin and you will not see it in the new wallet once updated.

two days of Sync mining is a waste of time then. new wallet displays them as pale data

[Soul_eater_123]

People dont realize that just because the earlier wallets still work (1.0.1, etc) they need to ONLY be using either 1.0.3.0 or 1.1.0.0. If you are NOT using one of these and the short new list of nodes, you are on the wrong fork and NOT getting stake....

Might also be useful to have an option to turn off staking for low powered/old computers that have issues.  I think the cryptographic part staking might be computationally difficult for older non-optimized and single core CPUs.

[mikeyfinn]

People dont realize that just because the earlier wallets still work (1.0.1, etc) they need to ONLY be using either 1.0.3.0 or 1.1.0.0. If you are NOT using one of these and the short new list of nodes, you are on the wrong fork and NOT getting stake....

Might also be useful to have an option to turn off staking for low powered/old computers that have issues.  I think the cryptographic part staking might be computationally difficult for older non-optimized and single core CPUs.

This might be a dumb question, but why would you need the wallet open at all times if you AREN'T staking?

[mikeyfinn]

two days of Sync mining is a waste of time then. new wallet displays them as pale data
[/quote]

there is no mining of sync, there is only staking (interest). You lost 2 days of interest.

[Soul_eater_123]

People dont realize that just because the earlier wallets still work (1.0.1, etc) they need to ONLY be using either 1.0.3.0 or 1.1.0.0. If you are NOT using one of these and the short new list of nodes, you are on the wrong fork and NOT getting stake....

Might also be useful to have an option to turn off staking for low powered/old computers that have issues.  I think the cryptographic part staking might be computationally difficult for older non-optimized and single core CPUs.

This might be a dumb question, but why would you need the wallet open at all times if you AREN'T staking?

Good point.  If you don't like to wait for the blockchain to update would be the only reason I can think of.

[mikeyfinn]

People, you need to be checking the OP (for those that dont know, OP=Original Post, post one on the thread) for changes. It has the latest wallet and nodes you need. When it says that an update is MANDATORY, maybe you should listen? Just sayin'....

 

[mikeyfinn]

All these people still using the wrong wallets are fucking up the blockchain. My wallet keeps switching between synced and 100ish blocks behind.

[effort]

On my mac new mandatory update 1.0.3 works fine. If you note that 1.0.3 does not synchronize you are probably still on wrong fork due to a bad "blk0001.dat" file

1) close 1.0.3
2) make a backup of the file ~/Library/Application Support/Sync/wallet.dat
3) delete everything from   ~/Library/Application Support/Sync/   except "wallet.dat" and "Sync.conf" (if Sync.conf is not present, create it)
4) check that "Sync.conf" contains only these official nodes:
addnode=107.170.51.29
addnode=107.170.206.182
addnode=192.241.244.198
5) download bootstrap.dat from https://dl.dropboxusercontent.com/u/80376827/bootstrap.dat  and place it inside  ~/Library/Application Support/Sync/
6) open 1.0.3 and wait that bootstrap loads (be patient: it took on my mac at least 30 minutes)
7) as soon as bootstrap import ends, your wallet will synchronize fine

done all this yesterday and again this morning. Works exactly as you described, but the result is still negative. Two of Mined are 'Generated but not accepted Mined'.
v1.0.2 can see Mined and Received coins above them. If the last Received coins would be the wrong fork that would be understandable. But the Mined are credited over 12hrs earlier.

Is there way to fix 'blk0001.dat'? It would be a pity to give up now.
Let's imagine, tomorrow Sync is $10k and next wallet update will conflict couple of Syncs; that will bother a lot! Why Sync wallet is a puzzle? I have no assurance in it now. Take the Dogecoin walet, no puzzles and updates are easy peasy.

[mikeyfinn]

On my mac new mandatory update 1.0.3 works fine. If you note that 1.0.3 does not synchronize you are probably still on wrong fork due to a bad "blk0001.dat" file

1) close 1.0.3
2) make a backup of the file ~/Library/Application Support/Sync/wallet.dat
3) delete everything from   ~/Library/Application Support/Sync/   except "wallet.dat" and "Sync.conf" (if Sync.conf is not present, create it)
4) check that "Sync.conf" contains only these official nodes:
addnode=107.170.51.29
addnode=107.170.206.182
addnode=192.241.244.198
5) download bootstrap.dat from https://dl.dropboxusercontent.com/u/80376827/bootstrap.dat  and place it inside  ~/Library/Application Support/Sync/
6) open 1.0.3 and wait that bootstrap loads (be patient: it took on my mac at least 30 minutes)
7) as soon as bootstrap import ends, your wallet will synchronize fine

done all this yesterday and again this morning. Works exactly as you described, but the result is still negative. Two of Mined are 'Generated but not accepted Mined'.
v1.0.2 can see Mined and Received coins above them. If the last Received coins would be the wrong fork that would be understandable. But the Mined are credited over 12hrs earlier.

Is there way to fix 'blk0001.dat'? It would be a pity to give up now.
Let's imagine, tomorrow Sync is $10k and next wallet update will conflict couple of Syncs; that will bother a lot! Why Sync wallet is a puzzle? I have no assurance in it now. Take the Dogecoin walet, no puzzles and updates are easy peasy.

How many times must it be said? STOP USING 1.0.2!!!! It is the WRONG FORK!!! That means it is a fantasy world that has no basis in reality. Anything you think you earned there AFTER block 86400 DOES NOT COUNT. Stay on the right chain.

[corsaro]

On my mac new mandatory update 1.0.3 works fine. If you note that 1.0.3 does not synchronize you are probably still on wrong fork due to a bad "blk0001.dat" file

1) close 1.0.3
2) make a backup of the file ~/Library/Application Support/Sync/wallet.dat
3) delete everything from   ~/Library/Application Support/Sync/   except "wallet.dat" and "Sync.conf" (if Sync.conf is not present, create it)
4) check that "Sync.conf" contains only these official nodes:
addnode=107.170.51.29
addnode=107.170.206.182
addnode=192.241.244.198
5) download bootstrap.dat from https://dl.dropboxusercontent.com/u/80376827/bootstrap.dat  and place it inside  ~/Library/Application Support/Sync/
6) open 1.0.3 and wait that bootstrap loads (be patient: it took on my mac at least 30 minutes)
7) as soon as bootstrap import ends, your wallet will synchronize fine

done all this yesterday and again this morning. Works exactly as you described, but the result is still negative. Two of Mined are 'Generated but not accepted Mined'.
v1.0.2 can see Mined and Received coins above them. If the last Received coins would be the wrong fork that would be understandable. But the Mined are credited over 12hrs earlier.

Is there way to fix 'blk0001.dat'? It would be a pity to give up now.
Let's imagine, tomorrow Sync is $10k and next wallet update will conflict couple of Syncs; that will bother a lot! Why Sync wallet is a puzzle? I have no assurance in it now. Take the Dogecoin walet, no puzzles and updates are easy peasy.

they are not accepted for the simple reason you mined them under 1.0.2 soon after the mandatory upgrade has been released. So these mined coins, are on a wrong fork, and are not valid on right block chain.

It is normal.

I think you are on right fork now, so leave your wallet opened and unlocked and wait for new mined coins coming in the following days.
It is importanto to use only the mandatory updrade v 1.0.3
Windows: https://mega.co.nz/#!NhFh1YYb!dzynF480lycoTkZMex-Lw1kj00WVPzpOovh_Fa3xiMc

Mac: https://dl.dropboxusercontent.com/u/60507461/Sync-Qt.zip

[Biomech]

On my mac new mandatory update 1.0.3 works fine. If you note that 1.0.3 does not synchronize you are probably still on wrong fork due to a bad "blk0001.dat" file

1) close 1.0.3
2) make a backup of the file ~/Library/Application Support/Sync/wallet.dat
3) delete everything from   ~/Library/Application Support/Sync/   except "wallet.dat" and "Sync.conf" (if Sync.conf is not present, create it)
4) check that "Sync.conf" contains only these official nodes:
addnode=107.170.51.29
addnode=107.170.206.182
addnode=192.241.244.198
5) download bootstrap.dat from https://dl.dropboxusercontent.com/u/80376827/bootstrap.dat  and place it inside  ~/Library/Application Support/Sync/
6) open 1.0.3 and wait that bootstrap loads (be patient: it took on my mac at least 30 minutes)
7) as soon as bootstrap import ends, your wallet will synchronize fine

done all this yesterday and again this morning. Works exactly as you described, but the result is still negative. Two of Mined are 'Generated but not accepted Mined'.
v1.0.2 can see Mined and Received coins above them. If the last Received coins would be the wrong fork that would be understandable. But the Mined are credited over 12hrs earlier.

Is there way to fix 'blk0001.dat'? It would be a pity to give up now.
Let's imagine, tomorrow Sync is $10k and next wallet update will conflict couple of Syncs; that will bother a lot! Why Sync wallet is a puzzle? I have no assurance in it now. Take the Dogecoin walet, no puzzles and updates are easy peasy.

How many times must it be said? STOP USING 1.0.2!!!! It is the WRONG FORK!!! That means it is a fantasy world that has no basis in reality. Anything you think you earned there AFTER block 86400 DOES NOT COUNT. Stay on the right chain.

I'm seeing some confusion here. If I read this correctly, he was using 1.02 as a reference, showing a different balance before upgrading.

Still, It is likely the blocks were produced after the fork, so first off VERYIFY that. If it staked after the update on the wrong chain, well, you wasted some electricity. Not a huge deal, but I understand the annoyance.

However, if you are certain that you have transactions not confirming after the update that are BEFORE block 86400, you have some things to do.

First off, forget blk0001.dat. It's just a piece of the blockchain. It don't matter to recovering your coins. There is one file that you should be concerned with, and another you need. The first is wallet.dat THAT is the one that contains your private keys, and therefore access to every transaction you've made on the blockchain. The other is the configuration file. Get rid of everything else in your data directory and resync.

If that still don't work, use the dumpwallet command to export your wallet to a text file. Reimport it into a new wallet, and all will be well.

[mikeyfinn]

Dumpwallet as a backup, or is it just to be used in case of a corrupted wallet?