[LOGIC] Logicoin | Decentralized Anonymous Smart Contracts | Blockchain Tech

[myagui]

Do you have anything that will back up your claims ?

DGW is making its adjustments based on the pool's reported hashpower. Your statement is illogical..

You do not seem to understand how difficulty adjustments are performed. A pool does not "make" any network difficulty adjustments. The issues with "fake shares" and "shares below target", only affect the buggy pool itself and the miners on it, the network could not care less for these bugs.

The network, relying on DGW, makes adjustments based on the time that it took to solve previous blocks, and then estimating the nethash so that the new difficulty results in block solving at the desired rate.

Multipools hopping on and off are a well known problem. For a coin that has a modest nethash, when a multipool joins, difficulty will be through the roof. When the multipool jumps off, the network will have a hard time solving the next block. This is completely expected. Smart (or rather, ethical?) multipools, only jump on coins that have enough nethash to not be "catastrophically" impacted by the multipool. Does not seem to be the case with "trade my bit", but I honestly don't know of their motivations or if they care. No offense intended really.

Hope this helps settle your concerns.
Happy mining,
~ Myagui

[1715004926]

1715004926

[Logicoin.info]

Thanks for the explanation guys. Hopefully that should clear up any confusion.


Things are still not ideal but they are looking much much better http://chainz.cryptoid.info/lgc/#

If you want to look at it the other way it seems we are still profitable enough that a multipool would mine us even with the adjusted block reward.

[fairglu]

5limi was a constant contributor to hashrate though. Unlike trade my bit they didn't jump off to another coin when difficulty raised which is the main problem as it leaves the difficulty out of whack with the hashrate.

Yes, I'm not blaming them, just underlining that there wasn't much hashrate left.

I see SuchPool is rising now (moved above the P2Pools), 5limi miners are probably switching over to it.

Trade My Bit got 8.94GH/s on us. Our usual mining hash is only 1.67GH/s.

Without 5limi the "usual" mining hashrate was probably below 1GH/s, as 5limi was about 50%.

This is consistent with the ratio of blocks claimed by tmb, which peaks at 90% (if tmb has 9 GH/s and the rest has less than 1 GH/s, then tmb logically gets 90% of the blocks)
http://chainz.cryptoid.info/lgc/extraction.dws?11.htm

Anyone could get in touch with 5limi admins?

DGW gets it's input from the blocks solved in the past N time and also (mostly) from the network-hashrate reported by the peers.

Hashrate can be an accurate measure at a pool (where miners report their hashrate), but the network hashrate is calculated from the time between blocks and their difficulty.

[Hippie Tech]

I have contacted Trade My Bit about the incorrect block reward and asking that LGC be deslited from their multipool. Any assitance you guys could offer would be amazing.

Ohhh the lolzz..  "go away you meany multi pool !"

You didn't seem to mind them before this...

Has Trade my Bit been checked for any of these ?

fake hash vulnerability  #66
https://github.com/slush0/stratum-mining-proxy/issues/66

Flooding with shares below the pool target #326
https://github.com/Crypto-Expert/stratum-mining/issues/326

Those only affect pool hashrate and not global hash rate.  You can submit as many fakeshares as you want towards the pool but that doesn't mean a block will get solved any quicker. What it means is that when the pool solves a block you get the majority of shares that come from the pool.

Do you have anything that will back up your claims ?

DGW is making its adjustments based on the pool's reported hashpower. Your statement is illogical..

No. DGW is making adjustments based on the amount of blocks solved and the total network hashrate.  It makes adjustments based on the coind's networkhashps.

Maybe this thread will explain it better than I can. https://bitcointalk.org/index.php?topic=513382.0

BOTH the pool AND the network are using the same daemon. This means both will be fooled by these exploits because the daemon is accepting the pool's hashrate which was calculated using the bloated sharerate figures.

fake hash vulnerability #1938
https://github.com/MPOS/php-mpos/issues/1938

With this method, all pools accepts fake hashrate and shares.

[Hippie Tech]

Btw, how do we know that the fake shares are not minting blocks ?

Many miners are listed as "anonymous".

