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

[s0urcec0de]

how do you decide?

I usually flip a coin or draw straws.

[1714581647]

1714581647

[1714581647]

1714581647

[1714581647]

1714581647

[1714581647]

1714581647

[1714581647]

1714581647

[thunder04839]

how do you decide?

I usually flip a coin or draw straws.

[Kenta]

Anyone else been on the ride with crypto coin?

absolute little gem thats made me 2btc just from my mining

in 2 weeks I think its going higher than it is now,

the whales are definantly there.

new to me.  It is called crypto coin?

yes crypto CRY on bittrex

I found the one that you are talking about actually called cryptcoin.  seems to have a touch of potential but who knows with these days.  where and how do you decided what kinds of coins you will mine next?  I know of a couple of coin calendars but it seems there are so many coming out.  how do you decide?

I think I will give BitSlap a chance today. https://bitcointalk.org/index.php?topic=622985.0

[LTCagt]

block 9121 and syncing - 35 connections

[LTCagt]

ive a few mtgoxcoin - i thought it was dead - can anyone tell me why difficulty is rising there ? strange what kinda a coins outthere

[Nite69]

Yes, the one with the hardfork but there's a new fix for the blockchain stuck and some checkpoint but the new wallet for that is not yet released.

Will that wallet be released before or after the hardfork?

It doesn't have to because it only adds checkpoints of historic blocks. When you are not downloading the entire chain, you don't need it. But for the guys setting up extra nodes to support the network, it makes life a bit easier.

But the code is already released and everyone is free to compile it for Windows if they want

For the hard fork, current version 1.0.1 is enought.

The latest version, however, adds more than just checkpoints. There is 2 other changes:
1) After this, the wallet won't even try to download blocks from old nodes. I think it is safe
now to add this, there is enought nodes with protocol version 60017. It will block out problems
caused by old nodes still alive pushing wrong blocks.
https://github.com/MsCollec/sync/commit/7b8a9864c7ef473f31b075c23c29fc8c7c247d66

2) When I changed the minimum stake difficulty to speed up the blockchain, I missed one point which needed also a modification. It made blockchain stuck at 8200 a bit worse. My fault, but now fixed. The blockchian will still stuck at 8200, but now it will recover when the first new block is found.
https://github.com/MsCollec/sync/commit/e7fca001fd184936ed29b20d4a9d87a6857fa268

No need to update from 1,0,1 to 1,0,2, if you are on the top of the blockchain. But if you are experiencing syncing problems, this should help.

[zmija]

Anyone else been on the ride with crypto coin?

absolute little gem thats made me 2btc just from my mining

in 2 weeks I think its going higher than it is now,

the whales are definantly there.

new to me.  It is called crypto coin?

yes crypto CRY on bittrex

I found the one that you are talking about actually called cryptcoin.  seems to have a touch of potential but who knows with these days.  where and how do you decided what kinds of coins you will mine next?  I know of a couple of coin calendars but it seems there are so many coming out.  how do you decide?

I think I will give BitSlap a chance today. https://bitcointalk.org/index.php?topic=622985.0

looks like interesting coin

[deephouse]

I am on MAC wallet 1.0.1.0. My balance was 0.16 and the icon turned green in 10 mins.  

Staked 0.004 but not credited as it has only 13 confirmations & it needs 50 confirmations.
Now, all my 0.16 coins moved to the Stake section.

Few minutes back I transferred few coins from Bittrex to my wallet and It has come under Spendable.

My question - when does the new amount credited from Bittrex move from Spendable to stake and when it does, how can I bring it back to Spendable.

thanks

[raskul]

Yes, the one with the hardfork but there's a new fix for the blockchain stuck and some checkpoint but the new wallet for that is not yet released.

Will that wallet be released before or after the hardfork?

It doesn't have to because it only adds checkpoints of historic blocks. When you are not downloading the entire chain, you don't need it. But for the guys setting up extra nodes to support the network, it makes life a bit easier.

