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

[turner3d]

I really didn't want to hop into the club of those having issues, but it seems that I must. At the time of this writing, Sync is on block 8607.

It took me a great deal of time and effort to get the wallet to sync past block 8234. Like many, I was stuck at block 8234 for countless restarts and data deletions with the latest wallet, port 24241 open and forwarded, conf file in place, etc. I finally got my wallet almost synced by writing a script to generate a PeerBlock blacklist the IPs of peers with non-current wallets. Unless I'm reading it all wrong, the current block count of a peer's wallet can be determined by lines in debug.log like the following:

receive version message: version 60016, blocks=8607, us=xxx.xxx.xxx.xxx:50541, them=yyy.yyy.yyy.yyy:24241, peer=yyy.yyy.yyy.yyy:24241

Examining IPs from the sync.conf that's floating around this thread reveals the following information about the node IPs it contains:

addnode=162.243.214.192 - could not connect
addnode=192.241.240.216 - stuck on block 8234
addnode=188.226.192.115 -current at block 8607
addnode=188.226.243.136 - stuck on block  8234
addnode=107.170.159.98 - stuck on block 8599 (like me)
addnode=23.226.225.224 - could not connect


Compiling a list of all connectable peers provides the following list of current block: number of clients on that block:

4040: 1
5903: 1
7204: 1
7205: 3
7206: 22
7603: 1
8200: 10
8210: 3
8214: 8
8215: 15
8233: 1
8234: 5
8287: 2
8328: 1
8349: 1
8416: 1
8445: 1
8446: 1
8460: 1
8465: 1
8467: 1
8483: 1
8512: 1
8520: 1
8537: 1
8555: 3
8558: 2
8559: 1
8563: 1
8590: 1
8598: 6
8599: 7
8600: 16
8601: 2
8602: 3
8603: 21
8604: 3
8606: 13
8607: 15

As you can see, they're all over the place. These don't appear to be clients actively engaged in a wallet update - most of the lower values seem to be stuck there. I was able to get myself up to block 8599, but it won't go any farther. Any time the wallet receives a new block from one of the peers that's caught up to the current block, I get a message in debug.log like this:

received block daefa843fc3985b7a020
Misbehaving: yyy.yyy.yyy.yyy:24241 (0 -> 100) DISCONNECTING
disconnecting node yyy.yyy.yyy.yyy:24241
ERROR: ProcessBlock() : block with too little proof-of-stake

This leaves me currently only 8 blocks behind at block 8599, but apparently stuck again - is this a normal behavior? If not, hopefully this information will be useful to the dev(s).

[1714571253]

1714571253

[1714571253]

1714571253

[1714571253]

1714571253

[raskul]

So what was the big news that was promised for yesterday? It's not another youtube video is it?

it was going to be the announcement that your mom has a big flappy twat, but since I left my underwear in her bed, I refrained from posting it as I didn't want to be found out  

Did you put your pants on today? You've been cryin' like a bitch the last couple days. 

i know, she gave me an STD, probably from sucking your dick.

Russell Gray Sneddon, 39? I had you pegged at 14. Another d-bag with a camera that thinks he's an artist.

  wanna compare earnings; arsewipe? i'm doing OK for a 14 year old douchebag
 

[raskul]

addnode=162.243.214.192 - could not connect
addnode=192.241.240.216 - stuck on block 8234
addnode=188.226.192.115 -current at block 8607
addnode=188.226.243.136 - stuck on block  8234
addnode=107.170.159.98 - stuck on block 8599 (like me)
addnode=23.226.225.224 - could not connect

WTF? my node is the only one on the current block?

blackmail time   LOL kidding

we at 8611 currently

[sovie]

addnode=162.243.214.192 - could not connect
addnode=192.241.240.216 - stuck on block 8234
addnode=188.226.192.115 -current at block 8607
addnode=188.226.243.136 - stuck on block  8234
addnode=107.170.159.98 - stuck on block 8599 (like me)
addnode=23.226.225.224 - could not connect

WTF? my node is the only one on the current block?

blackmail time   LOL kidding

we at 8611 currently

I can confirm my 2 wallets say 8611 as does the blockchain
have you got the correct wallet from the Original page of this thread?

[dbt1033]

[raskul]

Just to advise, I got off my arse and PM'd the dev of the paper wallet (as MsCollec and the rest of the dev team seemed unable to attend to this issue).

PREVIOUS ISSUES WITH THE PAPER WALLET NOT IMPORTING PRIVATE KEYS ARE NOW RECTIFIED.
YOU MAY NOW USE THE PAPER WALLET IF YOU SO WISH.

you're welcome 

[dbt1033]

Just to advise, I got off my arse and PM'd the dev of the paper wallet (as MsCollec and the rest of the dev team seemed unable to attend to this issue).

PREVIOUS ISSUES WITH THE PAPER WALLET NOT IMPORTING PRIVATE KEYS ARE NOW RECTIFIED.
YOU MAY USE THE PAPER WALLET.

Glad to see you are still here btw

[raskul]

Just to advise, I got off my arse and PM'd the dev of the paper wallet (as MsCollec and the rest of the dev team seemed unable to attend to this issue).

PREVIOUS ISSUES WITH THE PAPER WALLET NOT IMPORTING PRIVATE KEYS ARE NOW RECTIFIED.
YOU MAY USE THE PAPER WALLET.