Thx for the link, Logicoin.info. You've made it easier for me to prove my point(s).

On stablehash Groestl, someone take 99% of all rewards, sending thousands shares while other send 5 or 6.. Look at the invalide rate too..



I don't think this guy find any block too, but in anonymous, we can't verify..

There is some exploit out there..

[Logicoin.info]

I have contacted Trade My Bit about the incorrect block reward and asking that LGC be deslited from their multipool. Any assitance you guys could offer would be amazing.

Ohhh the lolzz..  "go away you meany multi pool !"

You didn't seem to mind them before this...

Has Trade my Bit been checked for any of these ?

fake hash vulnerability  #66
https://github.com/slush0/stratum-mining-proxy/issues/66

Flooding with shares below the pool target #326
https://github.com/Crypto-Expert/stratum-mining/issues/326

Those only affect pool hashrate and not global hash rate.  You can submit as many fakeshares as you want towards the pool but that doesn't mean a block will get solved any quicker. What it means is that when the pool solves a block you get the majority of shares that come from the pool.

Do you have anything that will back up your claims ?

DGW is making its adjustments based on the pool's reported hashpower. Your statement is illogical..

No. DGW is making adjustments based on the amount of blocks solved and the total network hashrate.  It makes adjustments based on the coind's networkhashps.

Maybe this thread will explain it better than I can. https://bitcointalk.org/index.php?topic=513382.0

BOTH the pool AND the network are using the same daemon. This means both will be fooled by these exploits because the daemon is accepting the pool's hashrate which was calculated using the bloated sharerate figures.

fake hash vulnerability #1938
https://github.com/MPOS/php-mpos/issues/1938

With this method, all pools accepts fake hashrate and shares.

Ah cmon dude. Have you even bothered to read the replies given too you? You said it yourself "POOLS" accept fakeshres not the network.

I'm close to being done wasting my effort replying to your fud. I've tried very hard to give you clear and concise explanations but it appears you know more about the stratum protcol and how the network functions than the rest of us.

[Logicoin.info]

Btw, how do we know that the fake shares are not minting blocks ?

Many miners are listed as "anonymous".

Thx for the link, Logicoin.info. You've made it easier for me to prove my point(s).

On stablehash Groestl, someone take 99% of all rewards, sending thousands shares while other send 5 or 6.. Look at the invalide rate too..



I don't think this guy find any block too, but in anonymous, we can't verify..

There is some exploit out there..

Please read the thread over. You are clearly misunderstanding the entire issue and seriously making yourself out to look silly at this point.

[Eastwind]

Trade My Bit got 8.94GH/s on us. Our usual mining hash is only 1.67GH/s.

Without 5limi the "usual" mining hashrate was probably below 1GH/s, as 5limi was about 50%.

This is consistent with the ratio of blocks claimed by tmb, which peaks at 90% (if tmb has 9 GH/s and the rest has less than 1 GH/s, then tmb logically gets 90% of the blocks)
http://chainz.cryptoid.info/lgc/extraction.dws?11.htm

Anyone could get in touch with 5limi admins?

The ratio of Trade My Bit to the total network rate is 84.2% if we use the 8.94 and 1.67 as reported on their website. They are getting 90% of the total blocks as they are just mining the low difficulty blocks from LGC. When we are mining high difficulty blocks, they are mining other coins.

Would a multipool have more profit than a nonswitching pool?

[Logicoin.info]

Trade My Bit got 8.94GH/s on us. Our usual mining hash is only 1.67GH/s.

Without 5limi the "usual" mining hashrate was probably below 1GH/s, as 5limi was about 50%.

This is consistent with the ratio of blocks claimed by tmb, which peaks at 90% (if tmb has 9 GH/s and the rest has less than 1 GH/s, then tmb logically gets 90% of the blocks)
http://chainz.cryptoid.info/lgc/extraction.dws?11.htm

Anyone could get in touch with 5limi admins?

The ratio of Trade My Bit to the total network rate is 84.2% if we use the 8.94 and 1.67 as reported on their website. They are getting 90% of the total blocks as they are just mining the low difficulty blocks from LGC. When we are mining high difficulty blocks, they are mining other coins.

