Bitcoin Finance Core FIP-03 TOG Updates:

TOG Pre Build Notes:

A. The difficulty adjustment rules triggered by the computing power fluctuation threshold:

Excessive computing power growth leads to increased difficulty. When the transaction price fluctuates significantly and causes a large number of miners to go offline, the computing power is insufficient to support When the entire blockchain network normally discovers new blocks,
a timeout mechanism is introduced. This update will not affect all other features of the BTC network and is limited to the following trigger conditions
If you have any questions about the above update preview, please contact us.
[email protected]

TOG(Triger of Block Timeout Generation) Trigger conditions:

1. No new blocks have been discovered for long time.

2. A large fluctuation in computing power leads to a large adjustment in difficulty.

B.Bitcoin Finance Layer2:

Introduce the second-layer network, provide API and technology stack support for creating trading pairs, introduce the stable currency USDT, and open up the exchange and mapping between USDT, BSC, and ETH.

Download & Update BitcoinFinance Core:

Implementation

It should be noted that the states are maintained along block chain branches, but may need recomputation when a reorganization happens.

Given that the state for a specific block/deployment combination is completely determined by its ancestry before the current retarget period (i.e. up to and including its ancestor with height block.height - 1 - (block.height % 2016)), it is possible to implement the mechanism above efficiently and safely by caching the resulting state of every multiple-of-2016 block, indexed by its parent. Warning mechanism

To support upgrade warnings, an extra "unknown upgrade" is tracked, using the "implicit bit" mask = (block.nVersion & ~expectedVersion) != 0. Mask will be non-zero whenever an unexpected bit is set in nVersion. Whenever LOCKED_IN for the unknown upgrade is detected, the software should warn loudly about the upcoming soft fork. It should warn even more loudly after the next retarget period (when the unknown upgrade is in the ACTIVE state).