[Dev] Hard fork to change retarget, averages and block time
-
Re: DigiShield implementation
I can also see another problem we tried to avoid in using the nActualTimespan. The solution without reference to measuring actual time has fewer drawbacks.
-
Just a couple of points.
We will probably need a name. That has not been our priority but something like “Advanced Difficulty Averaging” ADA
or ABC - Advanced block calculation. or FAB Feathercoin Advanced Block (Calc)
FMP
-
FOMP - Stands for, Please Go Away Multipools.
Lol
-
FOMP - Stands for, Please Go Away Multipools.
Ah, didn’t see someone beat me to it!
-
We def need to get this change going soon… This is killing loyal miners with the hash rate so low, and it will take over 9 hours to re-target???
-
Yes. Last week I have stopped my POOL, mining FTC no profit . Purchase cost than mining. I’m minging some of the new currency until the FTC Reply.
-
If we drop the difficulty change then it increases the ability of multipools to manipulate us. The flip side is that hostile entities can push our difficulty up quicker, but there is still the averaging that stops it from being too rapid.
Wrapper is happy with the 9% difficulty as it is and our difficulty change is still less than Dogecoin are planning. They now have a lot of resources and developers as they launched into a much bigger crypt community. We should give them some faith… Actually their new difficulty should have kicked in by now. I’m going to go take a look at how they are doing.
Once we are past the fork we can look at the algo change to duck the Scrypt ASICs and who ever has been attacking us with what is presumed redirected Scrypt resources.
-
Here we go again today with another 9hr High difficulty rate and only 1 hr at a lower difficulty rate once it resets.
Any idea on the time frame these difficulty changes might be implemented?
We def need to get this change going soon… This is killing loyal miners with the hash rate so low, and it will take over 9 hours to re-target???
-
These changes need to be tested carefully before implementation.
It’s in the testbed right now.
We all are keen to get it implemented, but we need to be sure, that it works as expected before we can implement it in the production network.
I’m sure, as soon as the tests are finished, Bushstar will announce the change and the new version of the wallet will be released
-
Inspirational . We need to deal with 30Ghash attacks. In the future may also be more.
-
Yes lizhi, we are in the 30 GH/s right now… and they keep pushing at least to times a day.
So, wellenreiter, keep up the good work!
-
The people involved should rattle their tip jars a little more. :)
-
The people involved should rattle their tip jars a little more. :)
rattle… rattle… rattle…
Lol :D
Look at my signature ;)
But I’m not doing this for tips, even if every tip is appreciated ;)
I want to keep feathercoin safe and solid in the long term.
-
Still, tipping culture is a positive one. :)
-
It is and it’s a nice motivation, indeed :)
-
Another way to stop multipools is to implement a block limiter. It accepts only a limited number of blocks per time frame and orphans the rest. Multipools waste about 90% of their hash power this way. I understand many may not like this solution, but PXC is going to adopt it in the next update. It doesn’t require a hard fork though.
-
rattle… rattle… rattle…
Lol :D
Look at my signature ;)
But I’m not doing this for tips, even if every tip is appreciated ;)
I want to keep feathercoin safe and solid in the long term.
Your work is appreciated :-)
Edit: you too wrapper
-
Another way to stop multipools is to implement a block limiter. It accepts only a limited number of blocks per time frame and orphans the rest. Multipools waste about 90% of their hash power this way. I understand many may not like this solution, but PXC is going to adopt it in the next update. It doesn’t require a hard fork though.
Could it be beneficial/possible for ftc to also add block limiting?
-
Block limiting stops more than a certain amount of blocks being mined in set time period. It does this by orphaning blocks. Very small coins may need this if their hash power can be sent up by hundreds of times but that does not apply to us, plus I would personally be unhappy if I spent two days solo mining a block at home to get my block orphaned by the block limiter.
Ghostlander has come up with a good solution for Phoenix coin but I do not believe that it suits us.
-
Ah ok. Fair enough. Was just curios.