Would a multipool have more profit than a nonswitching pool?

We seem to be having a much better experience now that they have adjusted their reward 

http://chainz.cryptoid.info/lgc/#

[myagui]

BOTH the pool AND the network are using the same daemon. This means both will be fooled by these exploits because the daemon is accepting the pool's hashrate which was calculated using the bloated sharerate figures.

fake hash vulnerability #1938
https://github.com/MPOS/php-mpos/issues/1938

With this method, all pools accepts fake hashrate and shares.

Wrong again.

The pools are processing shares of various difficulties. In contrast, the "network" only accepts full "blocks" at the proper network difficulty at any given time. There are no fake shares submitted to the network...

See, an abuser can submit all the fake shares he wants. The buggy pool will take them - BUT - unless the pool eventually finds a valid block, there is 0 reward. When the buggy pool does find a block, the block reward is perfectly valid, what is messed up (due to the abuse), is the share distribution of that block to the buggy pool miners. The network is completely unaffected. The victims, are the legitimate miners on the buggy pool, which are not getting their share of blocks found by the pool.

Please... Stop posting for a while, go take a read, a break, a smoke, then have another think about your claims. You have received well beyond any reasonable explanations to your concerns, and you do not appear to be taking a breath's moment to think about what is being explained.

Cheers,
~ Myagui

[Hippie Tech]

BOTH the pool AND the network are using the same daemon. This means both will be fooled by these exploits because the daemon is accepting the pool's hashrate which was calculated using the bloated sharerate figures.

fake hash vulnerability #1938
https://github.com/MPOS/php-mpos/issues/1938

With this method, all pools accepts fake hashrate and shares.

Wrong again.

The pools are processing shares of various difficulties. In contrast, the "network" only accepts full "blocks" at the proper network difficulty at any given time. There are no fake shares submitted to the network...

See, an abuser can submit all the fake shares he wants. The buggy pool will take them - BUT - unless the pool eventually finds a valid block, there is 0 reward. When the buggy pool does find a block, the block reward is perfectly valid, what is messed up (due to the abuse), is the share distribution of that block to the buggy pool miners. The network is completely unaffected. The victims, are the legitimate miners on the buggy pool, which are not getting their share of blocks found by the pool.

Please... Stop posting for a while, go take a read, a break, a smoke, then have another think about your claims. You have received well beyond any reasonable explanations to your concerns, and you do not appear to be taking a breath's moment to think about what is being explained.

Cheers,
~ Myagui

https://bitcointalk.org/index.php?topic=252127.msg4492641#msg4492641

[myagui]

https://bitcointalk.org/index.php?topic=252127.msg4492641#msg4492641

The thread you're pointing too, shows a an example of a pool being abused by fake shares, which is, again, completely irrelevant with regards to network security and block rewards for just everyone (except those on the abused pool). The coin in question eventually forked for reasons again completely unrelated to your claims here. This adds absolutely nothing to what has already been expressed.

You continue to not take the time to read the explanations that you're offered, and you have not added any question or argument of value.
Sorry, but I'm done here. You are not being ignored, but I will certainly not feed this discussion any further!
Cheers,
~ Myagui

[esotericizm]

BOTH the pool AND the network are using the same daemon. This means both will be fooled by these exploits because the daemon is accepting the pool's hashrate which was calculated using the bloated sharerate figures.

fake hash vulnerability #1938
https://github.com/MPOS/php-mpos/issues/1938

With this method, all pools accepts fake hashrate and shares.

Wrong again.

The pools are processing shares of various difficulties. In contrast, the "network" only accepts full "blocks" at the proper network difficulty at any given time. There are no fake shares submitted to the network...

See, an abuser can submit all the fake shares he wants. The buggy pool will take them - BUT - unless the pool eventually finds a valid block, there is 0 reward. When the buggy pool does find a block, the block reward is perfectly valid, what is messed up (due to the abuse), is the share distribution of that block to the buggy pool miners. The network is completely unaffected. The victims, are the legitimate miners on the buggy pool, which are not getting their share of blocks found by the pool.