Glad to see you are still here btw

some fucker has to do shit, huh? 

[dbt1033]

I haven't lost faith in the Dev team...yet. 

I'm giving them a chance to impress, MsCollec and Loljosh are using their real forum names at least...

Let's see if they release some form of "big news" in the next week.

Until then, I'm cool with them.

[raskul]

I haven't lost faith in the Dev team...yet. 

I'm giving them a chance to impress, MsCollec and Loljosh are using their real forum names at least...

Let's see if they release some form of "big news" in the next week.

Until then, I'm cool with them.

i'm dubious, although I haven't lost confidence in them completely - as far as i'm concerned Sync is working fine - I like the long confirmation time (as it forces the 'long-term' idealism), so they have delivered a very worthwhile coin. We are slowly getting the smaller issues fixed, and i'm sure the V21 wallet will sort out the main problem. I'm still here.

[MsCollec]

does any have less than 0.3 SYNC and they are staking?

[raskul]

does any have less than 0.3 SYNC and they are staking?

may I point out a piece of your code;

Code:

+static const int64_t MAX_MINT_PROOF_OF_STAKE = 0.01 * COIN;	// 1% annual interest
 +static const int64_t MAX_MINT_PROOF_OF_STAKE_FORKED = 1 * COIN;	// 100% annual interest

i shouldn't need to explain what this means, but I note this code is active.

[mikeyfinn]

does any have less than 0.3 SYNC and they are staking?

may I point out a piece of your code;

Code:

+static const int64_t MAX_MINT_PROOF_OF_STAKE = 0.01 * COIN;	// 1% annual interest
 +static const int64_t MAX_MINT_PROOF_OF_STAKE_FORKED = 1 * COIN;	// 100% annual interest

i shouldn't need to explain what this means, but I note this code is active.

If I could code I'd fix stuff like that and send pull request. Anyone? Beuller?

[nongdanvoz]

my wallet still out of sync

Open and close, again, again, ... 

[nongdanvoz]

Tell me another nodes plz

[YAdaminer]

Wallet is out of sync, again. Stuck at block 8559 and this is not even funny any more.
I don't know where is the problem but this is just pain in the ass.
And it seems that only staking causing problems.
Fortunately I have only 1.3 sync in wallet so I can dump this shit I have on mint.

[biohammer]

Wallet currently disabled on Bittrex   ....Nice

[YAdaminer]

Do you have the conf? If notmake Sync.conf and copy this inside:

server=1
listen=1
rpcuser=user
rpcpassword=pass
rpcport=24240
addnode=162.243.214.192
addnode=192.241.240.216
addnode=188.226.192.115
addnode=188.226.243.136
addnode=107.170.159.98
addnode=23.226.225.224

Yes I have conf, I was deleting, files from roaming directory to get wallet sync, I was doing that 3 times today until I got wallet synced and when staking begun wallet goes out of sync, so my conclusion is that when staking/minting starts wallet falls in problems.

[Biomech]

Is it 1% or 100% POS per year?  I have seen both numbers floating around.

Bro it tells u on OP.did u read that at all

I really think a lot of people don't. I wonder if this is how they do their investing? No homework just do it for me.

One could hope so...

[Kenta]

I really didn't want to hop into the club of those having issues, but it seems that I must. At the time of this writing, Sync is on block 8607.

It took me a great deal of time and effort to get the wallet to sync past block 8234. Like many, I was stuck at block 8234 for countless restarts and data deletions with the latest wallet, port 24241 open and forwarded, conf file in place, etc. I finally got my wallet almost synced by writing a script to generate a PeerBlock blacklist the IPs of peers with non-current wallets. Unless I'm reading it all wrong, the current block count of a peer's wallet can be determined by lines in debug.log like the following:

receive version message: version 60016, blocks=8607, us=xxx.xxx.xxx.xxx:50541, them=yyy.yyy.yyy.yyy:24241, peer=yyy.yyy.yyy.yyy:24241

Examining IPs from the sync.conf that's floating around this thread reveals the following information about the node IPs it contains:

addnode=162.243.214.192 - could not connect
addnode=192.241.240.216 - stuck on block 8234
addnode=188.226.192.115 -current at block 8607
addnode=188.226.243.136 - stuck on block  8234
addnode=107.170.159.98 - stuck on block 8599 (like me)
addnode=23.226.225.224 - could not connect


Compiling a list of all connectable peers provides the following list of current block: number of clients on that block:

....

As you can see, they're all over the place. These don't appear to be clients actively engaged in a wallet update - most of the lower values seem to be stuck there. I was able to get myself up to block 8599, but it won't go any farther. Any time the wallet receives a new block from one of the peers that's caught up to the current block, I get a message in debug.log like this:

received block daefa843fc3985b7a020
Misbehaving: yyy.yyy.yyy.yyy:24241 (0 -> 100) DISCONNECTING
disconnecting node yyy.yyy.yyy.yyy:24241
ERROR: ProcessBlock() : block with too little proof-of-stake

This leaves me currently only 8 blocks behind at block 8599, but apparently stuck again - is this a normal behavior? If not, hopefully this information will be useful to the dev(s).

Thanks for telling!

addnode=188.226.243.136 is updated.

It's not too easy now as there's so many traps/forks around. The one at 8599 is really a blind-gate and I had to delete the entire folder several times to get around it.
Hopefully the new wallet will give us a more steady block creation.