But the code is already released and everyone is free to compile it for Windows if they want

For the hard fork, current version 1.0.1 is enought.

The latest version, however, adds more than just checkpoints. There is 2 other changes:
1) After this, the wallet won't even try to download blocks from old nodes. I think it is safe
now to add this, there is enought nodes with protocol version 60017. It will block out problems
caused by old nodes still alive pushing wrong blocks.
https://github.com/MsCollec/sync/commit/7b8a9864c7ef473f31b075c23c29fc8c7c247d66

2) When I changed the minimum stake difficulty to speed up the blockchain, I missed one point which needed also a modification. It made blockchain stuck at 8200 a bit worse. My fault, but now fixed. The blockchian will still stuck at 8200, but now it will recover when the first new block is found.
https://github.com/MsCollec/sync/commit/e7fca001fd184936ed29b20d4a9d87a6857fa268

No need to update from 1,0,1 to 1,0,2, if you are on the top of the blockchain. But if you are experiencing syncing problems, this should help.

can you also advise please; previously, when staking has hit an orphan block - my wallet has gone OOS and does not recover until I delete the entire blockchain and resync.

i am not sure if this has been made clear yet, is this issue now fixed?

I having been staking good blocks, i've not staked any orphan blocks since the last time this occurred but an affirmation that this issue is now corrected would be very much appreciated.

thanks.

[wasamata]

I am on MAC wallet 1.0.1.0. My balance was 0.16 and the icon turned green in 10 mins.  

Staked 0.004 but not credited as it has only 13 confirmations & it needs 50 confirmations.
Now, all my 0.16 coins moved to the Stake section.

Few minutes back I transferred few coins from Bittrex to my wallet and It has come under Spendable.

My question - when does the new amount credited from Bittrex move from Spendable to stake and when it does, how can I bring it back to Spendable.

thanks

probably a min of 6 hours from initial deposit (you can check advanced coin control under "options" and then send (input) to see your coin age tree). Once it becomes non spendable it will need 50 confirms again could take a few hour.

[LTCagt]

just to be sure...  

the latest Version is that shown on site 1 ? beacuse my Version although updating is stil 1.0.0.

[Kenta]

Yes, the one with the hardfork but there's a new fix for the blockchain stuck and some checkpoint but the new wallet for that is not yet released.

Will that wallet be released before or after the hardfork?

It doesn't have to because it only adds checkpoints of historic blocks. When you are not downloading the entire chain, you don't need it. But for the guys setting up extra nodes to support the network, it makes life a bit easier.

But the code is already released and everyone is free to compile it for Windows if they want

For the hard fork, current version 1.0.1 is enought.

The latest version, however, adds more than just checkpoints. There is 2 other changes:
1) After this, the wallet won't even try to download blocks from old nodes. I think it is safe
now to add this, there is enought nodes with protocol version 60017. It will block out problems
caused by old nodes still alive pushing wrong blocks.
https://github.com/MsCollec/sync/commit/7b8a9864c7ef473f31b075c23c29fc8c7c247d66

2) When I changed the minimum stake difficulty to speed up the blockchain, I missed one point which needed also a modification. It made blockchain stuck at 8200 a bit worse. My fault, but now fixed. The blockchian will still stuck at 8200, but now it will recover when the first new block is found.
https://github.com/MsCollec/sync/commit/e7fca001fd184936ed29b20d4a9d87a6857fa268

No need to update from 1,0,1 to 1,0,2, if you are on the top of the blockchain. But if you are experiencing syncing problems, this should help.

can you also advise please; previously, when staking has hit an orphan block - my wallet has gone OOS and does not recover until I delete the entire blockchain and resync.

i am not sure if this has been made clear yet, is this issue now fixed?

I having been staking good blocks, i've not staked any orphan blocks since the last time this occurred but an affirmation that this issue is now corrected would be very much appreciated.

thanks.