Please... Stop posting for a while, go take a read, a break, a smoke, then have another think about your claims. You have received well beyond any reasonable explanations to your concerns, and you do not appear to be taking a breath's moment to think about what is being explained.

Cheers,
~ Myagui

https://bitcointalk.org/index.php?topic=252127.msg4492641#msg4492641

lol u are a joke. its been explained by atleast 3 people that you are flatout wrong yet you continue to spread your bullshit. I looked through ur history and it seems all you do is spread misinformation because you pretend to know more than you clearly actually do.

[Eastwind]

I noticed that when the difficulty is low, around 15-20, the blocks are usually solved by one pool in quick succession, is it because the new block has not been broadcasted fast enough to whole network, the pool solved the last block get the new block earlier than other miners?

Is this particular to the fast block coins?


Blockheight   Age   Transactions   Value Out   Difficulty   Extracted by
48407   2 minutes   1   25.0 LGC   39.21   SuchPool.pw
48406   2 minutes   1   25.0 LGC   30.11   Trade My Bit
48405   2 minutes   1   25.0 LGC   27.89   Trade My Bit
48404   3 minutes   1   25.0 LGC   23.54   Trade My Bit
48403   4 minutes   1   25.0 LGC   21.41   Trade My Bit
48402   4 minutes   1   25.0 LGC   20.64   Trade My Bit
48401   4 minutes   1   25.0 LGC   20.02   Trade My Bit
48400   4 minutes   1   25.0 LGC   19.76   Trade My Bit
48399   4 minutes   2   79.9953379 LGC   15.70   Trade My Bit
48398   4 minutes   1   25.0 LGC   15.22   Trade My Bit
48397   4 minutes   1   25.0 LGC   15.76   Trade My Bit
48396   4 minutes   1   25.0 LGC   16.31   Trade My Bit
48395   4 minutes   1   25.0 LGC   16.62   Trade My Bit
48394   4 minutes   1   25.0 LGC   15.85   Trade My Bit
48393   4 minutes   1   25.0 LGC   16.66   Trade My Bit
48392   5 minutes   1   25.0 LGC   17.62   P2Pool
48391   5 minutes   1   25.0 LGC   20.23   Trade My Bit
48390   8 minutes   2   27.22119527 LGC   21.98   SuchPool.pw
48389   9 minutes   2   50.0 LGC   26.01   SuchPool.pw
48388   13 minutes   1   25.0 LGC   28.21   SuchPool.pw
48387   15 minutes   1   25.0 LGC   28.97   SuchPool.pw
48386   16 minutes   2   50.0 LGC   30.54   SuchPool.pw
48385   17 minutes   1   25.0 LGC   30.29   SuchPool.pw
48384   18 minutes   1   25.0 LGC   37.16   P2Pool
48383   25 minutes   1   25.0 LGC   40.05   SuchPool.pw
48382   27 minutes   1   25.0 LGC   38.40   SuchPool.pw
48381   28 minutes   1   25.0 LGC   37.03   SuchPool.pw
48380   29 minutes   1   25.0 LGC   37.56   SuchPool.pw
48379   30 minutes   1   25.0 LGC   45.89   SuchPool.pw
48378   34 minutes   1   25.0 LGC   45.43   SuchPool.pw
48377   35 minutes   1   25.0 LGC   49.10   SuchPool.pw
48376   36 minutes   1   25.0 LGC   46.81   SuchPool.pw
48375   36 minutes   1   25.0 LGC   43.97   SuchPool.pw
48374   37 minutes   1   25.0 LGC   39.93   SuchPool.pw
48373   37 minutes   1   25.0 LGC   35.41   P2Pool
48372   37 minutes   1   25.0 LGC   33.22   Trade My Bit
48371   37 minutes   1   25.0 LGC   21.55   Trade My Bit
48370   38 minutes   1   25.0 LGC   19.97   Trade My Bit
48369   38 minutes   2   47.29430806 LGC   18.42   Trade My Bit
48368   38 minutes   1   25.0 LGC   17.96   Trade My Bit
48367   38 minutes   1   25.0 LGC   17.17   Trade My Bit
48366   38 minutes   1   25.0 LGC   16.70   Trade My Bit
48365   38 minutes   1   25.0 LGC   15.56   Trade My Bit
48364   38 minutes   1   25.0 LGC   15.38   Trade My Bit
48363   38 minutes   1   25.0 LGC   14.80   Trade My Bit
48362   39 minutes   1   25.0 LGC   14.01   Trade My Bit
48361   38 minutes   1   25.0 LGC   11.56   SuchPool.pw
48360   39 minutes   1   25.0 LGC   11.51   Trade My Bit
48359   39 minutes   1   25.0 LGC   11.60   Trade My Bit
48358   39 minutes   1   25.0 LGC   11.25   Trade My Bit
48357   40 minutes   1   25.0 LGC   10.77   Trade My Bit

