[ANNOUNCE] New alternate cryptocurrency - Geist Geld

[smoothie]

You going to release a new version or shall we restart?

[1714048526]

1714048526

[1714048526]

1714048526

[1714048526]

1714048526

[1714048526]

1714048526

[1714048526]

1714048526

[1714048526]

1714048526

[Lolcust]

You going to release a new version or shall we restart?

I believe a new version is in order... Though it might take some time...

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);
    }

Given that I am no programmer and not the author of multicoin, I shall consult sacarlson...

[Bitcoin Oz]

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

He will just ddos it for you. 

[CosicMiner]

He is currently doing it

[CosicMiner]

I tink my ISP is trying to contact me. hmmm

[smoothie]

I tink my ISP is trying to contact me. hmmm

ISP: Sir are you mining GGcoins? Or maybe PornCoins?

If so, sir we need you to stop because bitcoins are crashing!

lol

[CosicMiner]

[ArtForz]

Trying something, hold on to your hats.

[smoothie]

Trying something, hold on to your hats.

Hat came off and stopped mining for the time being. =)

[CosicMiner]

Trying something, hold on to your hats.

Mining on full throttle this time?

[ArtForz]

Ok, done.
In case anyone is wondering what on earth that storm of blocks was, a slightly optimized bitcoind with 9Gh of miners @ diff 0.0625.

[ArtForz]

Trying something, hold on to your hats.

Mining on full throttle this time?

Nope, but before I was always mining @ effective diff 1 due to H==0 checks in my miners and poold.
Also gave me an opportunity to test some of my bitcoind/pool performance improvements on a "live" network.

[smoothie]

Ok, done.
In case anyone is wondering what on earth that storm of blocks was, a slightly optimized bitcoind with 9Gh of miners @ diff 0.0625.

How many blocks u get in that shot?

[ArtForz]

A bit over 3400, around 4 blocks/sec average (= around 13% effective hashrate). bitcoind still starts lagging like hell beyond 3 blocks/sec or so

[CosicMiner]

Trying something, hold on to your hats.

Mining on full throttle this time?

Nope, but before I was always mining @ effective diff 1 due to H==0 checks in my miners and poold.
Also gave me an opportunity to test some of my bitcoind/pool performance improvements on a "live" network.

It was so fast I couldnt read the log output on geistd.

[smoothie]

A bit over 3400, around 4 blocks/sec average (= around 13% effective hashrate). bitcoind still starts lagging like hell beyond 3 blocks/sec or so

Cool. Least we got some benchmarking done.

Good test chain.

Doubt an exchange or pool will jump on this though.

No worries =)

[ArtForz]

Only way I see to fix the "someone produces blocks in the future to fuck with diff" problem is... to narrow the accept window a lot. When moving zombie-i0 to 90 sec/block and retarget every 3h I lowered the window to only allow blocks up to 5 minutes in the future (could've done 15 seconds as well, one benefit of the [somewhat half-assed] NTP support).

edit: 10 seconds or so *should* work for geist. guess miners will simply have to make sure they have a accurate clock on their boxes *g*
edit2: I have some finished-but-needs-more-testing NTP code around here somewhere that I indended for zombie-i0 v1.2, if anyone is interested...

[Lolcust]

edit: 10 seconds or so *should* work for geist. guess miners will simply have to make sure they have a accurate clock on their boxes *g*

Let's try 30 seconds ( Due to sacarlson's kind help I have code for tweaking that stuff via config almost done) and see how bad that fares.

edit2: I have some finished-but-needs-more-testing NTP code around here somewhere that I indended for zombie-i0 v1.2, if anyone is interested...

That's super cool, but integrating NTP  into GG is way over my limited ability

P.S.:

Meanwhile....

Guys, here's a question that crossed my mind - would changing the "adjustment step  limit" from "/4" to some other value benefit a fork with fast blocks, and if so, which approximate value should that be ?

[Lolcust]

Okay guys, I've pushed the version that 1) opens up the whole accept window to .conf manipulation Multicoin-style 2) sets it to 30 secs to git

Could someone give it a quick look to see if I fucked up big time anywhere, and if not, I shall concoct win builds for this beast ASAP

P.S.:

Having update kick in at block x is somewhat above my humble abilities

[JohnDoe]

Meanwhile....

Guys, here's a question that crossed my mind - would changing the "adjustment step  limit" from "/4" to some other value benefit a fork with fast blocks, and if so, which approximate value should that be ?

I've always felt that there's no reason to have a limit when adjusting downwards. If the current hashing rate is less than the required to adjust exactly by /4 then you'll need 2 long retargets to get back to normal speed, but if it can adjust freely then only 1 is needed. Namecoin is currently on this predicament. The next adjustment will be by /4 to 23,500 but the "instant" difficulty (average of the last 120 blocks) is 7,000 so after this very long adjustment cycle there will be yet another long cycle, if the current hash rate remains constant.