[ANN] Launch-time charts - 57 currencies - cryptometer.org

[CryptoBuck]

Hello Sir,
The CryptoBuck Team has proudly released the CryptoBuck Last Night.  www.cryptobuck.com  I personally have been a fan of your site since it's launch, and do appreciate the time and effort you have put into this project.  We are looking forward to being able to watch the performance of CryptoBuck here on your cryptometer.org

POW/POS
BUK - released 9-2-2013 - first 300 Blocks are Ramp-Up Blocks valued at 1 - Block 301 begins the full reward payout of 33.  Currently at the time of this writing the network is hashing Block 243

[1715235245]

1715235245

[1715235245]

1715235245

[1715235245]

1715235245

[DakotaEllington]

Nice great site! You should add Butterflycoin (BFC)

[kriwest]

Could you add Anoncoin to the list?

[canoe]

Hi All,

I've been away from working on the site for a while but I'm getting back at it again:

1. Over the past week, I started updating all the charts.  I started at the top and now I'm at nibble. I'll keep working my way down the list.  This is requiring tons of re-compiling because a lot of the daemons were updated.  Soon everything should be relatively up to date.  A lot of the currencies are older than 90 days now so the most recent info is in the "All weeks" charts.

2. I've tried to add all the currencies that were requested to the first post.  Let me know if I missed yours.  Since I'm falling behind, I think I will switch to adding currencies based on network hashrate rather than first come first served.

3. The suggestion by SlyWax to separate the coinbase transactions from normal transactions is great and I will do that. 

4. Noticed some donations: 2MNC and 50WDC.   Thanks!

[Whoisthelorax]

bump for importance sake. I would love for someone, even if not the original cryptometer himself, to continue this work as it exposes the bad coins for what they are and the solid coins with good foundation.

Any word? Any other project that is doing similar work?

Thank you so much!

[xchrix]

bump for importance sake. I would love for someone, even if not the original cryptometer himself, to continue this work as it exposes the bad coins for what they are and the solid coins with good foundation.

Any word? Any other project that is doing similar work?

Thank you so much!

i think its a lot and very time consuming work. running all those wallets. maybe someone should do this which already has running the wallet. cryptometer should provide a script for each dev of his own cryptocoin to run it and send the data to the website.

[canoe]

I've added Freicoin to the site:
http://cryptometer.org/freicoin_96_hour_charts.html
http://cryptometer.org/freicoin_90_day_charts.html
http://cryptometer.org/freicoin_104_week_charts.html

I have not taken the demurrage into account yet.  This means the total supply chart is slightly too high.  Since the currency is about a year old, the chart should be approximately 5% lower at the end.  The demurrage is probably based on blocks and not time so to get a precise value, I'll have to look at the algorithm in the Freicoin code.  That's on my todo list now.


In other news, I'm doing another round of updates on the other currencies.

[xchrix]

glad that you are back in the game

I've added Freicoin to the site:
http://cryptometer.org/freicoin_96_hour_charts.html
http://cryptometer.org/freicoin_90_day_charts.html
http://cryptometer.org/freicoin_104_week_charts.html

I have not taken the demurrage into account yet.  This means the total supply chart is slightly too high.  Since the currency is about a year old, the chart should be approximately 5% lower at the end.  The demurrage is probably based on blocks and not time so to get a precise value, I'll have to look at the algorithm in the Freicoin code.  That's on my todo list now.


In other news, I'm doing another round of updates on the other currencies.

[glerant]

I've added Freicoin to the site:
http://cryptometer.org/freicoin_96_hour_charts.html
http://cryptometer.org/freicoin_90_day_charts.html
http://cryptometer.org/freicoin_104_week_charts.html

I have not taken the demurrage into account yet.  This means the total supply chart is slightly too high.  Since the currency is about a year old, the chart should be approximately 5% lower at the end.  The demurrage is probably based on blocks and not time so to get a precise value, I'll have to look at the algorithm in the Freicoin code.  That's on my todo list now.


In other news, I'm doing another round of updates on the other currencies.

Great Site!

It's the first time I have seen it! 

Could you add LeadCoin LDC?