[esotericizm]

I noticed at when the difficulty is low, around 15-20, the blocks are usually solved by one pool in quick succession, is it because the new block has not been broadcasted fast enough to whole network, the pool solved the last block get the new block earlier than other miners?

Is this particular to the fast block coins?


Blockheight   Age   Transactions   Value Out   Difficulty   Extracted by
48407   2 minutes   1   25.0 LGC   39.21   SuchPool.pw
48406   2 minutes   1   25.0 LGC   30.11   Trade My Bit
48405   2 minutes   1   25.0 LGC   27.89   Trade My Bit
48404   3 minutes   1   25.0 LGC   23.54   Trade My Bit
48403   4 minutes   1   25.0 LGC   21.41   Trade My Bit
48402   4 minutes   1   25.0 LGC   20.64   Trade My Bit
48401   4 minutes   1   25.0 LGC   20.02   Trade My Bit
48400   4 minutes   1   25.0 LGC   19.76   Trade My Bit
48399   4 minutes   2   79.9953379 LGC   15.70   Trade My Bit
48398   4 minutes   1   25.0 LGC   15.22   Trade My Bit
48397   4 minutes   1   25.0 LGC   15.76   Trade My Bit
48396   4 minutes   1   25.0 LGC   16.31   Trade My Bit
48395   4 minutes   1   25.0 LGC   16.62   Trade My Bit
48394   4 minutes   1   25.0 LGC   15.85   Trade My Bit
48393   4 minutes   1   25.0 LGC   16.66   Trade My Bit
48392   5 minutes   1   25.0 LGC   17.62   P2Pool
48391   5 minutes   1   25.0 LGC   20.23   Trade My Bit
48390   8 minutes   2   27.22119527 LGC   21.98   SuchPool.pw
48389   9 minutes   2   50.0 LGC   26.01   SuchPool.pw
48388   13 minutes   1   25.0 LGC   28.21   SuchPool.pw
48387   15 minutes   1   25.0 LGC   28.97   SuchPool.pw
48386   16 minutes   2   50.0 LGC   30.54   SuchPool.pw
48385   17 minutes   1   25.0 LGC   30.29   SuchPool.pw
48384   18 minutes   1   25.0 LGC   37.16   P2Pool
48383   25 minutes   1   25.0 LGC   40.05   SuchPool.pw
48382   27 minutes   1   25.0 LGC   38.40   SuchPool.pw
48381   28 minutes   1   25.0 LGC   37.03   SuchPool.pw
48380   29 minutes   1   25.0 LGC   37.56   SuchPool.pw
48379   30 minutes   1   25.0 LGC   45.89   SuchPool.pw
48378   34 minutes   1   25.0 LGC   45.43   SuchPool.pw
48377   35 minutes   1   25.0 LGC   49.10   SuchPool.pw
48376   36 minutes   1   25.0 LGC   46.81   SuchPool.pw
48375   36 minutes   1   25.0 LGC   43.97   SuchPool.pw
48374   37 minutes   1   25.0 LGC   39.93   SuchPool.pw
48373   37 minutes   1   25.0 LGC   35.41   P2Pool
48372   37 minutes   1   25.0 LGC   33.22   Trade My Bit
48371   37 minutes   1   25.0 LGC   21.55   Trade My Bit
48370   38 minutes   1   25.0 LGC   19.97   Trade My Bit
48369   38 minutes   2   47.29430806 LGC   18.42   Trade My Bit
48368   38 minutes   1   25.0 LGC   17.96   Trade My Bit
48367   38 minutes   1   25.0 LGC   17.17   Trade My Bit
48366   38 minutes   1   25.0 LGC   16.70   Trade My Bit
48365   38 minutes   1   25.0 LGC   15.56   Trade My Bit
48364   38 minutes   1   25.0 LGC   15.38   Trade My Bit
48363   38 minutes   1   25.0 LGC   14.80   Trade My Bit
48362   39 minutes   1   25.0 LGC   14.01   Trade My Bit
48361   38 minutes   1   25.0 LGC   11.56   SuchPool.pw
48360   39 minutes   1   25.0 LGC   11.51   Trade My Bit
48359   39 minutes   1   25.0 LGC   11.60   Trade My Bit
48358   39 minutes   1   25.0 LGC   11.25   Trade My Bit
48357   40 minutes   1   25.0 LGC   10.77   Trade My Bit