This happened to me as well, because my wallet started following a fork when internet connection here on Cyprus was intermittent.

The only way to avoid this is to avoid bad nodes, which I think point 1 is an attempt of.

If the coins start staking on a fork, that's not really relevant to our chain and they will not be able to stake "for real" until you connect to the correct chain.

[raskul]

Yes, the one with the hardfork but there's a new fix for the blockchain stuck and some checkpoint but the new wallet for that is not yet released.

Will that wallet be released before or after the hardfork?

It doesn't have to because it only adds checkpoints of historic blocks. When you are not downloading the entire chain, you don't need it. But for the guys setting up extra nodes to support the network, it makes life a bit easier.

But the code is already released and everyone is free to compile it for Windows if they want

For the hard fork, current version 1.0.1 is enought.

The latest version, however, adds more than just checkpoints. There is 2 other changes:
1) After this, the wallet won't even try to download blocks from old nodes. I think it is safe
now to add this, there is enought nodes with protocol version 60017. It will block out problems
caused by old nodes still alive pushing wrong blocks.
https://github.com/MsCollec/sync/commit/7b8a9864c7ef473f31b075c23c29fc8c7c247d66

2) When I changed the minimum stake difficulty to speed up the blockchain, I missed one point which needed also a modification. It made blockchain stuck at 8200 a bit worse. My fault, but now fixed. The blockchian will still stuck at 8200, but now it will recover when the first new block is found.
https://github.com/MsCollec/sync/commit/e7fca001fd184936ed29b20d4a9d87a6857fa268

No need to update from 1,0,1 to 1,0,2, if you are on the top of the blockchain. But if you are experiencing syncing problems, this should help.

can you also advise please; previously, when staking has hit an orphan block - my wallet has gone OOS and does not recover until I delete the entire blockchain and resync.

i am not sure if this has been made clear yet, is this issue now fixed?

I having been staking good blocks, i've not staked any orphan blocks since the last time this occurred but an affirmation that this issue is now corrected would be very much appreciated.

thanks.

This happened to me as well, because my wallet started following a fork when internet connection here on Cyprus was intermittent.

The only way to avoid this is to avoid bad nodes, which I think point 1 is an attempt of.

If the coins start staking on a fork, that's not really relevant to our chain and they will not be able to stake "for real" until you connect to the correct chain.

excellent, thanks.
So, in light of this, that there are bad nodes, is it a good idea for MsCollec to delete the posts which I advise my node address (it's a good node). And for him/her to refuse my node from the OP, when it is actually something which is there to help the Sync community.
Isn't this a tad foolhardy, when my node is good and up to date, and also maintained to ensure it is kept up to date and should not cause any problems for anyone?
I will refrain from personal abuse towards MsCollec, but i fear MsCollec is unable to refrain from directing personal abuse towards me.

my latest stake has just matured - locking up the wallet now to get ready for the fork tomorrow.

It might sound like a good idea, but who will generate new blocks for the blockchain if nobody stakes/mints?

someone other than me   i'm playing it safe, i'm not here to support the group, i'm here to realise an investment.
although there was a time when I would gladly have done some heavy marketing, and done whatever I could to help out. that chance was lost.

asshole!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[nexus00]

Is it just me? or does everyone else sense there are a lot of trolls in this forum who act like they have never used a POS system before.

[Kenta]

Is it just me? or does everyone else sense there are a lot of trolls in this forum who act like they have never used a POS system before.

Some are here to learn (like me) and some are here to troll, sometimes it's very hard to spot the difference.

Whereabouts are you?

[Nite69]

Yes, the one with the hardfork but there's a new fix for the blockchain stuck and some checkpoint but the new wallet for that is not yet released.

Will that wallet be released before or after the hardfork?

It doesn't have to because it only adds checkpoints of historic blocks. When you are not downloading the entire chain, you don't need it. But for the guys setting up extra nodes to support the network, it makes life a bit easier.

But the code is already released and everyone is free to compile it for Windows if they want

For the hard fork, current version 1.0.1 is enought.

The latest version, however, adds more than just checkpoints. There is 2 other changes:
1) After this, the wallet won't even try to download blocks from old nodes. I think it is safe
now to add this, there is enought nodes with protocol version 60017. It will block out problems
caused by old nodes still alive pushing wrong blocks.
https://github.com/MsCollec/sync/commit/7b8a9864c7ef473f31b075c23c29fc8c7c247d66

