Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the reading-time-wp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /usr/html/blog/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /usr/html/blog/wp-includes/functions.php:6114) in /usr/html/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":124,"date":"2023-05-31T15:27:00","date_gmt":"2023-05-31T13:27:00","guid":{"rendered":"https:\/\/prodtest.hacken.ai\/blog\/?p=124"},"modified":"2023-05-31T18:09:45","modified_gmt":"2023-05-31T16:09:45","slug":"hdao-hai-inside-decision-making-flow","status":"publish","type":"post","link":"https:\/\/site.hacken.ai\/blog\/?p=124","title":{"rendered":"hDAO: HAI inside Decision-Making Flow"},"content":{"rendered":"\n

<\/p>\n\n\n\n

At hDAO, we\u2019re all about empowering our community to build a secure Web3 ecosystem that\u2019s inclusive for all. To achieve the mission, we\u2019re creating a platform that welcomes promising ideas and proposals from anyone in our community.<\/p>\n\n\n\n

As befits DAOs, the hDAO governance process is divided into two parts \u2014 Request for Proposal (RFP) that promotes a rough idea and the reasoning for the change, and the Proposal itself \u2014 a fully-fledged document with an already existing vision of technical implementation. An RFP is a low-level unit to test the waters and shape the idea for something viable. Proposals are refined ideas that go through several checkpoints before they are available to be voted on. Proposal processes can be on-and off-chain in nature.<\/p>\n\n\n\n

Each step of the governance process is powered by the HAI token.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Explaining Request-for-Proposal<\/h2>\n\n\n\n

Participation in hDAO starts with obtaining HAI, our governance token. By having some of it in one\u2019s possession, an HAI holder can create Requests-for-Proposal, a document containing suggestions and describing possible changes in how hDAO would operate. Based on Diversity, Equity, and Inclusion principles, each member of the HAI community who has an idea can apply it in the form of an RFP.<\/p>\n\n\n\n

An RFP is needed to ensure that a concept to be transformed into Proposal is fair, efficient, and doesn\u2019t include spam, low-quality, or are-not-aligned with hDAO mission ideas.<\/p>\n\n\n\n

To apply for an RFP, a holder needs to use a template and fill it out to submit his idea for a Committee review.<\/p>\n\n\n\n

\n

As was announced before, by staking a particular amount of HAI, a Member receives an equal amount of Voting Power that enables his right to participate in governance. To enable submission of RFP, it will be required to lock a certain amount of HAI. Such a step helps prevent spam and time wasting and shows a certain level of Member commitment and confidence regarding the effectiveness of the concept he offers to hDAO.<\/em><\/strong><\/p>\n<\/blockquote>\n\n\n\n

<\/p>\n\n\n\n

hDAO Committees<\/h2>\n\n\n\n

Let\u2019s review hDAO Committees in more detail. Committees will be divided by field of expertise and influence. Primarily, they will be based on the most crucial topics that impact our growth. Each Committee will be formed from individuals with expertise in different areas. To become on a Committee, they should be selected by active community members, contribute to the ecosystem, and prove their expertise in needed fields.<\/p>\n\n\n\n

The first step in establishing hDAO will involve forming the Quality Control Committee, which will play a crucial role in initiating the hDAO. The Quality Control Committee will oversee two important steps in Proposal formation, first as RFP and then as fully-fledged Proposals. It will also play a significant role in understanding the structure and forming other Committees, for example, those focused on controlling the work in fields such as Marketing and Business Development, Trust Army Management, Liquidity Management, and more.<\/p>\n\n\n\n

<\/p>\n\n\n\n

Committee Review<\/h2>\n\n\n\n

When an RFP is submitted, it goes through a thorough review process by members of the Quality Control Committee. It assesses the idea\u2019s potential, feasibility, and alignment with the hDAO mission before voting on approval or disapproval of it. That means only the best RFPs make it through to the next stage, which fits into the industry standards of the government process.<\/p>\n\n\n\n

\n

If an RFP is approved by the Committee, an RFP submitter gets back his HAI locked for the submission. In case of a declined RFP \u2014 the locked tokens will be sent to the hDAO Treasury and partially burnt.<\/em><\/strong><\/p>\n<\/blockquote>\n\n\n\n

Only after completing the steps described above, an RFP can be transformed into a Proposal by a Delegate and sent back to the Committee. The latter considers the Proposal, and either sends it back for revision or approves it to be voted on. If the Proposal is approved, a Delegate puts it on to the vote for further decision-making in the form of on-chain or off-chain voting.<\/p>\n\n\n\n

<\/p>\n\n\n\n

Committee and Treasury Budgeting<\/h2>\n\n\n\n

As hDAO continues to take shape, the Hacken core team has finalized the decision regarding the distribution of the remaining HAI Treasury within departments and products.<\/p>\n\n\n\n

For the year 2023, pre-selected budgets have been set for each department as follows:<\/h3>\n\n\n\n