it's because of the hashrate of trademybit imo we should be contacting them and asking them to stop mining lgc as they seem to be doing damage to the confidence in the coin. i mined kittehcoin for a while and they had an issue similar to this but instead of the hard blocks being solved in under 30 miuntes it woudl sometimes take almost 24 hours to find a block.

[sumgye]

I noticed at when the difficulty is low, around 15-20, the blocks are usually solved by one pool in quick succession, is it because the new block has not been broadcasted fast enough to whole network, the pool solved the last block get the new block earlier than other miners?

Is this particular to the fast block coins?


Blockheight   Age   Transactions   Value Out   Difficulty   Extracted by
48407   2 minutes   1   25.0 LGC   39.21   SuchPool.pw
48406   2 minutes   1   25.0 LGC   30.11   Trade My Bit
48405   2 minutes   1   25.0 LGC   27.89   Trade My Bit
48404   3 minutes   1   25.0 LGC   23.54   Trade My Bit
48403   4 minutes   1   25.0 LGC   21.41   Trade My Bit
48402   4 minutes   1   25.0 LGC   20.64   Trade My Bit
48401   4 minutes   1   25.0 LGC   20.02   Trade My Bit
48400   4 minutes   1   25.0 LGC   19.76   Trade My Bit
48399   4 minutes   2   79.9953379 LGC   15.70   Trade My Bit
48398   4 minutes   1   25.0 LGC   15.22   Trade My Bit
48397   4 minutes   1   25.0 LGC   15.76   Trade My Bit
48396   4 minutes   1   25.0 LGC   16.31   Trade My Bit
48395   4 minutes   1   25.0 LGC   16.62   Trade My Bit
48394   4 minutes   1   25.0 LGC   15.85   Trade My Bit
48393   4 minutes   1   25.0 LGC   16.66   Trade My Bit
48392   5 minutes   1   25.0 LGC   17.62   P2Pool
48391   5 minutes   1   25.0 LGC   20.23   Trade My Bit
48390   8 minutes   2   27.22119527 LGC   21.98   SuchPool.pw
48389   9 minutes   2   50.0 LGC   26.01   SuchPool.pw
48388   13 minutes   1   25.0 LGC   28.21   SuchPool.pw
48387   15 minutes   1   25.0 LGC   28.97   SuchPool.pw
48386   16 minutes   2   50.0 LGC   30.54   SuchPool.pw
48385   17 minutes   1   25.0 LGC   30.29   SuchPool.pw
48384   18 minutes   1   25.0 LGC   37.16   P2Pool
48383   25 minutes   1   25.0 LGC   40.05   SuchPool.pw
48382   27 minutes   1   25.0 LGC   38.40   SuchPool.pw
48381   28 minutes   1   25.0 LGC   37.03   SuchPool.pw
48380   29 minutes   1   25.0 LGC   37.56   SuchPool.pw
48379   30 minutes   1   25.0 LGC   45.89   SuchPool.pw
48378   34 minutes   1   25.0 LGC   45.43   SuchPool.pw
48377   35 minutes   1   25.0 LGC   49.10   SuchPool.pw
48376   36 minutes   1   25.0 LGC   46.81   SuchPool.pw
48375   36 minutes   1   25.0 LGC   43.97   SuchPool.pw
48374   37 minutes   1   25.0 LGC   39.93   SuchPool.pw
48373   37 minutes   1   25.0 LGC   35.41   P2Pool
48372   37 minutes   1   25.0 LGC   33.22   Trade My Bit
48371   37 minutes   1   25.0 LGC   21.55   Trade My Bit
48370   38 minutes   1   25.0 LGC   19.97   Trade My Bit
48369   38 minutes   2   47.29430806 LGC   18.42   Trade My Bit
48368   38 minutes   1   25.0 LGC   17.96   Trade My Bit
48367   38 minutes   1   25.0 LGC   17.17   Trade My Bit
48366   38 minutes   1   25.0 LGC   16.70   Trade My Bit
48365   38 minutes   1   25.0 LGC   15.56   Trade My Bit
48364   38 minutes   1   25.0 LGC   15.38   Trade My Bit
48363   38 minutes   1   25.0 LGC   14.80   Trade My Bit
48362   39 minutes   1   25.0 LGC   14.01   Trade My Bit
48361   38 minutes   1   25.0 LGC   11.56   SuchPool.pw
48360   39 minutes   1   25.0 LGC   11.51   Trade My Bit
48359   39 minutes   1   25.0 LGC   11.60   Trade My Bit
48358   39 minutes   1   25.0 LGC   11.25   Trade My Bit
48357   40 minutes   1   25.0 LGC   10.77   Trade My Bit

