[Dev] Hard fork to change retarget, averages and block time
-
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.
-
Hi All,
Just thought you “guys” should know Bush has been working very very hard with Wellenreiter on getting “Enhanced hash rate compensation” coded and tested.
We are getting to the stage where some code review would really help. Particularly looking at “shed painting protocols” and for any other code traps.
I’m hopefully we can get a more public test up on line, again a few volunteers to do some testing would encourage Bush to take some time to open it out.
Remember, the more members that get involved the safer and quicker we can get this done.
-
Hi All,
Just thought you “guys” should know Bush has been working very very hard with Wellenreiter on getting “Enhanced hash rate compensation” coded and tested.
We are getting to the stage where some code review would really help. Particularly looking at “shed painting protocols” and for any other code traps.
I’m hopefully we can get a more public test up on line, again a few volunteers to do some testing would encourage Bush to take some time to open it out.
Remember, the more members that get involved the safer and quicker we can get this done.
What can those of us with more limited coding abilities do?, I can read through code but not well enough to be of use. What else needs doing?
-
Hi Ryan,
You can probably help downloading and testing the new wallet, a little latter on. When we get the first public beta out.
At this stage, we mainly need Devs and miners/pools to get involved. “Lookin around” the actual coding, which is pretty bleeding edge to catch up on. Mainly due to complexity of how the “Hard Forking” system in the Bitcoind protocol works.
I didn’t worry too much about being a hacker, the codes pretty straight forward, as far as readability.
If you learn Github or the Feathercoin Guide / instructions to compile the source code in a Virtualbox, means anyone (even windows) can get hold of the fresh code and see what’s happening. That’s why those compile guide instruction show how to view the code in Qt Creator IDE (open source development environment.)
Learn Github. Set up and learn to compile code ready to do alpha testing.
Another requirement is help setting up a test net, I did get a Digital Ocean droplet set up with a p2pool feathercoin testnet at one stage, but I had to take that down. With the test net extra CPU miners would be advantageous, and would be easy to do, with a few instructions (that need compiling).
We need to update miners and pools that a hard fork is coming, members could help by giving pools and miners some warning that developments are a foot …
The main Devs are very busy, - Without help the development will go on, but take longer.
.
-
Let me know where to point my miner and where to setup an instance of a p2pool feathercoin test net. How big does the droplet need to be? O0
-
We’ll let you know, soon.
Concentration is on completing our test spec.
We found out yesterday that, the Feathercoin p2pool software needs an update to add testnet compliance. Once that is done (we can help, but can’t do it now) we can point miners (CPU) using cgminer to a “Test pool”, and members could help test mine then.
At the moment, we would also have to apply a compiled Feathercoind, to get the test version working. I couldn’t “self compile” on a 1 GB droplet. There may be a way to do it then re size down. It will run p2pool on a 0.5 GByte Droplet.
Let us know if you have skill sets to get that (or something similar) going and not interrupt the Devs, (too much).
-
Wellenreiter has fixed the p2pool and we are awaiting that to be merged.
https://github.com/wellenreiter01/p2pool-feathercoin.git
Here is the link to any member who can help to set up a test p2pool, it will need the --testnet switch.
The idea a p2pool is, the software changes are on the server, so only one place needs up-dateing with fixes and we can get less technical members attached as say, cpu miners.
Again, we’re a bit busy, so some help would be appreciated and be very effective, so worth the effort…