http://bitcointalk.org/index.php?topic=382404.0;all

Quark QRK

https://bitcointalk.org/index.php?topic=260031.0

and Frozen FZ

http://bitcointalk.org/index.php?topic=366762.0


Many, many thanks! 

Many thanks!

[canoe]

Wondering where to point your ASICs?  I added these 8 currencies:

- Zetacoin ZET
- Tigercoin TGC
- AsicCoin ASC
- eMark DEM
- Unobtanium UNO
- Betacoin BET
- JouleCoin XJO
- FireFlyCoin FFC

And of course I updated the charts for the old guys: BTC, NMC, IXC, PPC, TRC, and BTE.

http://cryptometer.org

It seems to me that some of the new coins have a problem with their progressive difficulty algorithm.  They are never hitting their advertised block generation rate.  Rather, they are hitting a different rate and being very consistent about it.  I don't think it's a serious problem because the block generation rate is very stable through increasing and decreasing network hashrates.  But it is not the predicted rate.  If you look at the hourly charts, it looks like the difficulty gets into some sort of alternating loop.  My first guess would be that the window of previous blocks it looks at is too small.

Zetacoin:    Advertised: 30 seconds,   Actual: ~22 seconds
Tigercoin:   Advertised: 45 seconds,   Actual: ~60 seconds
Unobtanium: Advertised: 3 minutes,  Actual: ~48 seconds
FireFlyCoin: Advertised: 60 seconds,  Actual: ~27 seconds

Perhaps those devs should have a look at that.  Or just do some re-branding?


Also, adding these to the request list:
- LeadCoin LDC
- Quark QRK (was already there)
- Frozen FZ

[crazymike79]

Add request

42coin, Potcoin and Craftcoin please

Thanks!

edit: didn't see Craftcoin

[SlyWax]

Could you add MemoryCoin (MMC).

They used a bad parameter at the beginning which resulted in quite a big funny fluctuation, they then changed the algorithm, it's smooth now. Could be interesting.

[canoe]

Added Quark to the site:
http://cryptometer.org/quark_96_hour_charts.html
http://cryptometer.org/quark_90_day_charts.html
http://cryptometer.org/quark_104_week_charts.html


And I added 42coin, Potcoin, and MemoryCoin to the request list.

[canoe]

Could you add MemoryCoin (MMC).

They used a bad parameter at the beginning which resulted in quite a big funny fluctuation, they then changed the algorithm, it's smooth now. Could be interesting.

Added MemoryCoin charts to the site:
http://cryptometer.org/memorycoin_96_hour_charts.html
http://cryptometer.org/memorycoin_90_day_charts.html

Yes, that's interesting.  You can see the fluctuation on the first chart.  I guess they hard-forked at Hour 71?  Sounds stressful!  I'm going to read that giant thread and see what parameter they changed.

[minecrew]

You have a wonderful statistics. People don't speak about it. I'll just start to examine this site. Thanks.

[canoe]

Could you add MemoryCoin (MMC).

They used a bad parameter at the beginning which resulted in quite a big funny fluctuation, they then changed the algorithm, it's smooth now. Could be interesting.

Added MemoryCoin charts to the site:
http://cryptometer.org/memorycoin_96_hour_charts.html
http://cryptometer.org/memorycoin_90_day_charts.html

Yes, that's interesting.  You can see the fluctuation on the first chart.  I guess they hard-forked at Hour 71?  Sounds stressful!  I'm going to read that giant thread and see what parameter they changed.

I found the fix in github.  They replaced the entire algorithm.  It's not a simple parameter change.  I also compared the old algorithm in MemoryCoin with the current algorithms in Unobtanium and Zetacoin.  They are the same.  So that's the problem and how to fix it.

https://github.com/memorycoin/memorycoin/commit/05d26375cb17804bf2fa233678d0bb2dbea6321f

The old algorithm:

Code:

