OutlierVentures / QTM-Interface

GNU General Public License v3.0
28 stars 18 forks source link

Meta Bucket Allocations #25

Closed BlockBoy32 closed 1 year ago

BlockBoy32 commented 1 year ago

I am getting 0's for all of the meta bucket allocations which I believe should have numbers in them. I made a state update function and added the meta_bucket_allocations to the state variables. I am not sure what you were intending with the logic so could I leave it up to you to adjust these values and for now I will just add default ones to use?

Screen Shot 2023-07-18 at 8 23 32 PM Screen Shot 2023-07-18 at 8 24 16 PM
BlockBoy32 commented 1 year ago
Screen Shot 2023-07-18 at 8 36 22 PM

building on that I really need this data too. You seem to already have some logic in place to get it so I am going to rely on you for it.

achimstruve commented 1 year ago

Working on this now!

achimstruve commented 1 year ago

It turns out solving this along with the individual utility allocations is like already building half of the model hehe. Requires some time to get it done, but I am on it.

achimstruve commented 1 year ago

The agent meta bucket allocations are built in and tested now!

image

achimstruve commented 1 year ago

Note that the holding supply amounts (From Holding Supply of prev. Month + Incentives + Airdrops) are not processed yet as they depend on later modules/steps!

However, you should have some data to start with for the utilities considering the green tested rows.

Note that utility share allocations (QTM rows 103 to 108) should be calculated from the individual agent utility share allocations. You'll find corresponding utility attributes for agents are already being integrated. See the picture below for reference.

So far these attributes are not used and the logic for them being used still has to be implemented.

image

achimstruve commented 1 year ago

Closing this issue as the meta bucket allocations are done now with exception of the free holding supply part, which is coming later down the road.

The next step is to implement the agent <> utility interactions. I opened a new issue for this and assigned it to you, @BlockBoy32