Trying something, hold on to your hats.
Mining on full throttle this time?Also gave me an opportunity to test some of my bitcoind/pool performance improvements on a "live" network.
Topic: [ANNOUNCE] New alternate cryptocurrency - Geist Geld - page 29. (Read 74190 times)
Also gave me an opportunity to test some of my bitcoind/pool performance improvements on a "live" network.
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.
In case anyone is wondering what on earth that storm of blocks was, a slightly optimized bitcoind with 9Gh of miners @ diff 0.0625.
Trying something, hold on to your hats.
Mining on full throttle this time? 
Trying something, hold on to your hats.
Hat came off and stopped mining for the time being. =)
Trying something, hold on to your hats.
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
I tink my ISP is trying to contact me. hmmm
He is currently doing it 
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.
You going to release a new version or shall we restart?
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);
}
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.
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
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.
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.
Well, I am currently discussing best way to go about it with sacarlson, and hope ArtForz will suggest something as well.
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*
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.
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*
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!
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*
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
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.
Jump to: