Skip to content

Hypha Issuance Contract Specification #6

Description

@n13

Specification follows the tokenomics document

Primarily, the release amount is calculated as follows

image

The release of tokens is then time dilated by the ratio of staked tokens vs total circulating supply

The idea behind this is that if the staking ratio is very high, more hypha tokens enter the market faster.

And if the staking ratio ("usage") is low, fewer hypha tokens enter the market (slower).

The release amount is then divided amongst a number of cohorts with different liquidity profiles - or payout prefernces.

Gross allocation

See 6.1 in the tokenomics whitepaper

Payout schedule for different cohorts

See 6.2 Circulating Supply in the whitepaper

Different cohorts receive different percentages of the total liquidity according to rules

_The circulating HYPHA increases following the supply curve and releasing liquidity for the various allocated cohorts and incentives. However, there are some liquidity preferences within the model.

  1. Hypha DAO Treasury receives a relatively large proportion of the initial issuance to ensure the project is adequately capitalized.

  2. Early Stakeholders receive 10% of their allocation on initial issuance.

  3. Launch Stakeholders receive preferential liquidity on ongoing issuance pushing back liquidity for the other cohorts._

  4. The launch event releases 15M tokens according to the table in 6.2

  5. Ongoing token issuance is calculated as follows:
    A - 30% goes to launch stakeholders until their stake is fully liquid.
    B - 50% goes to DAO incentives (staking rewards)
    C - The rest is divided between DAO treasury and early stakeholders according to their relative holdings.

Missing factors

We will get the constants k, e, and t (the time measurement) to create the actual calculation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions