[ANN] GameCoin (GME) - Current version = v0.8.4.2

[elend]

Well it has been a little over 100 blocks but even the current system of looking 576 blocks into the past would work just fine if the coin had a reasonable sized network that was pretty stable. The coin would find it's sweet spot in time.

The real problem is miners chasing the high profitability of whatever the coin of the hour may be. This problem is endemic across the entire market.

I really don't want to hard fork it again as it won't really change anything other than the speed at which it goes from one extreme to the other. I may just leave it as is.

As you say, it may be an idea to ask Sal002 to remove it from coinchoose until the network has time to find it's feet.

Since this is the second time this has happened recently, perhaps you still have it looking back too many blocks... look at all the other coins that have had this massive hash rush thru the past weeks and recovered fine... just a thought but I can't think of many coins that have been hamstrung by this problem, and are still a viable coin.

for example franko had this kind of massive hash- and difficulty swings without harm and without any updates/changes to the client ....

[1714008848]

1714008848

[1714008848]

1714008848

[1714008848]

1714008848

[1714008848]

1714008848

[1714008848]

1714008848

[1714008848]

1714008848

[elend]

i agree with bcx for once. another thing which needs to be done is tompool needs to keep off GME. a stable low hash is far better than a 2 min spike in the hash

You realize that tompool is only like 26Mh/s which is tiny. There are people with 10 times that jumping on the coin. There is no way tompool could get the coin up to 3.1 diff that it is at currently. Work it out first before you are critical.

+1

[elend]

i agree with bcx for once. another thing which needs to be done is tompool needs to keep off GME. a stable low hash is far better than a 2 min spike in the hash

You realize that tompool is only like 26Mh/s which is tiny. There are people with 10 times that jumping on the coin. There is no way tompool could get the coin up to 3.1 diff that it is at currently. Work it out first before you are critical.

actually YOU need to work it out before being critical. tompool themselvs have said  on their website that the multipool will occasionally switch to GME aside from the static GME mining,The mulipool should not switch to gme period! its a chain reaction which will only affect gme not benefit it

YOU say, GME will not profit from, but other people does have other opinions.

[elend]

i agree with bcx for once. another thing which needs to be done is tompool needs to keep off GME. a stable low hash is far better than a 2 min spike in the hash

You realize that tompool is only like 26Mh/s which is tiny. There are people with 10 times that jumping on the coin. There is no way tompool could get the coin up to 3.1 diff that it is at currently. Work it out first before you are critical.

actually YOU need to work it out before being critical. tompool themselvs have said  on their website that the multipool will occasionally switch to GME aside from the static GME mining,The mulipool should not switch to gme period! its a chain reaction which will only affect gme not benefit it

FFS It's pretty obvious that you open your mouth before looking up how many MH/s you need to have before getting to a particular difficulty figure tompool is not capable of achieving more than about 30MH/s

On average it takes (difficulty * 2^32 hashes) to solve each block, so to get to 3.1 diff it means there were 3.1* 2^32 hashes in a 2.5min period, which is many times more than tompool can do.

the peak in GME-network-wide hashing power I noticed was around 450.000 MHs and only a fraction came from Tomspool ...

[elend]

it may be any more than tompool can do, But it does not do GME ANY favours. so it should stay off

This is only your opinion!

And probably you just say that because he is a 0.00%-fee-pool taking away your profits from your partly non-working pool ....

[elend]

it may be any more than tompool can do, But it does not do GME ANY favours. so it should stay off

You are nothing but a troll aren't you, you have no idea when tompool was even last on GME, you just want to promote your own pool by trying to discredit the pools that actually helped when the coin was relaunched. Welcome to my ignore list.

exactly

+1

[elend]

Has anyone asked CoinChoose to delist GME?

~BCX~

hopefully not

[erk]

We seem to have runway low diff again.

0.07584385 and falling. I suspect a time warp attack from a solo miner, and fork.

[meta.p02]

We have address GXXTCTVdr8VwiF2s1fjQ4i2FLyL6azUaRi with 116 blocks and address GeUhKC1g5HMhgRMwf6xBtc1TKYGZChzXBw with 673 blocks. In addition, many blocks go to "UNKNOWN" in the block explorer (like 67357).

P.S. Diff is at 0.060 right now, bounced off 0.026 at 13:06 UTC and recovering.

[bluestang]

I really hate you hoppers and jumpers and multi pool type miners! Come in here with your fucking opinions and shit about the coin, yet don't mine it when it needs you the most!

Be loyal to the coin or just STFU!!!!

[erk]

I really hate you hoppers and jumpers and multi pool type miners! Come in here with your fucking opinions and shit about the coin, yet don't mine it when it needs you the most!

Be loyal to the coin or just STFU!!!!

I refuse to miner GME anymore, it's always under attack. (Or way off block time)

[bluestang]

Stop running you mouth then!

[erk]

Stop running you mouth then!

Give up with the attitude welcome to the ignore list.

Meanwhile I would say GME has just been attacked again with low diff injections, most likely someone solo so the destination shows as UNKNOWN on http://gme.p2pool.nl/chain/Gamecoins  I notice that p2pool blocks also come up as UNKNOWN there. Normal pool blocks fill in the address. The diff stopped falling about block 67258 where the chain looks a bit messy. 3 forks?

