DAO Constitution

Governing rules of PathDAO & treasury

Fund utilisation mandate​:

- 80% of fund to be invested into blockchain gaming protocols and assets (tokens, NFTs) in private rounds and secondary markets​

- 15% of fund to be utilised to grow gamer and investor community through marketing, events, and rewards​

- 5% of fund to be utilised for operational expenses of the execution team​

​

Operational mandate​:

- Execution team has full mandate to deploy treasury at any amount with the objective of growing the treasury.

- Treasury is stored in multisig accounts (Gnosis or Fireblocks), or deployed into yield farming protocols governed by multisigs. Exception is granted to NFT assets required for gamer operations where multisig and cold wallets create too much operational complexity. ​

- Execution team is given mandate to develop an ecosystem of infrastructures with the objective of creative the most sticky web3 gamer experience, with the final objective of increasing treasury value. Team can utilise operating budget and marketing budget in respect to this growth and development. ​

- Execution team is given mandate to deploy Community $PATH tokens for the benefit of growing the ecosystem and community, as long as it follows the governing emission schedule​

- Changes to tokenomics that can affect $PATH and $PATH holders require governance voting (e.g. reward pools, emissions schedule)​

Governance:​

- $PATH tokens have an equal weight of voting​

- All allocated $PATH tokens are counted in governance regardless of it being vested or locked​ ​

Passed Proposals ​:

Proposal	Passed date
PIP-1: Liquidity Provision Incentives to increase LP depth	23/12/2021
PIP-2: Centralised Exchange Listing	28/12/2021
PIP-3: Yield Generation on Anchor Protocol	2/1/2022
PIP-4: Staking contract upgrade	8/1/2022
PIP-5: $PATH bridge to Polygon	12/3/2022
PIP-6: $PATH token value alignment	2/4/2022
PIP-7: Protocol-Owned Liquidity	10/5/2022
PIP-8: Additional $PATH utility on Polygon	30/5/2022