bushstar (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2013, 11:24:24 AM |
|
Feathercoin - The Miner Update - Hard Fork Block 87948The latest Feathercoin version 0.6.4.4 is now available and is a mandatory update. This update includes a hard fork of the block chain to accommodate the changes made in this patch. This hard fork should happen roughly around the 1st October which is only a week away. To be able to send and receive Feathercoin after block 87948 you have to use the new client. Continuing to use old clients after the hard fork could result in the loss of coins. Primarily this update is to further the refine of the difficulty adjust. Though the current Feathercoin difficulty which we changed to get us out of a tough spot it is not fair for long term miners who have to experience 41.4% swings on every adjust. The new code will adjust four times more frequently at 126 blocks but to approximately 9% which still gives the exact same overall adjust. To prevent the difficulty from being sent up or down too rapidly the current 504 sample window is being maintained and damping is being introduced to reduce fluctuations between extremes. There have been long running discussion and arguments on the Feathercoin forum including simulations of various different options surrounding this solution. Feel free to take a look at the latest discussion here. To get the latest update please go to the Official Feathercoin Website and download the client from the homepage. Official Feathercoin WebsiteChangelog: Move to 126 difficulty adjust with 504 averaging window and .25 damping Reduce effectivness of Time Warp attack Reinstate CAlert system Make getnetworkhashps more accurate Release Windows binary with QR encode
|
|
|
|
ChekaZ
Legendary
Offline
Activity: 1884
Merit: 1005
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2013, 11:39:16 AM |
|
Great to see the work doesnt stop! ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
BTC: 1Ges1taJ69W7eEMbQLcmNGnUZenBkCnn45 FTC: 6sxjM96KMZ7t4AmDTUKDZdq82Nj931VQvY
|
|
|
smoothie
Legendary
Offline
Activity: 2492
Merit: 1473
LEALANA Bitcoin Grim Reaper
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2013, 11:42:03 AM |
|
Though the current Feathercoin difficulty which we changed to get us out of a tough spot it is not fair for long term miners who have to experience 41.4% swings on every adjust.
How so? If there is an even playing field (i.e. all participants agree to the rules of the network) how is that not fair?
|
███████████████████████████████████████
,╓p@@███████@╗╖, ,p████████████████████N, d█████████████████████████b d██████████████████████████████æ ,████²█████████████████████████████, ,█████ ╙████████████████████╨ █████y ██████ `████████████████` ██████ ║██████ Ñ███████████` ███████ ███████ ╩██████Ñ ███████ ███████ ▐▄ ²██╩ a▌ ███████ ╢██████ ▐▓█▄ ▄█▓▌ ███████ ██████ ▐▓▓▓▓▌, ▄█▓▓▓▌ ██████─ ▐▓▓▓▓▓▓█,,▄▓▓▓▓▓▓▌ ▐▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▌ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓─ ²▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓╩ ▀▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▀ ²▀▀▓▓▓▓▓▓▓▓▓▓▓▓▀▀` ²²² ███████████████████████████████████████
| . ★☆ WWW.LEALANA.COM My PGP fingerprint is A764D833. History of Monero development Visualization ★☆ . LEALANA BITCOIN GRIM REAPER SILVER COINS. |
|
|
|
Nutnut
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2013, 12:01:39 PM |
|
Perhaps loyal miners would have been a better term. In short, when the diff swings up 41% the hashrate drops to ~3Gh/s. The LOYAL miners, rather than hop to the next most profitable coin stick around and mine at a higher diff for 2+ days to bring the diff back down. Then when the diff does swing down by 41%, all the multipools and profiteers swing their miners back to FTC, the hashrate jumps to ~10Gh/s and so the good times (low diff) only lasts for 8 hours before swinging up again. This update will stop the 41% bounce and limit it to 9%. There will be swings still of course but hopefully the effect will be reduced. Simples. Of course, if you are not a loyal miner, you may not see the benefits, possibly the opposite but we're all about looking after the loyal guys in the community. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) That is all.
|
|
|
|
smoothie
Legendary
Offline
Activity: 2492
Merit: 1473
LEALANA Bitcoin Grim Reaper
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2013, 12:35:22 PM |
|
Perhaps loyal miners would have been a better term. In short, when the diff swings up 41% the hashrate drops to ~3Gh/s. The LOYAL miners, rather than hop to the next most profitable coin stick around and mine at a higher diff for 2+ days to bring the diff back down. Then when the diff does swing down by 41%, all the multipools and profiteers swing their miners back to FTC, the hashrate jumps to ~10Gh/s and so the good times (low diff) only lasts for 8 hours before swinging up again. This update will stop the 41% bounce and limit it to 9%. There will be swings still of course but hopefully the effect will be reduced. Simples. Of course, if you are not a loyal miner, you may not see the benefits, possibly the opposite but we're all about looking after the loyal guys in the community. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) That is all. Why not then just remove all that and go with the most granular diff adjustment (i.e. after each block)?
|
███████████████████████████████████████
,╓p@@███████@╗╖, ,p████████████████████N, d█████████████████████████b d██████████████████████████████æ ,████²█████████████████████████████, ,█████ ╙████████████████████╨ █████y ██████ `████████████████` ██████ ║██████ Ñ███████████` ███████ ███████ ╩██████Ñ ███████ ███████ ▐▄ ²██╩ a▌ ███████ ╢██████ ▐▓█▄ ▄█▓▌ ███████ ██████ ▐▓▓▓▓▌, ▄█▓▓▓▌ ██████─ ▐▓▓▓▓▓▓█,,▄▓▓▓▓▓▓▌ ▐▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▌ ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓─ ²▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓╩ ▀▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▀ ²▀▀▓▓▓▓▓▓▓▓▓▓▓▓▀▀` ²²² ███████████████████████████████████████
| . ★☆ WWW.LEALANA.COM My PGP fingerprint is A764D833. History of Monero development Visualization ★☆ . LEALANA BITCOIN GRIM REAPER SILVER COINS. |
|
|
|
erk
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2013, 12:50:19 PM |
|
I like the windows installer, a bit more pro than a lot of the other coins that you basically unzip.
|
|
|
|
Conqueror
Legendary
Offline
Activity: 1354
Merit: 1020
I was diagnosed with brain parasite
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 24, 2013, 03:46:44 PM |
|
Just perfect, no more diff traps for FTC!
|
|
|
|
SaltySpitoon
Legendary
Offline
Activity: 2590
Merit: 2156
Welcome to the SaltySpitoon, how Tough are ya?
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 29, 2013, 05:02:43 AM |
|
Stickied for a day or so. I'll be watching the thread, but please send me a pm after the fork target block has been passed.
|
|
|
|
flound1129
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 29, 2013, 08:28:03 AM |
|
Perhaps loyal miners would have been a better term. In short, when the diff swings up 41% the hashrate drops to ~3Gh/s. The LOYAL miners, rather than hop to the next most profitable coin stick around and mine at a higher diff for 2+ days to bring the diff back down. Then when the diff does swing down by 41%, all the multipools and profiteers swing their miners back to FTC, the hashrate jumps to ~10Gh/s and so the good times (low diff) only lasts for 8 hours before swinging up again. This update will stop the 41% bounce and limit it to 9%. There will be swings still of course but hopefully the effect will be reduced. Simples. Of course, if you are not a loyal miner, you may not see the benefits, possibly the opposite but we're all about looking after the loyal guys in the community. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) That is all. By profiteers you mean those guys who saved the coin from 51% attack back by switching to FTC when the diff dropped a couple months ago?
|
Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
|
|
|
|
erk
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 29, 2013, 12:09:21 PM |
|
I would love to hear how you're going to reduce the effectiveness of the TW Exploit and which one?
Either you're vulnerable to the exploit or you're not, there is no middle ground.
~BCX~
Read the source code and you might learn something.
|
|
|
|
bushstar (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 29, 2013, 08:55:42 PM |
|
I would love to hear how you're going to reduce the effectiveness of the TW Exploit and which one?
Either you're vulnerable to the exploit or you're not, there is no middle ground.
~BCX~
We experienced attacks where Feathercoin blocks were being created two hours into the future. This is the most that the protocol will tolerate and is the default of Bitcoin which has 12 blocks in that time period. We have 12 blocks in a 30 minute period and our code as been adjusted to reject blocks outside of that time period. So the attackers can still swing out time but not by as much. With adjusts every 126 blocks (5.25 hours) having attackers swing our time by two hours would be a huge problem so we had to limit this in some way.
|
|
|
|
aa
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 30, 2013, 07:19:42 AM |
|
Just let this piece of shit coin die already.
|
|
|
|
digitalindustry
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 30, 2013, 07:25:33 AM |
|
Just read the whole things from start to finish on the FTC forum .
as you know i'm not a holder of FTC but i think these implementations help the FTC community -
particularly the 504 averaging window and .25 damping
in conjunction with the shortening of the time regarding the "Time warp" flaw.
as this can help sure up security which ultimately supports confidence to the degree that you can control that aspect.
so good work.
|
- Twitter @Kolin_Quark
|
|
|
ChrisJ
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
September 30, 2013, 07:03:39 PM |
|
Just let this piece of shit coin die already.
Survival is the best form of revenge... hmm that gives me an idea.
|
I want to make the world better than I found it
|
|
|
flound1129
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 01, 2013, 05:14:30 AM |
|
After updating, two blocks Multipool found were rejected with the following error:
ThreadRPCServer method=submitblock ERROR: AcceptBlock() : rejected by synchronized checkpoint ERROR: ProcessBlock() : AcceptBlock FAILED
What is the fix for this?
|
Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
|
|
|
Balthazar
Legendary
Offline
Activity: 3108
Merit: 1359
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 01, 2013, 06:39:42 AM |
|
You can't fix this. This message means that another block is already accepted by network and successfully checkpointed. It seems that blockchain is too fast for the current checkpoints implementation/settings. You can switch it into advisory mode to prevent such events in the future.
But it's better to change checkpoints interval setting to 6-12 blocks.
|
|
|
|
erk
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 01, 2013, 07:59:06 AM |
|
You can't fix this. This message means that another block is already accepted by network and successfully checkpointed. It seems that blockchain is too fast for the current checkpoints implementation/settings. You can switch it into advisory mode to prevent such events in the future.
But it's better to change checkpoints interval setting to 6-12 blocks.
Are you sure? The advanced checkpointing has been running since August, you should have noticed any problems like that ages ago. I am inclined to think it was something else.
|
|
|
|
flound1129
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 01, 2013, 08:13:28 AM |
|
You can't fix this. This message means that another block is already accepted by network and successfully checkpointed. It seems that blockchain is too fast for the current checkpoints implementation/settings. You can switch it into advisory mode to prevent such events in the future.
But it's better to change checkpoints interval setting to 6-12 blocks.
So I basically got 2 orphans in a row is what you're saying?
|
Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
|
|
|
bushstar (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
October 01, 2013, 08:51:03 AM |
|
So I basically got 2 orphans in a row is what you're saying?
You said those blocks got orphaned after updating but were those blocks minted before you updated or after? Blocks found on the old chain will get orphaned by the new fork. If anyone wants to continue using 0.6.4.3 they would need to set ACP to advisory.
|
|
|
|
|