Randomized Epoch based distributed rebase
Over the past few weeks, we have been trying to optimize the countercyclical pressure that arises when the system goes through negative suppression.
We are benchmarking and optimizing the environments that sequentialize the rebase through the gauntlet.
How does Dynamo work?
What usually happens as of today is that we go through linear regression in our systems supply wrt to the rebase calls that happens regularly.
Dynamo dissects that rebase continuity by introducing epoch-based rebase calls, in simpler words within 1 epoch only 1 rebase call would be sustained by the system.
We have initialized the first epoch in the linkbase system as 7 days, and further epochs are determined through POA’s RandomAura.sol for determining on-chain randomness based epoch value for our system.
This will be the de-facto way of maintaining the system hear on.
What to expect?
Starting from today after 7 days, the first rebase call will take place bringing the price of LBD to the target price of (Chianlink’s_Fully_Diluted_Mcap)*0.1¹⁰
Then the system will run the function from randomaura to derive the length for the next epoch.
For example, after 7 days the rebase() is called, and then immediately the length of the next epoch is determined, for say the length of the next epoch computes to be 3, so after 3 days from the first function call, the rebase is triggered once again.
The length of a particular epoch will be hidden and masked until the system executes the call, and only can be determined after the call has been executed.
This makes the system more dynamic all the while collecting the 3% tax and rerouting it to the LPs in valhalla.