it's because of the hashrate of trademybit imo we should be contacting them and asking them to stop mining lgc as they seem to be doing damage to the confidence in the coin. i mined kittehcoin for a while and they had an issue similar to this but instead of the hard blocks being solved in under 30 miuntes it woudl sometimes take almost 24 hours to find a block.

As for contacting them, dev already did, and they've already adjusted their systems. I doubt they'll stop mining LGC - but they weren't aware that the block reward had halved from 50 to 25.

Proof: http://chainz.cryptoid.info/lgc/extraction.dws?11.htm

[sumgye]

https://bitcointalk.org/index.php?topic=252127.msg4492641#msg4492641

The thread you're pointing too, shows a an example of a pool being abused by fake shares, which is, again, completely irrelevant with regards to network security and block rewards for just everyone (except those on the abused pool). The coin in question eventually forked for reasons again completely unrelated to your claims here. This adds absolutely nothing to what has already been expressed.

You continue to not take the time to read the explanations that you're offered, and you have not added any question or argument of value.
Sorry, but I'm done here. You are not being ignored, but I will certainly not feed this discussion any further!
Cheers,
~ Myagui

That link just reminds me of what talesfromthescrypt looked like after everyone abandoned it. Just a few lingering cpu miners solving all the blocks while others faked hashrates and scooped up whatever rewards they happened to find. It was kind of sad really.

[esotericizm]

I noticed at when the difficulty is low, around 15-20, the blocks are usually solved by one pool in quick succession, is it because the new block has not been broadcasted fast enough to whole network, the pool solved the last block get the new block earlier than other miners?

Is this particular to the fast block coins?


