User inputs

These sheets cover design parameters, hypotheses, and the vesting schedule that should be tested in the simulation. These will be parameters that the dashboard user will be able to change and play with once the simulation is up-and-running.

Base

This sheet contains some key configuration parameters common to every tokenomics simulation. Only a single row of values should be filled in.

The values required are:

Project name (Text): Name of the project. Will be use as the dashboard title.
Initial total supply (Number): Default value for the initial amount of tokens that are minted at the token generation event, in millions of tokens. The dashboard user will be able to change this parameter.
Min/max Initial total supply (Number): Minimum and maximum initial amount of tokens that the user will be able to choose in the simulation, in millions of tokens.
Initial token price (Number): Default token price at the beginning of the simulation. Note that this is only the initial price. The evolution in price with time in the simulation will be the result of the simulated market dynamics.
Min/max Initial token price (Number): Minimum and maximum initial token price that the user will be able to choose in the simulation.
Default simulation time frame (Number): Default timespan of the simulation in the dashboard, in months.
Min/Max simulation time frame (Number): Minimum and maximum simulation time frame that the user will be able to choose in the simulation, in months.
Timestep (Number): Size of the steps in the simulation, in seconds. Short timesteps lead to more granular simulations, but it takes longer to simulate, making the dashboard less responsive. Higher timesteps are faster to simulate, but might lead to imprecisions (a minimum of 3600 seconds is recommended).
Login screen (ON/OFF): Enable/Disable the login screen. The login screen turns your site into private and allows 2 different kinds of users: one for the team, with the full capabilities, and another one for investors, where they are not capable of changing the input parameter values.

Static Parameters

This table contains all the numerical input parameters to the simulation. This includes design parameters (e.g. a fee percentage in the protocol) and hypotheses (e.g. the expected average usage per user and month for a service).

The table defines a default value for each parameter, but generally the parameter will be available in the dashboard sidebar to be adjusted by the user using sliders or a textbox input (see the “Sidebar Configuration” sheet).

Note that this table should NOT include time-dependent parameters (see the "Time Dependent Parameters" sheet) or the parameters relating to the vesting schedule (see the “Vesting” sheet).

To complete the table, add one new line per static parameter you want to include, with the following information in the corresponding column for each:

Reference (Alphanumerical): a unique identifier to this parameter for use within the spreadsheet. It will not be displayed anywhere in the dashboard. It must start with a letter and contain only letters, underscores (_), or numbers. The reference must be unique, and is not case sensitive. It is a good practice to start with "SP_..." for the references in this section.
Display Name (Text): Name of the parameter, and how it will be displayed in the dashboard.
Help (Text, optional): Information to be shown as a the tooltip in the dashboard.
Format (Number): Number of decimals that will be shown to the end user.
Units (Text, optional): units of the parameter, like “USD”, “days” or “%”. It will be shown along the values in the dashboard.
Default value (Number): The default value the parameter will take in the dashboard until the user modifies it.
Min/max value (Number): Limits on the values that a parameter will have in the sliders.
Step (Number): minimum change allowed in the value of a parameter in the sliders.
Min/Max allowed value (Number, optional): when the option Textbox Input is active (instead of sliders) in the dashboard, the max/min allowed value to be input by the user. For example, this should be used when a value should never be negative, like an amount of tokens as reward for an action. In such a case, we would put 0 as the minimum allowed, and leave the max allowed empty.

Selector Parameters

This table contains input parameters with a set of options for the user to select from. For example, these parameters can be used to select between two or more different designs for a mechanic in the simulation.

After being included in the Sidebar Config sheet, they will show up in the dashboard as a dropdown selector, with the first element as the default.

To complete the table, add one new line per selector parameter you want to include, with the following information in the corresponding column for each:

Reference (Alphanumerical): a unique identifier to this parameter for use within the spreadsheet. It will not be displayed anywhere in the dashboard. It must start with a letter and contain only letters, underscores (_), or numbers. The reference must be unique, and is not case sensitive. It is a good practice to start with "SE_..." for the reference.
Display Name (Text): name of the parameter, and how it will be displayed in the dashboard.
Options (List of texts): the possible values for the selector, separated by “;”. The first option listed will be the default option.
Help (Text): information to be shown as a the tooltip in the dashboard.

Time Dependent Parameters

This table contains all the inputs to the simulation that constitute a time series (e.g. a monthly projection of the number of users of the protocol).

The values defined in the table are the defaults that will be shown in the dashboard, but which can be adjusted by the user. The values will be linearly interpolated.

To complete the table, add one new line per time dependent parameter you want to include, with the following information in the corresponding column for each:

Reference (Alphanumerical): a unique identifier to this parameter for use within the spreadsheet. It will not be displayed anywhere in the dashboard. It must start with a letter and contain only letters, underscores (_), or numbers. The reference must be unique and is not case sensitive. It is a good practice to start with "TDP_..." for the reference.
Display Name (Text): Name of the parameter, and how it will be displayed in the dashboard.
Help (Text, optional): Information to be shown as a the tooltip in the dashboard.
Month X (Number): The value of the parameter at the start of that month in the simulation. Any value left empty in the table will be ignored, and will be linearly interpolated from the closest values available. If a simulation is expected to run only up to the (for example) 50th month, the 51st month onwards can be left empty.

Vesting

This table contains the token allocation and vesting schedule. The configuration defined is the one that the end user will see as default in their simulation. However, they will be able to change parameters values on the final dashboard.

To complete the table, add one new line per vesting entity (i.e. section of the token allocation) you want to include, with the following information in the corresponding column for each:

Reference (Alphanumerical): a unique identifier to this parameter for use within the spreadsheet. It will not be displayed anywhere in the dashboard. It must start with a letter and contain only letters, underscores (_), or numbers. The reference must be unique and is not case sensitive. It is a good practice to start with "VE_..." for the reference.
Display Name (Text): name of the vesting entity, and how it will be displayed in the dashboard. • Agent reference (Reference): the reference for the agent that receives the token allocation. Any agent that receives tokens must be defined on the "Agents" sheet.
Allocation percentage (Number, from 0 to 100): The percentage of the total supply that an agent will receive as allocation.
Start month (Number): the month of the simulation when the vesting process starts for a given agent. Both "Cliff Month" and "Vesting Months" start from the "Start Month".
Cliff month (Number): the amount of months that will happen until the first tokens are vested. It is added to the "Start Month" value.
Vesting months (Number): month at which an agent will have received the 100% of the tokens allocated. The vesting is linear and starts from the "Start Month".
Vesting sales percentage (Formula, optional): this is an optional feature to define a percentage of the vested token that will end up being sold on the market eventually, according to the sales mean time defined in the next column. It sets up automatically a simple sales flow between the agent this token allocation is assigned to, and the market. However, you can define an equivalent flow with different mechanics manually in the Flows section if you prefer.
Vesting sales mean time months (Formula, optional): this is an optional feature to define the mean number of months it will take between unlocking and selling the token on the market, up to the percentage of the allocation defined by the previous column. It sets up automatically a simple sales flow between the agent this token allocation is assigned to, and the market. However, you can define an equivalent flow with different mechanics manually in the Flows section if you prefer.

In order to have a part of the allocation unlocked from the start, you can set the "Start month", "Cliff month" and "Vesting months" all to 0. This will result in the allocation for that entity being unlocked from the beginning of the simulation.

PreviousSpreadsheet Structure NextToken Mechanics

Last updated 5 months ago