We have been pretty quiet lately, but still plodding away behind the scenes. Of particular note, we finished our "on chain operations" module and have monitored performance long enough to be confident that it's working.
Here are the flows:
The game itself never sells any THREE; but on-chain flows mirroring in-game activity result in regular purchases of THREE, particularly enough THREE to mirror the reward pool flows.
Instead of immediately burning the target amounts, we will gradually fund the three.burn account with the proposed burn value but inject it into the LP.
Once every game account is caught up to its target holdings levels to fully mirror in-game flows, we will target 100% holdings in THREE on three.growth until it holds more THREE than it was originally issued.
Then we will begin our THREE burns until the total THREE that we have burned catches up to our target burn levels.
As we burn THREE, we will gradually shift funds back from the three.burn account to keep its holdings at (proposed burn minus actual burn) so once we are caught up with our burn targets then three.burn will hold nothing.
It's a gradual plan that gets us back to where we wanted to start, but enables us to still release free-to-play when it is ready instead of having to rebuild the growth fund because we burned it all.
The cash flows that we earn on our LP positions are split, with part of it helping our accounts compound into their target levels, and part of it funding the ongoing skill-based rewards pool. When we have reached our burn targets, we will recalibrate and double the flows going into the rewards pools.
We are making good progress on the Autonomy module. It will allow users to set workgroups and priority levels that allows a lot more "autoplay" functionality within their Three Legacy households, shifting action from manual "click all the time" levels up to a more strategic "establish priorities and fine-tune how the different settings interact."
We will post more about the different settings available and how they will interact when the module is ready to release.