2) When I changed the minimum stake difficulty to speed up the blockchain, I missed one point which needed also a modification. It made blockchain stuck at 8200 a bit worse. My fault, but now fixed. The blockchian will still stuck at 8200, but now it will recover when the first new block is found.
https://github.com/MsCollec/sync/commit/e7fca001fd184936ed29b20d4a9d87a6857fa268

No need to update from 1,0,1 to 1,0,2, if you are on the top of the blockchain. But if you are experiencing syncing problems, this should help.

can you also advise please; previously, when staking has hit an orphan block - my wallet has gone OOS and does not recover until I delete the entire blockchain and resync.

i am not sure if this has been made clear yet, is this issue now fixed?

I having been staking good blocks, i've not staked any orphan blocks since the last time this occurred but an affirmation that this issue is now corrected would be very much appreciated.

thanks.

This happened to me as well, because my wallet started following a fork when internet connection here on Cyprus was intermittent.

The only way to avoid this is to avoid bad nodes, which I think point 1 is an attempt of.

If the coins start staking on a fork, that's not really relevant to our chain and they will not be able to stake "for real" until you connect to the correct chain.

No, AFAIK, this is not fixed, unless it is a side effect of the problems fixed. I'll put this on the list, and please send me PM if you encounter this with the 1.0.2 version or later.

I'm going to be honest: If this probelms is still there, we might have similar problems after the fork and a some, maybe a lot of you will suffer from this.

I'm trying to figure out what will happen at the fork transition; this might be speculation, but this is how I think it will go (please comment, if you disagree or notice something I did not):

1. the weight paraneters is 1000 times bigger after fork; that means the blockrate will be 1000 times more frequent, until retarget adjusts it. If there is now 6 blocks/hour, the speed will be 6000 blocks/hour, ie a couple of blocks per second. Not sure how long this will stay, it can actually adjust it to preset 1/min within a few minutes.
2. If this lasts long enought, *every* coin online will get stake.. and after that it takes 6 hours to get next.. but I think this won't be the case, adjust will likely be faster. However, just to be sure, it might be good if not everyone is online at the transition time. It's up to you to decide if you want to keep your wallet online.

But there will also be orhpans.. and if there is such problem, we almost certainly will see it when the rate is 2 blocks/second :-(. If this happens to you, I just hope you'll be patient and prepare for it. You''ll anyway get your stake when you get your chain up to date. And you have an option to stay offline at the transition time and start your wallet at will. (if you are interested, I'll keep my online :-)

But before that, I'll do my best to find if this still is a problem. Unfortunately at this timeline and no possibility to test it, most likely I won't find it.

If you all want, we have an option to postpone the fork. My opinion is not to postpone it (there is no reason to assume anything unfixable ḧappens)

Edit: sorry if this is just feeding a troll. If there is no problms with orphan blocks, then the fork is also safe

[Hippie Tech]

Wrong.. Instead of labelling them as "newly generated coins", Block 1 and 2 each had 5 SYNC TX fees.

Has anyone checked to see if this applies here ? --->> https://bitcointalk.org/index.php?topic=444775.0

It could look like money are "generated" by fee's, yes. But nothing is paid out from that fee in block #1, and it makes sense because there wasn't any money in the system.
The same thing happens in block #94, which also has a negative block reward but never gets deducted from any account. I guess block #1 also would have had a negative block reward if moneysupply had been > 0 ?

