Supported Feathercoin client versions: Current production Version: 0.13.1.

Info: If you have problems to post, create one post in the ‘newbies’ category and try again. If you have further problems, find support under Guides or use the shoutbox

FTC Block Difficulty analysis 500 difficulty MHash "attack"


  • Moderators

    I’ve done an analysis of 10/09/2017

    It can be seen that a very large hash rate was directed at FTC at 9am, 12:30pm, 22:30 and 8 am 11/09/2017.

    Block Time Trans Value Difficulty CDD Block Time Tran Temporal Anomaly
    1879055 2017-09-11 07:46:25 4 1878422.28 13.272 137.97 00:01 1
    1879054 2017-09-11 07:46:24 3 2502104.72 12.166 136.55 00:09 1
    1879053 2017-09-11 07:46:15 3 1514184.12 11.152 97739.62 00:09 1 1

    Transactions 1878844 and 1878869 were not done during high hash rate, so had long transaction block confirmation times. The temporal anomaly is due the time of these blocks being slightly before the previous block, however its within a “normal margin”, especially with such a large over hash rate of ~50 times.

    Overview and Conclusions

    The Feathercoin difficulty has increased to an average value of 36, with peak values near 500. The hash variations is much larger than previous analysis, showing very high levels of hash power being directed at FTC. Almost too high possibly indicating a very large pool or some new equipment available to one miner.

    This analysis is a check of blockchain timings and activity. Over 1000 Blocks … from 9th to 10/07/2017

    The average block time over 1000 Blocks is bad at 1:33 mins

    The percentage of blocks with transactions was ~14% of blocks. The transfer to Fee value is also “normal” at 1% Value transfered

    There were 167 minor time anomalies in the blockchain timings for the 1000 min test period. Many of those time anomalies were due to Blocks with the similar times, before.

    Feathercoin Block Analysis

    FTC is routinely analysed if there are any concerns. These analysis are stored on Github to use as templates or review historical analysis.

    Values of the parameters analysed can be extracted from FTC debug file. The ABE software used to produce sites such as http://explorer.feathercoin.com/chain/Feathercoin?count=1000&hi=1783533 does some of this work for you, so for sporadic analysis of a few days it is convenient to scrape the data from there.

    Normally the web site displays up to 100 blocks but this can be expanded manually.

    The data is accumulated in a text document, then pasted into the spreadsheet template from the last analysis. Charts and calculations data ranges are corrected as required.

    Overview of the 1000 min period up to 11/09/2017

    FTC Fees over 1000 Blocks 80000
    Transactions less fees 8.8M FTC
    1 % Fee to Transaction volume ratio
    Percentage Blocks with Transaction 14%
    Average Block Time 4 days 1:33 mins

    Block Difficulty

    FTC Difficulty 10/09/2017

    Block Times

    FTC Block Times 10/09/2017

    Transactions per Block

    FTC Transactions 10/09/2017

    Block Transaction values

    FTC Transactions Values 10/09/2017


  • Moderators

    The block time has settled down to 1:06. The high block rate is still slightly evident. Probably changed to shorter duration burst to reduce difficulty increase.

    09:40pm, 10:20, 11:20, 12:00, 14:00 …

    Block Difficulty - 11-09-2017

    FTC Difficulty 11/09/2017

    Block Times

    FTC Block Times 11/09/2017

    Transactions per Block

    FTC Transactions 11/09/2017

    Block Transaction values

    FTC Transactions Values 11/09/2017


  • Moderators

    Thanks @wrapper

    what’s confusing me is…I can figure out how much hashrate was thrown at FTC

    The below chart shows hashrate overlayed with difficulty and we can see the difficulty skyrocket but not the hashrate.

    Maybe these were only switched on for very short amounts of time ? enough to affect network difficulty but not enough to show up in the Bitinfocharts graphs ?

    alt text


  • Moderators

    The dashed line is the hash rate, which went up from ~ 1.4 GHash to 3.2 GHASh = +150%

    The solid line is the difficulty, which went up from about 284 to ~ 600 = +110%

    given the fact, that the difficulty is calculated based on an average of hashrate and also damped, and that the high hashrate peaks where relatively short, I think the difficulty reacted as designed.

    @wrapper , please correct me, if I’m wrong


  • Moderators

    am I stupid ? the dashed lines raise in my image is in june… ?


  • Moderators

    indeed it is june… 😉

    you may need to change the time frame and duration ?


  • Moderators

    @Wellenreiter said in FTC Block Difficulty analysis 500 difficulty MHash "attack":

    indeed it is june… 😉

    yu may need to change the time frame and duration ?

    yay!! i’m not stupid.

    Even zoomed in…
    alt text

    it doesn’t make sense that a hashrate of 1.85 Ghs would have difficulty 554


  • Moderators

    @AcidD You are probably seeing the effect of different averages. That’s why I look at the actual difficulty.
    The only way to calculate the hash rate is from the difficulty, which is calculated from the times of previous blocks.



  • Great post! Thanks @wrapper

    So assume the worst for a minute: someone privately has figured out ASIC mining neoscrypt and is planning a sustained attack?

    What’s the contingency plan? I think i remember years back a discussion that if that ever were to happen, the devs would race to put together yet another unique algo to make it ASIC resistant again.


  • Regular Member

    @bsotnikow said in FTC Block Difficulty analysis 500 difficulty MHash "attack":

    Great post! Thanks @wrapper

    So assume the worst for a minute: someone privately has figured out ASIC mining neoscrypt and is planning a sustained attack?

    What’s the contingency plan? I think i remember years back a discussion that if that ever were to happen, the devs would race to put together yet another unique algo to make it ASIC resistant again.

    I understand trying to plan for the worst but my first thought here is why would someone do this? Developing an ASIC for NeoScrypt for the purpose of attack is foolish. ASICs are crazy expensive to develop and if used only to attack the network there is no recoup of that investment. The better option would be to develop it and mine all NeoScrypt coins for profit. Or sell the ASIC miners to the public.



  • @AmDD This is all very true. But at some point as there are fewer and fewer surviving old coins, it’ll make sense for them to try and disable each other. Profitable not directly, but by disabling the “competition”. (or it may appear smart to do so and someone does it, i think these kinds of attacks would hurt trust in all coins tho and be stupid). There are a lot of unpredictable instantly now rich people out there, who knows what they might do.

    Or a less nefarious situation. FTC price rises to the point where developing an ASIC miner does make sense. Just wondering if the long term goal is to remain a GPU-minable coin or if ASIC would be embraced?


  • Moderators

    @bsotnikow

    while we don’t have another Asic resistant algorithm in our pockets, the philosophy behind Feathercoin is to keep the mining as distributed as posible, and therefore Asics won’t be embraced by the community or the developers



  • @Wellenreiter Cool, thats what i thought. ASIC isn’t something i’d want to embrace for FTC either!


 

Looks like your connection to Feathercoin Forum was lost, please wait while we try to reconnect.