Blockheight   Age   Transactions   Value Out   Difficulty   Extracted by
48407   2 minutes   1   25.0 LGC   39.21   SuchPool.pw
48406   2 minutes   1   25.0 LGC   30.11   Trade My Bit
48405   2 minutes   1   25.0 LGC   27.89   Trade My Bit
48404   3 minutes   1   25.0 LGC   23.54   Trade My Bit
48403   4 minutes   1   25.0 LGC   21.41   Trade My Bit
48402   4 minutes   1   25.0 LGC   20.64   Trade My Bit
48401   4 minutes   1   25.0 LGC   20.02   Trade My Bit
48400   4 minutes   1   25.0 LGC   19.76   Trade My Bit
48399   4 minutes   2   79.9953379 LGC   15.70   Trade My Bit
48398   4 minutes   1   25.0 LGC   15.22   Trade My Bit
48397   4 minutes   1   25.0 LGC   15.76   Trade My Bit
48396   4 minutes   1   25.0 LGC   16.31   Trade My Bit
48395   4 minutes   1   25.0 LGC   16.62   Trade My Bit
48394   4 minutes   1   25.0 LGC   15.85   Trade My Bit
48393   4 minutes   1   25.0 LGC   16.66   Trade My Bit
48392   5 minutes   1   25.0 LGC   17.62   P2Pool
48391   5 minutes   1   25.0 LGC   20.23   Trade My Bit
48390   8 minutes   2   27.22119527 LGC   21.98   SuchPool.pw
48389   9 minutes   2   50.0 LGC   26.01   SuchPool.pw
48388   13 minutes   1   25.0 LGC   28.21   SuchPool.pw
48387   15 minutes   1   25.0 LGC   28.97   SuchPool.pw
48386   16 minutes   2   50.0 LGC   30.54   SuchPool.pw
48385   17 minutes   1   25.0 LGC   30.29   SuchPool.pw
48384   18 minutes   1   25.0 LGC   37.16   P2Pool
48383   25 minutes   1   25.0 LGC   40.05   SuchPool.pw
48382   27 minutes   1   25.0 LGC   38.40   SuchPool.pw
48381   28 minutes   1   25.0 LGC   37.03   SuchPool.pw
48380   29 minutes   1   25.0 LGC   37.56   SuchPool.pw
48379   30 minutes   1   25.0 LGC   45.89   SuchPool.pw
48378   34 minutes   1   25.0 LGC   45.43   SuchPool.pw
48377   35 minutes   1   25.0 LGC   49.10   SuchPool.pw
48376   36 minutes   1   25.0 LGC   46.81   SuchPool.pw
48375   36 minutes   1   25.0 LGC   43.97   SuchPool.pw
48374   37 minutes   1   25.0 LGC   39.93   SuchPool.pw
48373   37 minutes   1   25.0 LGC   35.41   P2Pool
48372   37 minutes   1   25.0 LGC   33.22   Trade My Bit
48371   37 minutes   1   25.0 LGC   21.55   Trade My Bit
48370   38 minutes   1   25.0 LGC   19.97   Trade My Bit
48369   38 minutes   2   47.29430806 LGC   18.42   Trade My Bit
48368   38 minutes   1   25.0 LGC   17.96   Trade My Bit
48367   38 minutes   1   25.0 LGC   17.17   Trade My Bit
48366   38 minutes   1   25.0 LGC   16.70   Trade My Bit
48365   38 minutes   1   25.0 LGC   15.56   Trade My Bit
48364   38 minutes   1   25.0 LGC   15.38   Trade My Bit
48363   38 minutes   1   25.0 LGC   14.80   Trade My Bit
48362   39 minutes   1   25.0 LGC   14.01   Trade My Bit
48361   38 minutes   1   25.0 LGC   11.56   SuchPool.pw
48360   39 minutes   1   25.0 LGC   11.51   Trade My Bit
48359   39 minutes   1   25.0 LGC   11.60   Trade My Bit
48358   39 minutes   1   25.0 LGC   11.25   Trade My Bit
48357   40 minutes   1   25.0 LGC   10.77   Trade My Bit

it's because of the hashrate of trademybit imo we should be contacting them and asking them to stop mining lgc as they seem to be doing damage to the confidence in the coin. i mined kittehcoin for a while and they had an issue similar to this but instead of the hard blocks being solved in under 30 miuntes it woudl sometimes take almost 24 hours to find a block.

As for contacting them, dev already did, and they've already adjusted their systems. I doubt they'll stop mining LGC - but they weren't aware that the block reward had halved from 50 to 25.

Proof: http://chainz.cryptoid.info/lgc/extraction.dws?11.htm

from what the dev quoted it sounded like they would stop mining it if it was hurtting the network

[sumgye]

from what the dev quoted it sounded like they would stop mining it if it was hurtting the network

You may well be right. The important thing is that they've stopped mining us for now.

[esotericizm]

glad im not the only one who thinks the dev is being honest