Topic: NA - page 456. (Read 893616 times)

Absolutely amazing how people are working together to help this fucking fantastic coin out. Respect to everyone here!!

Agreed.

Also, thanks for clarifying the changes that were made.  +1

-Fuse

Thanks for stepping up and making the change, it helps us all in the long run!

Just to correct things. We put less than 8th of our pool hashrate to NLG.

CleverMining always had an algorithm to limit amount of hashrate pointed at any coin depending on coin difficulty, to don't pump the coin difficulty too much. It works great with DigiShield coins and works well with most KGW coins. I'm not sure why NLG is different here. Maybe KGW doesn't work well with longer times between blocks (most coins these days have 60-second blocks)?

What I did is limited amount of hashpower pointed to NLG to 1/8th of what we point at any other coin with the same difficulty. This isn't related to our total pool hashrate, it's related only to coin difficulty and expected time to find a block. We adjust our maximum allowed hashrate to coin difficulty to don't find blocks too fast. NLG has 8x handicap here from now on. This means we allow 8x less hashpower pointed to NLG than to other coins at the same difficulty.

NLG difficulty already dropped after this change and remains steady. Times between blocks started being more regular. I hope this will help regular pools to also find good blocks and will prevent high difficulty jumps and long times between blocks.

We don't want to withdraw away completely from NLG as we have responsibilities to our users. We promised them to maximize their profits and to mine coins which are profitable. But we also don't want to harm coins and this is why I wanted to find some middle ground between CleverMining users interests and Guldencoin community interests. I hope I found the right balance. I will keep this 8x handicap until Sep 26th when I heard you plan to launch the new difficulty readjustment algorithm.

Thanks so much Fuse for contacting him to get this organised. Things appear to be a lot more stable currently but will see how it goes overnight.

Terk has gotten back to me.  He had originally limited the hashrate that was mining on NLG to a 4th of the total hashrate of the pool.  He has decreased that to an 8th of the total hashrate.  He asked that we monitor the chain and let him know how it looks.

While he hasn't agreed to stop mining NLG, he did agree to work with us to get things running smoothly.

-Fuse

In turmoil is greatest chance to get bargains as people worry. This is when good buys come.

Some "angsthaas" was panicselling just after the blocks were found. Thanks for the NLG 

Some good news is the next blocks have come through. We will be monitoring if the same mass spike in hash occurs again.

I have msg'd Terk, the OP for Clevermining, and kindly asked that he remove NLG from the pool.  I'll see what he says.

However, a difficulty algorithm change needs to happen soon.  KNC starts shipping batch 1 of the titans this week.  This is an event as big, if not bigger, as when scrypt coins went from GPUs to ASICs.  Expect some crazy things to happen in crypto in the next few weeks.

-Fuse

I have to agree with the above, when we rollout digishield it needs to be done right.

I have just used bitsms.eu and the transaction was processed straight away, so in terms of merchant usage there is no harm done which would be a concern. Like I have said previously implementing digishield is our top priority but it must be done with thorough testing.

Agree. Blocking goes against the whole core belief in decentralization. Patience is what is needed here, not knee jerk reactions. Let the team get Digishield working and the network will settle down and even out. No real harm will be done, miners understand what is going on and users will see is as a "speed bump" and forget about it when things steady up....

Blocking ip's won't do much good, a proxy is set up in a flash. Instead it might be an idea to create a whitelist embedded in the code, but that generates (IMHO) a far more serious problem, it's called control and centralization. Isn't that also one of the primary things we want to avoid with crypto?

For now I don't worry to much. I've seen these problems on many other occasions and yes, they are a pest, but it can be overcome. My trust lies for a 100% with the DEV team, they for sure will sort it out.

Remember, this is a long term initiative, lets take these "bumps" as a sort of exercise 

Sun still shines here 

This is current issue we discussing with multipools, the sync will only happen in 15 - 30 hours from now.

DigiShield has been working well to correct this problem and the people behind it are solid.

EDIT: I meant to say "for other coins". I realize NLG is not live with it yet.

Same here, restarted twice, no moving past that hump....

From peoples guesses we have 15-30 hours to make decisions before next block is resolved.

I agree the multipools are not in the best interests of Guldencoin. These pools have miners whose solely goal is trading the coin, if needed with big pump and dumps.
They do not give a sh.. about the future of Guldencoin. They rip it, take their profits and after it breaks down they move on to the next coin.

The goal of Guldencoin is to be(come) an accepted currency used in real-life payments. These multi-pools are a big threat to that goal.
You should not be afraid to block them. If they want to bring on a fight, the community is strong enough to win that fight. If you block them, they can only dump coins once, instead of day by day.

I think it is not Cleverming multipool. I test the mining there right now and a lot of new blocks are found.

So they are not on NLG atm.

What about only letting in the IPs from our current pools in the OP list instead of trying to block IPs until they update the coin with the new changes? Do pools only use 1 IP address?