Skip to content

The migration of significant computing power is causing a deflation of HACASH blocks. How can we adjust the difficulty to prevent the disruption caused by this migrating computing power? #44

@ADcarry-tech

Description

@ADcarry-tech

The first block at 0:00 on 3.8 is 731742
The first block at 0:00 on 3.9 is 732105,3.8-3.9 353 blocks were generated.
The first block at 0:00 on 3.10 is 732182,3.9-3.10 77 blocks were generated.
The first block at 0:00 on 3.11 is 732296,3.10-3.11 114 blocks were generated.
The first block at 0:00 on 3.12 is 732413,3.11-3.12 117 blocks were generated.
The first block at 0:00 on 3.13 is 732741,3.12-3.13 328 blocks were generated.
The first block at 0:00 on 3.14 is 732878,3.13-3.14 137 blocks were generated.
The first block at 0:00 on 3.15 is 733250,3.14-3.15 372 blocks were generated.
The first block at 0:00 on 3.16 is 733345,3.15-3.16 95 blocks were generated.
From the early morning of March 8th to the early morning of March 16th, over an eight-day period, theoretically, 288*8=2304 blocks should have been generated. However, only 1593 blocks were actually produced, representing a 30% contraction.
And due to uneven block generation, transaction waiting times are prolonged, potentially up to 2 hours. This affects the experience of new users and is not conducive to promotion.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions