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