unsigned int static OldGetNextWorkRequired(const CBlockIndex* pindexLast, const CBlockHeader *pblock)
{
    unsigned int nProofOfWorkLimit = bnProofOfWorkLimit.GetCompact();

    // Genesis block
    if (pindexLast == NULL)
        return nProofOfWorkLimit;

    //Change difficulty every block based on the previous nInterval blocks

    //Timewarp bug fix
        // Go back the full period unless it's the first retarget after genesis. Code courtesy of Art Forz
     int nBlocksBack = nInterval-1;
    if((pindexLast->nHeight+1) != nInterval)
        nBlocksBack = nInterval;

     const CBlockIndex* pindexFirst = pindexLast;
    for (int i = 0; pindexFirst && i < nBlocksBack; i++)
         pindexFirst = pindexFirst->pprev;

     //assert(pindexFirst);
        if(pindexFirst==NULL){
        return nProofOfWorkLimit;
        }

    // Limit adjustment step
    int64 nActualTimespan = pindexLast->GetBlockTime() - pindexFirst->GetBlockTime();
    printf("  nActualTimespan = %"PRI64d"  before bounds\n", nActualTimespan);

    if (nActualTimespan < nTargetTimespan*0.8)
        nActualTimespan = nTargetTimespan*0.8;

    if (nActualTimespan > nTargetTimespan*1.2)
        nActualTimespan = nTargetTimespan*1.2;

    // Retarget
    CBigNum bnNew;
    bnNew.SetCompact(pindexLast->nBits);
    bnNew *= nActualTimespan;
    bnNew /= nTargetTimespan;

    if (bnNew > bnProofOfWorkLimit)
        bnNew = bnProofOfWorkLimit;

    /// debug print
    //printf("\n");
    printf("nTargetTimespan = %"PRI64d"    nActualTimespan = %"PRI64d"\n", nTargetTimespan, nActualTimespan);
    printf("Before: %08x  %s\n", pindexLast->nBits, CBigNum().SetCompact(pindexLast->nBits).getuint256().ToString().c_str());
    printf("GetNextWorkRequired RETARGET After:  %08x  %s\n", bnNew.GetCompact(), bnNew.getuint256().ToString().c_str());

    return bnNew.GetCompact();
}

The new algorithm:

Code:

unsigned int static KimotoGravityWell(const CBlockIndex* pindexLast, const CBlockHeader *pblock, uint64 TargetBlocksSpacingSeconds, uint64 PastBlocksMin, uint64 PastBlocksMax) {
    /* current difficulty formula, Anoncoin - kimoto gravity well */
    const CBlockIndex *BlockLastSolved = pindexLast;
    const CBlockIndex *BlockReading = pindexLast;
    const CBlockHeader *BlockCreating = pblock;
BlockCreating = BlockCreating;
    uint64 PastBlocksMass = 0;
    int64 PastRateActualSeconds = 0;
    int64 PastRateTargetSeconds = 0;
    double PastRateAdjustmentRatio = double(1);
    CBigNum PastDifficultyAverage;
    CBigNum PastDifficultyAveragePrev;
    double EventHorizonDeviation;
    double EventHorizonDeviationFast;
    double EventHorizonDeviationSlow;

    if (BlockLastSolved == NULL || BlockLastSolved->nHeight == 0 || (uint64)BlockLastSolved->nHeight < PastBlocksMin) { return bnProofOfWorkLimit.GetCompact(); }

    for (unsigned int i = 1; BlockReading && BlockReading->nHeight > 0; i++) {
        if (PastBlocksMax > 0 && i > PastBlocksMax) { break; }
        PastBlocksMass++;

        if (i == 1) { PastDifficultyAverage.SetCompact(BlockReading->nBits); }
        else { PastDifficultyAverage = ((CBigNum().SetCompact(BlockReading->nBits) - PastDifficultyAveragePrev) / i) + PastDifficultyAveragePrev; }
        PastDifficultyAveragePrev = PastDifficultyAverage;

        PastRateActualSeconds = BlockLastSolved->GetBlockTime() - BlockReading->GetBlockTime();
        PastRateTargetSeconds = TargetBlocksSpacingSeconds * PastBlocksMass;
        PastRateAdjustmentRatio = double(1);
        if (PastRateActualSeconds < 0) { PastRateActualSeconds = 0; }
        if (PastRateActualSeconds != 0 && PastRateTargetSeconds != 0) {
        PastRateAdjustmentRatio = double(PastRateTargetSeconds) / double(PastRateActualSeconds);
        }
        EventHorizonDeviation = 1 + (0.7084 * pow((double(PastBlocksMass)/double(144)), -1.228));
        EventHorizonDeviationFast = EventHorizonDeviation;
        EventHorizonDeviationSlow = 1 / EventHorizonDeviation;

        if (PastBlocksMass >= PastBlocksMin) {
            if ((PastRateAdjustmentRatio <= EventHorizonDeviationSlow) || (PastRateAdjustmentRatio >= EventHorizonDeviationFast)) { assert(BlockReading); break; }
        }
        if (BlockReading->pprev == NULL) { assert(BlockReading); break; }
        BlockReading = BlockReading->pprev;
    }

    CBigNum bnNew(PastDifficultyAverage);
    if (PastRateActualSeconds != 0 && PastRateTargetSeconds != 0) {
        bnNew *= PastRateActualSeconds;
        bnNew /= PastRateTargetSeconds;
    }
    if (bnNew > bnProofOfWorkLimit) { bnNew = bnProofOfWorkLimit; }

    /// debug print
    printf("Difficulty Retarget - Kimoto Gravity Well\n");
    printf("PastRateAdjustmentRatio = %g\n", PastRateAdjustmentRatio);
    printf("Before: %08x %s\n", BlockLastSolved->nBits, CBigNum().SetCompact(BlockLastSolved->nBits).getuint256().ToString().c_str());
    printf("After: %08x %s\n", bnNew.GetCompact(), bnNew.getuint256().ToString().c_str());


    return bnNew.GetCompact();
}

