> For the complete documentation index, see [llms.txt](https://hai-9.gitbook.io/hai-governance-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hai-9.gitbook.io/hai-governance-documentation/governance/intro-to-governance/governance-parameters-tbc.md).

# Governance Parameters (TBC)

Up-to-date governance parameters

## Introduction

This page outlines the governance parameters for both on-chain and off-chain (Discourse / temperature check) governance. Note that although on-chain voting on Tally is weighted and requires delegation, the initial Discourse Poll, or temperature check, is not token weighted or gated by delegation. 

**On-chain**

This section outlines the on-chain governance parameters for the HAI Governance smart contracts (managed via [Tally](https://www.tally.xyz/governance/eip155:1:0xd8E2114f6bCbaee83CDEB1bD6650a28BBcF144D5)). All parameters are displayed in the table below.

Execution Delay, Voting Delay, and Voting Period are based on the assumption of a 15 second block creation time on the Ethereum Mainnet.

HAI Governance inherits functionality from the OpenZeppelin [GovernorSettings.sol module](https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/governance/extensions/GovernorSettings.sol), allowing **Voting Delay**, **Voting Period**, and **Proposal Threshold** parameters to be updated through an on-chain governance proposal and voting process.

| Parameter                 | Value                   |
| ------------------------- | ----------------------- |
| Voting Duration           | 17280 blocks (3 days)   |
| Voting Delay              |                         |
| Execution Delay           | 172800 seconds (2 days) |
| Quorum Numerator          | XXX% of KITE supply     |
| Proposal Threshold        | XXX                     |
| ds-pause timelock 2:1 day |                         |

1. More votes are cast in favor than against. 
2. The total number of votes cast in favor is at least the following percentage of the votable tokens: 
   1. 25% for an RFS HIP. 
   2. 3% for a standard HIP. 

A proposal passes if two conditions are met:

\
**Kite allocation**

* 20% - Team & Advisors (10+ folks)
* 20% - DAO Treasury
* 20% - FLX incentive alignment
* 40% - Community Incentives<br>