However, block #1 and block #94 doesn't have any transacted amount. Only block #2 has a transaction to SeSdxid5YnU5P5hCRfT8RFp3jAJJQtMv4u until POW mining starts at block #95 and they are all "minted".

I don't understand why block#2 shows up with a fee when it's all outputted to the dev account, but perhaps the person who made the block explorer could explain? Perhaps it's a bug in the explorer to compensate for that "owed" fee from block#1? I don't think it could show negative fee's? Did anyone find any examples of that?

I had previously presumed that the pre-mine was wrongly coded, that it was set as a tx fee rather than a value, and was amended.
But I could be wrong in my presumption.

It could well be that you are right, and the block#1 was an attempt to mint through fees, but was unsuccessful because of no coins to tax. That would explain why block#2 mints and pays out, but it doesn't explain how the payout also is a fee. But that's very often how programmers work; they test different things and when it works they might just carry on because it takes too much time to analyze every step. "If it is working, don't fix it!"

The coin and blockexplorer were purposely set up that way. eg. there is no way to verify what happened to them. They may as well put up a "This address has too many transactions" messege.

[Hippie Tech]

my latest stake has just matured - locking up the wallet now to get ready for the fork tomorrow.

It might sound like a good idea, but who will generate new blocks for the blockchain if nobody stakes/mints?

someone other than me  i'm playing it safe, i'm not here to support the group, i'm here to realise an investment.
although there was a time when I would gladly have done some heavy marketing, and done whatever I could to help out. that chance was lost.

asshole!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

CONGRATS !! Mr. Ponzi rigged Shitcoin Dev.

You have just earned my negative trust.

Welcome aboard raskul ! lolzzzz

[raskul]

No, AFAIK, this is not fixed, unless it is a side effect of the problems fixed. I'll put this on the list, and please send me PM if you encounter this with the 1.0.2 version or later.

I'm going to be honest: If this probelms is still there, we might have similar problems after the fork and a some, maybe a lot of you will suffer from this.

I'm trying to figure out what will happen at the fork transition; this might be speculation, but this is how I think it will go (please comment, if you disagree or notice something I did not):

1. the weight paraneters is 1000 times bigger after fork; that means the blockrate will be 1000 times more frequent, until retarget adjusts it. If there is now 6 blocks/hour, the speed will be 6000 blocks/hour, ie a couple of blocks per second. Not sure how long this will stay, it can actually adjust it to preset 1/min within a few minutes.
2. If this lasts long enought, *every* coin online will get stake.. and after that it takes 6 hours to get next.. but I think this won't be the case, adjust will likely be faster. However, just to be sure, it might be good if not everyone is online at the transition time. It's up to you to decide if you want to keep your wallet online.

But there will also be orhpans.. and if there is such problem, we almost certainly will see it when the rate is 2 blocks/second :-(. If this happens to you, I just hope you'll be patient and prepare for it. You''ll anyway get your stake when you get your chain up to date. And you have an option to stay offline at the transition time and start your wallet at will. (if you are interested, I'll keep my online :-)

But before that, I'll do my best to find if this still is a problem. Unfortunately at this timeline and no possibility to test it, most likely I won't find it.

If you all want, we have an option to postpone the fork. My opinion is not to postpone it (there is no reason to assume anything unfixable ḧappens)

Edit: sorry if this is just feeding a troll. If there is no problms with orphan blocks, then the fork is also safe

thanks, and no, i'm not trolling, trying to just understand, and learn more about the processes. Your input is appreciated, I, for one, value honesty and in giving us the information prior to any problematic occurrence, you are certainly not feeding trolls, but making sure everyone knows what to expect.

I will however, prefer to leave my wallet locked during the fork, I'm sure there will be many who gather lots of Sync in the speedup, but I think i'd rather stay safe and wait for my stake, after the adjustment kicks in and difficulty retargets.

It certainly sounds like a very delicate operation! Good luck with it, i hope it goes smoothly.

[wasamata]

Was doin a bit of detective work and finally found raskuls real identity at facebook