unsigned int static NeoGetNextWorkRequired(const CBlockIndex* pindexLast, const CBlockHeader *pblock)
{
    static const int64 BlocksTargetSpacing = 6 * 60; // 6 minutes
    unsigned int TimeDaySeconds = 60 * 60 * 24;
    int64 PastSecondsMin = TimeDaySeconds*0.25;
    int64 PastSecondsMax = TimeDaySeconds*1;
    uint64 PastBlocksMin = PastSecondsMin / BlocksTargetSpacing;
    uint64 PastBlocksMax = PastSecondsMax / BlocksTargetSpacing;

    return KimotoGravityWell(pindexLast, pblock, BlocksTargetSpacing, PastBlocksMin, PastBlocksMax);
}

[Zzzack]

Awesome! Great info about Quark! Shows that it was never only mined by a few, and network strength was the about the same for months after release!

[SlyWax]

Could you add MemoryCoin (MMC).

They used a bad parameter at the beginning which resulted in quite a big funny fluctuation, they then changed the algorithm, it's smooth now. Could be interesting.

Added MemoryCoin charts to the site:
http://cryptometer.org/memorycoin_96_hour_charts.html
http://cryptometer.org/memorycoin_90_day_charts.html

Yes, that's interesting.  You can see the fluctuation on the first chart.  I guess they hard-forked at Hour 71?  Sounds stressful!  I'm going to read that giant thread and see what parameter they changed.

Thanks, yes the fluctuation was stopping the mining due to high difficulty, FreeTrade applied this fix in just a few day, nice to him.

Buy the way, did you manage to remove the coin creation from the transaction chart, as we talked about before ?

[evoked22]

You should add Netcoin

[canoe]

Buy the way, did you manage to remove the coin creation from the transaction chart, as we talked about before ?

Ok.  I just did it and it was quite easy.  The coinbase transactions are now excluded from the Transactions chart.  I should have done it ages ago.  It really didn't make sense to count the coinbase transactions because the first chart which counts blocks is the same thing as the number of coinbase transactions.  It's much more interesting now.  As I update the different currencies on the site, it will gradually take affect.  Right now, I've only run it on Bitcoin.  To make the transition clear, the old chart is called "Transactions" and the new chart is called "Transactions (non coinbase)".  That way you know if it's applied to a particular currency yet.  Are there any currencies you want me to update first?