[ANN] [SPOT] | SUCCESSFUL FORK COMPLETE - On CoinPayments.net/Cryptsy/Coins-e

[draceus]

FUCK IT JUST HAPPENED AGAIN  diff 10 NO BLOCKS after another 2 hours waisted

this time 27 blocks gone 77568-77595

WHAT THE FUCK MAN

Can you post like a normal person?
Writing in all caps and swearing wont get you anywhere

[Luror]

10 SPOTS to anyone who posts an address before we get to page 68 - Only do it once or I'll skip both of your posts

MK8zGq7AQFyN7gPeN7Fd3PHVzRzFgMt6Q7

Thanks!

[iGotSpots]

FUCK IT JUST HAPPENED AGAIN  diff 10 NO BLOCKS after another 2 hours waisted

this time 27 blocks gone 77568-77595

WHAT THE FUCK MAN

Its been like this for 6 months. You're mad at a bunch of code right now

Regardless, yes, the fork will help slow down the swing

[serpicodk]

MTAN1oETESYJ2dhM1tJkXi9Mb3wW1m9UCw

Thank you

[nuttynoah]

MCiGaM5JnivkKuSnx9enHVdJmMg7WF25mX

Nice one!!

[sadcoin]

MKgFqv71rtYw3hvggKxibS3ZR1Jbzr419N

Thanks!

[kslavik]

The multipools are really bad. They are bad idea for everyone else but the pool owner, because most of the time the miners don't get what is advertised.

But, the result is that someone has at their disposal massive hashing power and they can point it anywhere they like, anytime.

Coins that have long difficulty update periods and permit large changes in difficulty are especially vulnerable.

It is not that Multipools are bad, but the coins have poor designs to allow this kind of difficulty jumps. The multipools are like wolves which make the crypto-currencies stronger as a whole by weeding out badly designed coins.

It is very easy to make a coin to withstand such multi-pool attacks by making an adjustment every block towards the desired difficulty based on the past 10-20 blocks, but this coin chose a different strategy.

This coin was designed against such multi-pools attacks and look how well it worked and it will fail again after the update too. Those are not multipools mining this coins on low difficulty periods, but individual solo-mines with software to detect the low difficulty periods and auto-switch their farms just few seconds after the re-target.

[ckoeber]

The multipools are really bad. They are bad idea for everyone else but the pool owner, because most of the time the miners don't get what is advertised.

But, the result is that someone has at their disposal massive hashing power and they can point it anywhere they like, anytime.

Coins that have long difficulty update periods and permit large changes in difficulty are especially vulnerable.

It is not that Multipools are bad, but the coins have poor designs to allow this kind of difficulty jumps. The multipools are like wolves which make the crypto-currencies stronger as a whole by weeding out badly designed coins.
 

It is very easy to make a coin to withstand such multi-pool attacks by making an adjustment every block towards the desired difficulty based on the past 10-20 blocks, but this coin chose a different strategy.

This coin was designed against such multi-pools attacks and look how well it worked and it will fail again after the update too. Those are not multipools mining this coins on low difficulty periods, but individual solo-mines with software to detect low difficulty periods and auto-switch their farms just in few seconds after the re-target.

Interesting; I believe, if I am not mistaken, your bolded piece is what will happen after the fork.

It seems like it will be a bit before we hit the fork but as long as the coin is solid after I am down...

[gal40n0k]

MW9g2mGTpHxb8qZ4DiBF2D871V9Cx1peiA

Thanks a lot!

[iGotSpots]

The multipools are really bad. They are bad idea for everyone else but the pool owner, because most of the time the miners don't get what is advertised.

But, the result is that someone has at their disposal massive hashing power and they can point it anywhere they like, anytime.

Coins that have long difficulty update periods and permit large changes in difficulty are especially vulnerable.

It is not that Multipools are bad, but the coins have poor designs to allow this kind of difficulty jumps. The multipools are like wolves which make the crypto-currencies stronger as a whole by weeding out badly designed coins.
 

It is very easy to make a coin to withstand such multi-pool attacks by making an adjustment every block towards the desired difficulty based on the past 10-20 blocks, but this coin chose a different strategy.

This coin was designed against such multi-pools attacks and look how well it worked and it will fail again after the update too. Those are not multipools mining this coins on low difficulty periods, but individual solo-mines with software to detect low difficulty periods and auto-switch their farms just in few seconds after the re-target.

Interesting; I believe, if I am not mistaken, your bolded piece is what will happen after the fork.

It seems like it will be a bit before we hit the fork but as long as the coin is solid after I am down...

Currently it adjusts every based on the last 21 so his suggestion has been on it since August. We are adjusting the % the difficulty can shift and reducing it significantly with the fork

[STT]

Thankyou
M9pPrz7vqEhXQvASKBP1k2YAGSn4fXeo4x

