[ANN] SUN COIN - Many Exchanges, Big Price PUMPS, MultiPool paying SUN!

[BTCspoon]

Are you kidding me?

I think he is serious, we are supposed to tremble in front of his broken KGW implementation...shake humans!!

[forzendiablo]

Are you kidding me?

I think he is serious, we are supposed to tremble in front of his broken KGW implementation...shake humans!!

hahah. can anybody check code why KGW didnt work?
i mean anybody that knows how code works

[appleblumpkin]

Are you kidding me?

I think he is serious, we are supposed to tremble in front of his broken KGW implementation...shake humans!!

hahah. can anybody check code why KGW didnt work?
i mean anybody that knows how code works

the Kimoto Gravity well... in this case.. since it is low hash would look something like 1/(1 + (0.7084 * (PastBlocksMass/144)^(-1.228))  this would result in diff retarget after every block.  Dev needs to comment on, at least, the fact that he understands that the KGW isn't being implemented.

[MeGaDoOm]

checking,,, first time working with GitHub though.

Looked in source, for now checking the extended debug-log. it should output something about kgw.
(qtwallet with parameter -debug) BRB ;-)

- debug info not showing kgw output. perhaps no retargetting difficulty (?)
looking further

[MeGaDoOm]

ok, keep in mind i´m not a C dev, but this looks weird to me.
(perhaps i just don´t understand the calculations going on)

unsigned int static GetNextWorkRequired(const CBlockIndex* pindexLast, const CBlock *pblock)
{
        int DiffMode = 1;
        if (fTestNet) {
                if (pindexLast->nHeight+1 >= 50) { DiffMode = 2; }
        }
        else {
                if (pindexLast->nHeight+1 >= 25000) { DiffMode = 2; }
        }
        
        if (DiffMode == 1) { return GetNextWorkRequired_V1(pindexLast, pblock); }
        else if (DiffMode == 2) { return GetNextWorkRequired_V2(pindexLast, pblock); }
        return GetNextWorkRequired_V2(pindexLast, pblock);
}
GetNextWorkRequired_V1 is the old diff routine,
GetNextWorkRequired_V2 is the KGW diff routine and is called when DiffMode becomes 2.
DiffMode becomes 2 when something (current block?) gets above 25000. 

Am i cross eyed?
Can SunCoin DEV check this out?

SUN: SeTwgd1vtkV8suztgc6h8PsUtpMCJHe35J

[linkme]

Yeah its still on the previously announced block number (originally it was going to be block 25000)

if (pindexLast->nHeight+1 >= 25000) { DiffMode = 2; }

DEV Please change and release another update

[MeGaDoOm]

Yeah its still on the previously announced block number (originally it was going to be block 25000)

if (pindexLast->nHeight+1 >= 25000) { DiffMode = 2; }

DEV Please change and release another update

Or he didn´t add the latest and greatest to GitHub yet !?

LOL, this time around it´s : pools check, community check, sun up, dev doublecheck

SUN: SeTwgd1vtkV8suztgc6h8PsUtpMCJHe35J

[MeGaDoOm]

did the dev put a bounty on that, or should i have waited  

SUN: SeTwgd1vtkV8suztgc6h8PsUtpMCJHe35J

[MeGaDoOm]

i just switched to testnet, so KGW should kick in at block 50 but the QT-client keeps crashing on me (so a no go on testnet)
(moved wallet, deleted blockchain and .conf first)
should i have a testnode (node=) for testnet?

if (fTestNet) {
                              if (pindexLast->nHeight+1 >= 50) { DiffMode = 2; }
                             }

[SUNcoinDEVs]

did the dev put a bounty on that, or should i have waited  

SUN: SeTwgd1vtkV8suztgc6h8PsUtpMCJHe35J

yes we put wrong number - too high shortly so it would tak weeks to get to that block. we will fix the code so in 24h the KGW will kick in.

the launch of new code will be delayed by 24h again - but at least more people will have chances to join us now.



you are getting the bounty sure.

[MeGaDoOm]

OP changed (!?)

KGW KICKS IN AT 25000 BLOCK. SUN GODS MADE US FOOLISH PEOPLE THINK OF DIFFERENT NUMBER. WE NEED TO MINE MORE TO SHOW THEM WE WORKSHIP THEIR POWERS.

edit: see next post. Dev will release an update in an hour !

[SUNcoinDEVs]

did the dev put a bounty on that, or should i have waited  

SUN: SeTwgd1vtkV8suztgc6h8PsUtpMCJHe35J

We are aware of the issue, and the block retarget will be changed in the next hour, please wait for an announcement to update. linux release and sources will be updated first then compiled windows and mac wallets will be created.

There was no official bounty as we were waiting for one of our devs to come online and he confirmed the issue was due to the code not being updated since we decided to make the change earlier. We are currently considering changing to block 21210 as we need time for pools and exchanges to update. Oh and You have received a reward anyway

[MeGaDoOm]

did the dev put a bounty on that, or should i have waited  

SUN: SeTwgd1vtkV8suztgc6h8PsUtpMCJHe35J

yes we put wrong number - too high shortly so it would tak weeks to get to that block. we will fix the code so in 24h the KGW will kick in.
the launch of new code will be delayed by 24h again - but at least more people will have chances to join us now.

you are getting the bounty sure.

Thanks man !                                                 

[FanEagle]

Okay, that's interesting.
That means Sun tricked us without the gravity thing?

[MeGaDoOm]

Okay, that's interesting.
That means Sun tricked us without the gravity thing?

Snakes. Why does it always have to be snakes?

[SUNcoinDEVs]

https://github.com/suncoin/suncoin/commit/136c212f96fe2e5ba9ef8e5be69e3576d5b857c0

Block changeover updated, those who are compiling from source should update, otherwise please wait for an announcement for the binaries

[MeGaDoOm]

https://github.com/suncoin/suncoin/commit/136c212f96fe2e5ba9ef8e5be69e3576d5b857c0

Block changeover updated, those who are compiling from source should update, otherwise please wait for an announcement for the binaries

Thanks ! OP still says 25000 though (?)
OK, so 21210 it is !

[tavirosu]

60s block, doesn't it mean it needs about 64h to reach block 2500?!

[MeGaDoOm]

i would say about 1 hour (isn´t 62 blocks about 62 minutes @ 60s a block?)

i hope all pools can update in time. correct me if i´m wrong, but wouldn´t we have a chain fork at hand if the largest pools don´t update in time?

[SUNcoinDEVs]

i would say about 1 hour (isn´t 62 blocks about 62 minutes @ 60s a block?)

i hope all pools can update in time. correct me if i´m wrong, but wouldn´t we have a chain fork at hand if the largest pools don´t update in time?

At the current diff, it will take a lot longer

Linux Binaries updated https://github.com/suncoin/suncoin/releases/download/1.2.1/suncoind