[ANNOUNCE] New alternate cryptocurrency - Geist Geld

[smoothie]

Code:

        // Update nTime
        if ((pindexPrev->nHeight+2) % 16 == 0)
            pblock->nTime = max(pindexPrev->GetMedianTimePast()+1, GetAdjustedTime() + 1800);
        else if ((pindexPrev->nHeight+1) % 16 == 0)
            pblock->nTime = pindexPrev->GetMedianTimePast()+1;
        else
            pblock->nTime = max(pindexPrev->GetMedianTimePast()+1, GetAdjustedTime());

*walks away whistling*

LOL did you drop your 50GH on this?

[1714111758]

1714111758

[1714111758]

1714111758

[server]

Code:

        // Update nTime
        if ((pindexPrev->nHeight+2) % 16 == 0)
            pblock->nTime = max(pindexPrev->GetMedianTimePast()+1, GetAdjustedTime() + 1800);
        else if ((pindexPrev->nHeight+1) % 16 == 0)
            pblock->nTime = pindexPrev->GetMedianTimePast()+1;
        else
            pblock->nTime = max(pindexPrev->GetMedianTimePast()+1, GetAdjustedTime());

*walks away whistling*

You again...

[ArtForz]

3Gh, and I'm not orphaning other miners blocks on purpose.

[CosicMiner]

Code:

        // Update nTime
        if ((pindexPrev->nHeight+2) % 16 == 0)
            pblock->nTime = max(pindexPrev->GetMedianTimePast()+1, GetAdjustedTime() + 1800);
        else if ((pindexPrev->nHeight+1) % 16 == 0)
            pblock->nTime = pindexPrev->GetMedianTimePast()+1;
        else
            pblock->nTime = max(pindexPrev->GetMedianTimePast()+1, GetAdjustedTime());

*walks away whistling*

What does this mean?

[smoothie]

3Gh, and I'm not orphaning other miners blocks on purpose.

Did you alter the code or something?

[ArtForz]

Yes, my miners are producing blocks with "creatively adjusted" timestamps.
Using the rules I posted.

[Lolcust]

Um...  I'll see what I can do....

[ArtForz]

Yes, it's supposed to.
But by adjusting the timstamp of the first and last block in each diff period you can make it retarget /4 *every single time*

[smoothie]

Yes, it's supposed to.
But by adjusting the timstamp of the first and last block in each diff period you can make it retarget /4 *every single time*

lol

[CosicMiner]

ddoscoin

[smoothie]

ddoscoin

+1 haha

[ArtForz]

Wow, I stop it for a bit and diff shoots back up to > 120 like instantly...

[smoothie]

Wow, I stop it for a bit and diff shoots back up to > 120 like instantly...

Probably the stupidest diff alg ever. The longer you don't generate a block the harder it gets?lol

EDIT: No offense to the OP.

[Lolcust]

Yes, it's supposed to.
But by adjusting the timstamp of the first and last block in each diff period you can make it retarget /4 *every single time*

Ah, now I understand, thank you.

Verily illustrative and creative, as usual.

ArtForz, first and foremost, I would like to officially invite you to offer your guidance and advice - I am merely a curious n00b, sacarlson is pretty busy, and this experiment could use input from someone like you (other input than cleverly crafted blocks, that is )

Now, as for this particular case, would you kindly answer the following questions:

1) Does this method affect only forks with time-based diff ?

2) Could you please suggest any fixes other than abandoning time-based diff retarget?

3) Would abandoning time-based retarget "fix" it ?

Wow, I stop it for a bit and diff shoots back up to > 120 like instantly...

Probably the stupidest diff alg ever. The longer you don't generate a block the harder it gets?lol

EDIT: No offense to the OP.

Actually, the opposite should be true, LOL

[smoothie]

Yes, it's supposed to.
But by adjusting the timstamp of the first and last block in each diff period you can make it retarget /4 *every single time*

Ah, now I understand, thank you.

Verily illustrative and creative, as usual.

ArtForz, first and foremost, I would like to officially invite you to offer your guidance and advice - I am merely a curious n00b, sacarlson is pretty busy, and this experiment could use input from someone like you (other input than cleverly crafted blocks, that is )

Now, as for this particular case, would you kindly answer the following questions:

1) Does this method affect only forks with time-based diff ?

2) Could you please suggest any fixes other than abandoning time-based diff retarget?

3) Would abandoning time-based retarget "fix" it ?

+1000 Good attitude!

[smoothie]

Yes, it's supposed to.
But by adjusting the timstamp of the first and last block in each diff period you can make it retarget /4 *every single time*

Ah, now I understand, thank you.

Verily illustrative and creative, as usual.

ArtForz, first and foremost, I would like to officially invite you to offer your guidance and advice - I am merely a curious n00b, sacarlson is pretty busy, and this experiment could use input from someone like you (other input than cleverly crafted blocks, that is )

Now, as for this particular case, would you kindly answer the following questions:

1) Does this method affect only forks with time-based diff ?

2) Could you please suggest any fixes other than abandoning time-based diff retarget?

3) Would abandoning time-based retarget "fix" it ?

Wow, I stop it for a bit and diff shoots back up to > 120 like instantly...

Probably the stupidest diff alg ever. The longer you don't generate a block the harder it gets?lol

EDIT: No offense to the OP.

Actually, the opposite should be true, LOL

LOL sure seems that way though. I commend you on your good attitude despite the oversight and artforz exploiting it.

Good learning experience I'd say for all.

[Lolcust]

Well, I am currently discussing best way to go about it with sacarlson, and hope ArtForz will suggest something as well.

[ArtForz]

should be possible to make bitcoins algo work for such short intervals.
Main thing, don't accept blocks that far into the future, current clients are accepting blocks up to 2h in the future. *bad* idea if your retarget interval is 4 minutes.

[Lolcust]

should be possible to make bitcoins algo work for such short intervals.
Main thing, don't accept blocks that far into the future, current clients are accepting blocks up to 2h in the future. *bad* idea if your retarget interval is 4 minutes.

Indeed. Thanks for input.

P.S.:
Sweet mighty Cthulhu, I need to get a   programmer to look after GeistGeld...

Any takers ? Pretty please

[JohnDoe]

Could you explain to us non-programmers what this is supposed to be doing?

Code:

int64 nSubsidy = (GetArgIntxx(50,"-Subsidy") * COIN);
    nSubsidy = nSubsidy + (GetArgIntxx(0,"-Subsidy_small"));
    if (mapArgs.count("-custom_inflation"))
    {
        printf("custom_inflation is set \n");
        if (nHeight > GetArgIntxx(INT_MAX,"-inflation_triger"))
        {
            printf("nHeight > inflation_triger detected \n");
            nSubsidy = GetArgIntxx(0,"-post_Subsidy") * COIN;
            nSubsidy = nSubsidy + (GetArgIntxx(0,"-post_Subsidy_small"));
            if (nHeight > GetArgIntxx(INT_MAX,"-inflation_trigerB"))
            {
                printf("nHeight > inflation_trigerB detected \n");
                nSubsidy = GetArgIntxx(0,"-post_SubsidyB") * COIN;
                nSubsidy = nSubsidy + (GetArgIntxx(0,"-post_SubsidyB_small"));
                if (nHeight > GetArgIntxx(INT_MAX,"-inflation_trigerC"))
                {
                    nSubsidy = (GetArgIntxx(0,"-post_SubsidyC") * COIN) + GetArgIntxx(0,"-post_SubsidyC_small");
                }
            }
        }
        printf("nSubsidy after custom = %lu \n",nSubsidy);
    }