🔁Redistribution Mechanism
We've designed an innovative mechanism that redistributes the value players inject into the game, back to them.
Last updated
We've designed an innovative mechanism that redistributes the value players inject into the game, back to them.
Last updated
The first instance of our Redistribution Mechanism will be in CafeCosmos. Players will be able to earn token through the Recipe Pools that reward players when they cook recipes. Let's take a look at how it works:
Tokens collected from Direct Contributions and Land Purchases fortify our Master Pool. 💼💰
These tokens are systematically distributed to various recipe pools. 💧➡️🏞️
Over time, the Master Pool accumulates tokens, strengthening the system. ⏳💪
At set intervals, referred to as 'X' period, a portion of the tokens are released from the Master Pool. 🗓️🔓
These tokens are then gradually disbursed to the recipe pools over this 'X' period. 🔄⏲️
Best of all, we can adjust the allocation to each pool as required. 🎛️💡\
Welcome to the sustainable world of CafeCosmos Redistribution! 🌐👍
TOTL = DCON + LAND
Our Master Pool is like a dam. It collects tokens from two rivers: Direct Contributions (DCON) and Land Purchases (LAND).
💡 Key Variables:
TOTL: The reservoir of tokens in the Master Pool
DCON: The inflow of tokens from direct contributions
LAND: The stream of tokens from land purchases
DIST = PERC * TOTL
Every so often (X period), the dam's gates open. A certain percentage (PERC) of the accumulated tokens (TOTL) gets released.
💡 Key Variables:
DIST: The tokens getting ready for a journey from the Master Pool
PERC: The percentage of tokens that get to start the journey each time. This value ranges from 0 to 1. For example, PERC = 0.1 means 10% of TOTL tokens get to leave the Master Pool each round.
X: The frequency at which the journey happens, i.e., the release of tokens from the Master Pool.
DRIPi = ADJi * DIST
Once the tokens leave the dam, they go to different recipe pools (DRIPi). The share each pool gets depends on an adjustable factor (ADJi).
💡 Key Variables:
DRIPi: Tokens going to recipe pool i during a time period X.
ADJi: An adjustable knob that dictates the share of tokens each pool i gets.
DIST: The tokens that were just released from the Master Pool.
🚨 Important Rule: Sum(ADJi) = 1 for all pools i from 1 to n.
This ensures that all tokens set for distribution are indeed distributed across the various pools.
If the sum of ADJi was less than 1, not all tokens would be distributed.
If it was more than 1, we would be trying to distribute more tokens than we have released.
DripRATEi = DRIPi / xRate
Tokens love to take their time, which is why they don't rush into the pools all at once. Instead, they drip at a certain rate (DripRATEi), based on the total tokens to distribute (DRIPi) and the duration (xRate).
💡 Key Variables:
xRate: The total duration of the token dripping process (in seconds). This corresponds to X, the schedule at which tokens are released.
DripRATEi: The speed at which tokens flow into each recipe pool.
It's important to identify and understand what parameters we can adjust in the equations and how that impacts the mechanism. We explore this a little below.
X: This is the rhythm setter. It determines how often tokens leave the Master Pool and head to the recipe pools. X could be in time units (e.g., every hour or day) or event-driven (e.g., after 100 transactions or each time a new user joins).
DCON: Tokens from direct contributions act as a booster. They enhance the reward pool in the Master Pool, aiding stability, and kick-starting the system. This is especially useful during low activity periods or to reward engagement.
PERC: This is the floodgate controller. A higher PERC value opens the gates wider, allowing more tokens to start their journey from the Master Pool, which in turn increases the rewards but drains the Master Pool faster. A lower PERC value conserves the Master Pool but slows down the rewards.
ADJi: The ADJi factor provides a control knob for the shares of each recipe pool. By adjusting it, you can regulate how much each pool receives. This is a powerful tool when upgrading to an algorithmic controller.