[NUFCrichard]

Something I don't understand.  Currently the problem is that the difficulty adjusts too much.  If that is the case, why are the blocks going so slowly at the moment?
We should be rattling through 1200+ blocks a day, whereas it is nowhere near that at the moment.  The difficulty should surely adjust to account for that, especially before the hardfork.

[NUFCrichard]

Just quickly had a look to add some numbers to the above post.  It took >15 hours between 77722 and 77821.
About 545 seconds a block.  That means it will be about 20 days until the hardfork kicks in, instead of the expected 2.5 days (actually last weekend was the original expectation).

I get that you are content that it takes longer until the fork, but why are blocks taking 475 seconds longer than expected?

[kslavik]

Just quickly had a look to add some numbers to the above post.  It took >15 hours between 77722 and 77821.
About 545 seconds a block.  That means it will be about 20 days until the hardfork kicks in, instead of the expected 2.5 days (actually last weekend was the original expectation).

I get that you are content that it takes longer until the fork, but why are blocks taking 475 seconds longer than expected?

Difficulty can only adjust when a block is found. If nobody mines this coins because the difficulty is too high, no blocks will be found for a long while. Once a block is found (after a long period of time) the difficulty jumps to a very low value and the network find low difficulty blocks very fast (much faster than a target of 70 seconds per block), so that the next difficulty is set to a very high level again to account for the increased network speed, which is NOT there because it goes away as soon as miners see that this coin is no longer profitable to mine.

The most valuable part of any crypto-coin is predictable confirmation period or stable generation of blocks. Until those difficulty jumps are fixed - this coin has no future. Don't get your hopes up for the upcoming fix at block 81k. Even though the developer never posted the exact changes to the algorithm of difficulty calculations, I very much doubt that he did it right (he is not a developer/programmer/engineer but a carpet cleaner) and the problem will continue to exist even after block 81k.
 

[TmottaDing]

Just quickly had a look to add some numbers to the above post.  It took >15 hours between 77722 and 77821.
About 545 seconds a block.  That means it will be about 20 days until the hardfork kicks in, instead of the expected 2.5 days (actually last weekend was the original expectation).

I get that you are content that it takes longer until the fork, but why are blocks taking 475 seconds longer than expected?

The most valuable part of any coins is predictable confirmation period or stable generation of blocks. Until those difficulty jumps are fixed - this coin has no future. Don't get your hopes up for the upcoming fix at block 81k. Even though the developer never posted the exact changes to the algorithm of difficulty calculations, I very much doubt that he did it right (he is not a developer/programmer/engineer but a carpet cleaner) and the problem will continue to exist even after block 81k.
 

As I tried to warn everyone Spots is a Bullshit artist. All I asked for was the confirmation txid that shows he paid me like he said. That was 2 months ago still no txid, just more spew of Bullshit.

[iGotSpots]

Just quickly had a look to add some numbers to the above post.  It took >15 hours between 77722 and 77821.
About 545 seconds a block.  That means it will be about 20 days until the hardfork kicks in, instead of the expected 2.5 days (actually last weekend was the original expectation).

I get that you are content that it takes longer until the fork, but why are blocks taking 475 seconds longer than expected?

The most valuable part of any coins is predictable confirmation period or stable generation of blocks. Until those difficulty jumps are fixed - this coin has no future. Don't get your hopes up for the upcoming fix at block 81k. Even though the developer never posted the exact changes to the algorithm of difficulty calculations, I very much doubt that he did it right (he is not a developer/programmer/engineer but a carpet cleaner) and the problem will continue to exist even after block 81k.
 

As I tried to warn everyone Spots is a Bullshit artist. All I asked for was the confirmation txid that shows he paid me like he said. That was 2 months ago still no txid, just more spew of Bullshit.

You got paid back, posted you were paid back, and still act like a bitch. Grow up son

As far as blocks going slow...feel free to keep blaming me all you guys want. Its been the same way for 6 months and you guys are only complaining now because better days are ahead

I should have just set new block reward to 0 so you guys had something real to be mad about

[r3wt]

You got paid back, posted you were paid back, and still act like a bitch. Grow up son

Hypocrite much?

[iGotSpots]

You got paid back, posted you were paid back, and still act like a bitch. Grow up son

Hypocrite much?

Not really. I left you alone when you paid me back, like adults do

[TmottaDing]

Like I said for past two months post txid. And don't worry with your name calling, either txid or do like you did before and ignore me.

[r3wt]

You got paid back, posted you were paid back, and still act like a bitch. Grow up son

Hypocrite much?

Not really. I left you alone when you paid me back, like adults do

Yeah, because adults leave negative feedback claiming someone "scammed over 50 btc from so many users", when really it was .4 btc and a broken contract from one user, that user was you.