[bluestang]

Stop running you mouth then!

Give up with the attitude welcome to the ignore list.

Stating facts that you don't like is not an attitude.

[Petr1fied]

GameCoin is not under attack, it just went to the top of coinchoose in a big way. When I first looked at the page the profitability was over 4000%.

People can't be bothered mining GameCoin when the difficulty is higher so the average time per block (calculated over 576 blocks) is much longer than 2.5 minutes so the difficulty will keep falling until the tipping point is reached at which point it reverses. Now the opposite is true. The difficulty will just keep going up until the average over the last 576 blocks is 2.5 minutes.

If people don't care enough to continue mine it so that it can find a sweet spot, this pattern will just keep repeating. if you want it to stabilize, stop coinchoose watching and continue to mine it.

[erk]

GameCoin is not under attack, it just went to the top of coinchoose in a big way. When I first looked at the page the profitability was over 4000%.

People can't be bothered mining GameCoin when the difficulty is higher so the average time per block (calculated over 576 blocks) is much longer than 2.5 minutes so the difficulty will keep falling until the tipping point is reached at which point it reverses. Now the opposite is true. The difficulty will just keep going up until the average over the last 576 blocks is 2.5 minutes.

If people don't care enough to continue mine it so that it can find a sweet spot, this pattern will just keep repeating. if you want it to stabilize, stop coinchoose watching and continue to mine it.

You must be joking, I sat there for about half an hour watching the hash rate go up, and the difficulty go down. Explain that?  There records are all there in the block explorer for the world to see.

The reason it suddenly leaped up on Coinchoose was because of the crazy falling difficulty.

[Petr1fied]

You clearly don't understand the way it works. The average block time is calculated over the last 576 blocks which under perfect circumstances would be 24 hours worth of blocks. Let me give you an example:

I'll start with block 67,000 as it's a nice round number and the difficulty was still falling at this point. The timestamp of this block was 1379249098 (Sun, 15 Sep 2013 12:44:58 GMT). The block 576 blocks behind this (66424) had a timestamp of 1379003057 (Thu, 12 Sep 2013 16:24:17 GMT). now already you must be able to clearly see that this is well over 24 hours. It's actually 4 hours shy of 3 days.

The target block time in GME is 2.5 minutes (150 seconds) so lets see what the average is between these 2 points:

1379249098 - 1379003057 = 246041

OK so there were 576 blocks so lets divide it by that number.

246041 / 576 = 427.15~

So there you have it. The average block time over the span of those 576 blocks was 427.15~ seconds per block which is over 2.84 times what it should be hence the difficulty continues to fall until this number is under 150 at which point it reverses.

If there were more than a few people consistently mining it instead of jumping ship the moment the difficulty went too high then the coin would find a sweet spot but all anyone cares about is what coinchoose says is the most profitable coin to mine at that specific moment.

[erk]

You clearly don't understand the way it works. The average block time is calculated over the last 576 blocks which under perfect circumstances would be 24 hours worth of blocks. Let me give you an example:

I'll start with block 67,000 as it's a nice round number and the difficulty was still falling at this point. The timestamp of this block was 1379249098 (Sun, 15 Sep 2013 12:44:58 GMT). The block 576 blocks behind this (66424) had a timestamp of 1379003057 (Thu, 12 Sep 2013 16:24:17 GMT). now already you must be able to clearly see that this is well over 24 hours. It's actually 4 hours shy of 3 days.

The target block time in GME is 2.5 minutes (150 seconds) so lets see what the average is between these 2 points:

1379249098 - 1379003057 = 246041

OK so there were 576 blocks so lets divide it by that number.

246041 / 576 = 427.15~

So there you have it. The average block time over the span of those 576 blocks was 427.15~ seconds per block which is over 2.84 times what it should be hence the difficulty continues to fall until this number is under 150 at which point it reverses.

If there were more than a few people consistently mining it instead of jumping ship the moment the difficulty went too high then the coin would find a sweet spot but all anyone cares about is what coinchoose says is the most profitable coin to mine at that specific moment.

How does that theory explain why the difficulty was well below 1 for several thousand blocks of high hash rate when it's only supposed to be a 576 block average?


GME roller coaster just fed millions of coins to some UNKNOWN address in minutes. I would call that an exploit.

You don't just suddenly drive at 100mph down the motorway because you spent an hour stuck in crawling traffic.
The function of the diff adjustments is to keep the block time as close to 2.5min as possible, not to appease some 24hour average by having wild swings between seconds and almost an hour per block which is what the last few blocks have been.


67781   2013-09-15 21:20:40   
67780   2013-09-15 20:25:40
67779   2013-09-15 19:31:04

 

[Petr1fied]

It's not a theory it's fact. If you don't understand the maths behind it then you really shouldn't continue trying to argue against it.

[erk]

It's not a theory it's fact. If you don't understand the maths behind it then you really shouldn't continue trying to argue against it.

Oh I understand the theory alright, I have looked though your code, and I also understand what the block chain timestamps are telling me.  

Block 66792  timestamp 1379244162
Block 67368  timestamp 1379250767

That's 576 blocks in 6,605sec or 11.47sec per block, an easy 576,000 coins.

Good luck with your roller coaster I am out of here.