Pages:
Author

Topic: [ANN] [eToken] Rare | Website 11 languages | New version -> mandatory update - page 49. (Read 108332 times)

sr. member
Activity: 826
Merit: 250
hero member
Activity: 532
Merit: 500
full member
Activity: 155
Merit: 100
sr. member
Activity: 308
Merit: 250
C surgeons required  Grin

// First version of eToken
// Diff retarget was to high.
static const int64 nTargetTimespan = 7 * 24 * 60 * 60; // eToken: 7d
static const int64 nTargetSpacing = 120; // eToken: 2 minute
static const int64 nInterval = nTargetTimespan / nTargetSpacing;

// New rules 'A' starting on block nRulesAHeight.
// The nTargetSpacing remain the same.
static const int64 nRulesAHeight = 42218;
static const int64 nATargetTimespan = 48 * 60; // 48min - 24 blocks
static const int64 nAInterval = nATargetTimespan / nTargetSpacing;
static const int64 nAdjustDiffMaxUp = 2;
static const int64 nAdjustDiffMaxDown = 4;

//
// minimum amount of work that could possibly be required nTime after
// minimum work required was nBase
//
unsigned int ComputeMinWork(unsigned int nBase, int64 nTime)
{
    // Testnet has min-difficulty blocks
    // after nTargetSpacing*2 time between blocks:
    if (fTestNet && nTime > nTargetSpacing*2)
        return bnProofOfWorkLimit.GetCompact();

    CBigNum bnResult;
    bnResult.SetCompact(nBase);
    while (nTime > 0 && bnResult < bnProofOfWorkLimit)
    {
        bnResult *= nAdjustDiffMaxDown;
        nTime -= nATargetTimespan*nAdjustDiffMaxDown;
    }
    if (bnResult > bnProofOfWorkLimit)
        bnResult = bnProofOfWorkLimit;
    return bnResult.GetCompact();
}
full member
Activity: 154
Merit: 100
Actually, one other option. As the owner of DR etokenpool, I could just switch back to older daemon - if the dev botched this release, we should continue on the stable one (same for other pools)
legendary
Activity: 1512
Merit: 1124
Invest in your knowledge
OP can just delete the failblocks from the block chain, right?

I think not.
It is possible by setting a new checkpoint by minting the block after the failed fork and hardcoding inside the source. Not many other options - it's either that or I have a nice fat etok wallet for sale (few thousand etoks). Smiley

how much
full member
Activity: 140
Merit: 100
OP can just delete the failblocks from the block chain, right?

I think not.
It is possible by setting a new checkpoint by minting the block after the failed fork and hardcoding inside the source. Not many other options - it's either that or I have a nice fat etok wallet for sale (few thousand etoks). Smiley

This was my ideea too. If dev wants to save the coin this is the only way

+1
hero member
Activity: 686
Merit: 500
hero member
Activity: 686
Merit: 500
OP can just delete the failblocks from the block chain, right?

I think not.
It is possible by setting a new checkpoint by minting the block after the failed fork and hardcoding inside the source. Not many other options - it's either that or I have a nice fat etok wallet for sale (few thousand etoks). Smiley

This was my ideea too. If dev wants to save the coin this is the only way
full member
Activity: 182
Merit: 100
May smb provide source code?
full member
Activity: 154
Merit: 100
OP can just delete the failblocks from the block chain, right?

I think not.
It is possible by setting a new checkpoint by minting the block after the failed fork and hardcoding inside the source. Not many other options - it's either that or I have a nice fat etok wallet for sale (few thousand etoks). Smiley
full member
Activity: 140
Merit: 100
.Block mining target: 120 seconds

So why it is not changed in this 1k or 5k blocks?
fail fork dif stuck at lowest
hero member
Activity: 798
Merit: 500
For the last 60 minutes an average of about 3 blocks per second have been mined...

Current number of blocks as I'm posting: 52905
full member
Activity: 182
Merit: 100
.Block mining target: 120 seconds

So why it is not changed in this 1k or 5k blocks?
jr. member
Activity: 70
Merit: 1
Seems that formula for diff change is broken
full member
Activity: 140
Merit: 100
So it was a fault of serveral pool owners?
Nope, check diff on vailderror...


Next Network Block
51834    (Current: 51833)


whales go 1000 more blocks since my last msg...

dif. is low cause pools dont work, too less miners...

nothing f*ed up, only pools down..

How diff could drop so fast?

u say 1000 block dif. drop fast?
dif is alreeady too low.. whales geting block in a sec...

Diff stucked I think, no chnages in 1000 blocks?

more like 5k blocks+
full member
Activity: 182
Merit: 100
So it was a fault of serveral pool owners?
Nope, check diff on vailderror...


Next Network Block
51834    (Current: 51833)


whales go 1000 more blocks since my last msg...

dif. is low cause pools dont work, too less miners...

nothing f*ed up, only pools down..

How diff could drop so fast?

u say 1000 block dif. drop fast?
dif is alreeady too low.. whales geting block in a sec...

Diff stucked I think, no chnages in 1000 blocks?
newbie
Activity: 56
Merit: 0
So it was a fault of serveral pool owners?
Nope, check diff on vailderror...


Next Network Block
51834    (Current: 51833)


whales go 1000 more blocks since my last msg...

dif. is low cause pools dont work, too less miners...

nothing f*ed up, only pools down..

How diff could drop so fast?

u say 1000 block dif. drop fast?
dif is alreeady too low.. whales geting block in a sec...
full member
Activity: 182
Merit: 100
So it was a fault of serveral pool owners?
Nope, check diff on vailderror...


Next Network Block
51834    (Current: 51833)


whales go 1000 more blocks since my last msg...

dif. is low cause pools dont work, too less miners...

nothing f*ed up, only pools down..

How diff could drop so fast?
full member
Activity: 140
Merit: 100
So it was a fault of serveral pool owners?
Nope, check diff on vailderror...


Next Network Block
51834    (Current: 51833)


whales go 1000 more blocks since my last msg...

dif. is low cause pools dont work, too less miners...

nothing f*ed up, only pools down..

join http://etoken.pool.digiraha.ee
Pages:
Jump to: