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

[mikeyfinn]

It is ok to update, one must just do it again, if someone finds some major problem. I assume there won't be any :-)

dafuq? I updated, deleted all but wallet.dat, it synced..showed all transactions...and then my balance is 0? My 1,47 SYNC + all staking is in transactions but is shown as "conflicted"?!

EDIT: Now they are showing to be ok...and it's downloading more blocks...688 remaining..and stuck again

UPDATE: had to restart 3 times in total...fully synced and staking.
P.S. Why the hell is version number still 1.0.0.0?!   So difficult to change it...?

Why are you all deleting everything so you have to re-download the blockchain? Just run the new wallet after backing up the old one.

[1714569593]

1714569593

[1714569593]

1714569593

[1714569593]

1714569593

[1714569593]

1714569593

[Nite69]

Well it solved it until block 8700 anyway

Yes, it seems to stuck at 8200, 8700 and I assume also on 9200 etc..
I'll see what I can do.

But you don't need to delete the blockchain for this update, at least if you update before the hard fork is in effect.
Just run the new version.

[SP4RK7]

I think I have just got into the habit of deleting and re-downloading with this coin

[romeshomey]

The download link is not to the updated wallet.

I still get version v.1.0.0.0

[MsCollec]

The download link is not to the updated wallet.

I still get version v.1.0.0.0

It's updated

[rfcdejong]

Thank you! Think this guy deserves some sort of donation...

Donations are allways wellcome, but you can send them *after* you see the fix works. I would feel embarrassed if something goes wrong

And, if you are a coder, please review it. We can make this safer together.

I checked your changeset, it seems oke as far as i can read it

https://github.com/MsCollec/sync/commit/150f9518586c6cd82d316e85ae0928abc71189e8#diff-fa018f4d28b5116a35b36b72fc9f4e51


CheckStakeKernelHash is changed, will do

bnCoinDayWeight = CBigNum(nValueIn) * GetWeight((int64_t)txPrev.nTime, (int64_t)nTimeTx) / 100000000 / (24 * 60 * 60);
instead of
bnCoinDayWeight = CBigNum(nValueIn) * GetWeight((int64_t)txPrev.nTime, (int64_t)nTimeTx) / 100000 / (24 * 60 * 60);


and the weight is balanced, in GetStakeWeight it will do

bnCoinDayWeight = CBigNum(pcoin.first->vout[pcoin.second].nValue) * nTimeWeight / 100000 / (24 * 60 * 60);
instead of
bnCoinDayWeight = CBigNum(pcoin.first->vout[pcoin.second].nValue) * nTimeWeight / 100000000 / (24 * 60 * 60);



oh you left over some debug print messages

[do0d]

The download link is not to the updated wallet.

I still get version v.1.0.0.0

It's updated

Help | About Sync shows 1.0.0.0

[LTCagt]

its updated although it Shows vers 1.0 - nothimg to worry about - simply you see it if you compare the size of the new one - its a Little bit bigger

[rfcdejong]

The download link is not to the updated wallet.

I still get version v.1.0.0.0

It's updated

Help | About Sync shows 1.0.0.0

indeed i see the same in my windows wallet, v1.0.0.0
going to dive into it why that is as nite69 changed the clientversion.h

how did you compile it MsCollec ? Compiled in linux on msx ?

[zmija]

Anybody knows why r my 0.34 coins not mature and not staking?

[s0urcec0de]

Shows vers 1.0 - nothimg to worry about

Of course its important. Thats why working in software is hard, versioning. Getting everyone on the same update.

[SP4RK7]

Anybody knows why r my 0.34 coins not mature and not staking?

Just leave the wallet unlocked and it will eventually it can take a while to turn green sometimes hours/days

[LTCagt]

Shows vers 1.0 - nothimg to worry about

Of course its important. Thats why working in software is hard, versioning. Getting everyone on the same update.

youre right - but im first interested in working smoothly - i mentioned the vers-nr "Long" ago - its Little to Change - but i wont cry if it doesnt appear

[LTCagt]

if you made it all new from the beginning dont Panic if there are conflicts in the wallet with the payments - that disappear while syncing

[s0urcec0de]

Shows vers 1.0 - nothimg to worry about

Of course its important. Thats why working in software is hard, versioning. Getting everyone on the same update.

youre right - but im first interested in working smoothly - i mentioned the vers-nr "Long" ago - its Little to Change - but i wont cry if it doesnt appear

It's the smallest details. Its a worrying sign that no-one cares imo. I think there must be 20 comments on here reminding the coders of the oversight, yet it seems to be the same according to some.

[do0d]

There's an updated client!  Lets celebrate and not nitpick 

[LTCagt]

smooth and running block 8894 1minute ago BUT DAMN ive forgotten to make a pic of block 8888    

there it goes - and mintpal is great and multipool is the greatest - all smooth and going fine

[Kenta]

yep, it's working!

And now indicating that it considers taking a few coins out for stake!  


Thanks dev!  Sync reborn!

[rfcdejong]

The download link is not to the updated wallet.

I still get version v.1.0.0.0

It's updated

Help | About Sync shows 1.0.0.0

indeed i see the same in my windows wallet, v1.0.0.0
going to dive into it why that is as nite69 changed the clientversion.h

how did you compile it MsCollec ? Compiled in linux on msx ?

the label in the about dialog is called "versionLabel" which is set in the code-behind

https://github.com/MsCollec/sync/blob/master/src/qt/aboutdialog.cpp

Code:

void AboutDialog::setModel(ClientModel *model)
{
    if(model)
    {
        ui->versionLabel->setText(model->formatFullVersion());
    }
}

being called from, but that doesn't matter

https://github.com/MsCollec/sync/blob/3e9aaf65160c7b300e7f3efdafdbf42721ba6d4d/src/qt/bitcoingui.cpp

Code:

void BitcoinGUI::aboutClicked()
{
    AboutDialog dlg;
    dlg.setModel(clientModel);
    dlg.exec();
}

the function for the version is formatFullVersion from util.cpp, line 1269

https://github.com/MsCollec/sync/blob/3e9aaf65160c7b300e7f3efdafdbf42721ba6d4d/src/util.cpp

Code:

string FormatFullVersion()
{
    return CLIENT_BUILD;
}

which is a const in c++ file

https://github.com/MsCollec/sync/blob/3e9aaf65160c7b300e7f3efdafdbf42721ba6d4d/src/version.cpp

and in the header here

https://github.com/MsCollec/sync/blob/0c44e567e511d1ab2989134554484a70e0217d5a/src/version.h


it seems it can be passed in when compiling with make, but i don't have time to experiement, someone else must know already!


So it must be the way MsCollect compiles it.
Maybe someone should look into Gitian build, anyone with experience?

The release process explained in bitcoin doc
https://github.com/bitcoin/bitcoin/blob/5c9078a0defea8bcf84c63c117a53534ab52a311/doc/release-process.md

[LTCagt]

there it goes like rockguitar https://www.mintpal.com/market/SYNC/BTC