# Ratify the Genesis Documentation [Official]

- Space: [Post Tech DAO](https://snapshot.box/s:posttechdao.eth.md)
- Author: 0x23dB246031fd6F4e81B0814E9C1DC0901a18Da2D
- State: Passed
- Voting type: Basic
- Start: 2023-12-21 15:30 UTC
- End: 2023-12-24 15:30 UTC
- Votes: 527
- Open in Snapshot: https://snapshot.box/#/s:posttechdao.eth/proposal/0xe2af76d04d33725d8969b4c46aa8eb833adb3a5e7547800da57b1ead8673c75a

## Results

- For: 9,008,309.56 voting power, 86.5%
- Against: 1,411.91 voting power, 0.0%
- Abstain: 1,409,077.56 voting power, 13.5%

## Proposal

Our genesis documentation was written to be a guiding document in support of, and evolving with, our community. To formally adopt this, the community must vote to ratify it.

The wording is as follows:
Introduction

This document is meant to serve as a starting point from which to build DAO official policies and structural definition. Many items herein are not meant to be permanent, but are the first defaults prior to broader community input. It is expected that over time, this document will evolve to suit the needs of the community and platform, and its administrative execution should be focused on the spirit of the writing, rather than the letter. The main exception to this is the core point that Post.Tech DAO’s purpose for existence is to interface with Post.Tech protocol and the Post.Tech community. The objective of this is to continuously ensure mutually beneficial alignment and perpetuation of the Post.Tech ecosystem.

Mission

Empower Post.Tech DAO in bridging the realms of web2 and web3, pushing boundaries, and fostering long-term dedication within our team. We strive to enhance the Post.Tech platform’s operations by aligning with user needs, identifying market opportunities, devising execution strategies, promoting sustainable development, analyzing competitive landscapes, ensuring community accountability, and researching iterative solutions for continual product enhancement.

Vision

Post.Tech as a ubiquitous content creation and consumption hub, harmonizing with users to disseminate information sovereignly. Our goal is to sustain wealth generation for creators, incentivize high-quality engagement, and provide content creators and curators with a comprehensive suite of empowering products. The ripple effects of a value-positive social experience within this hub will reshape the legacy we leave for future generations across various facets of life.

Values

Equitability, Credible neutrality, Regenerative practices, Duty to protocol, Alignment to community, Preservation of value capture for creators and users, Creating avenues of financial independence, and Adaptability.

Governance Methodology

Voting

Voting in the DAO will be by default open only to vePOST holders. Vote weight is calculated as the amount of post locked, multiplied by the amount of time locked, according to the formula described in the White Paper in section 9.4.3

This method can be updated via DAO vote to reflect the desires of the community, but the choice for this default is believed to create better alignment from users of the protocol and lend extra weight to those who take a longer term view.

The Genesis votes will take 3 days, and will not have the RageQuit deployed.
After the genesis votes, the default window of time for a vote will be 7 days, and then another 3 days for the RageQuit option to be exercised (when functional). This means that votes will last 10 days in total.

Delegating

The ability to delegate your vePOST voting power to another user is a desirable trait, as the community has signaled that Liquid delegated governance is the most desirable option presently available.
Delegation is supported via: Snapshot

RageQuit

To ensure that delegates are accurately representing the desires of those who delegate to them, a RageQuit window is proposed as a way for users to withdraw consent from a vote before it is finalized.

In order to facilitate this, after the standard voting phase is completed, a window of time will be opened to allow users to withdraw their votes from a delegate, and to reallocate to a new delegate, or to self vote. This period is initially set to 72 hours, giving users a short window of time to modify their positions before the vote results become final and binding.

Emergency action

In the event of a critical vulnerability disclosure, or any other time sensitive revelation to the team, the Multisig will be empowered to act without a ratifying vote of governance to mitigate impact and protect User/DAO funds. If such power is exercised, it is expected that an after activity report be published, detailing the actions taken, the precipitating cause, and next steps for the community.

Situations that are potentially applicable to Emergency action powers should have a clear and present danger identified that puts funds, or private data at risk.

If the situation is not time sensitive however, the default expectation is that it will adhere to standard governance processes.

Veto Power

Multisigners have the option to decline to execute on a vote if the vote would cause them to commit a crime, or assume unreasonable risk (either for themselves, or for the community). If a quorum of multisigners is unable to be reached to execute a vote, the proposal will be effectively vetoed.
If the community is not voting for the commission of a crime or other unreasonable risk, and a multisigner declines to ratify resulting in a veto, the community may choose to call for a recall of the multisigner and initiate a special vote to fill the seat for the remainder of the term, as detailed in the Multisig Policy.

Multisig Policy

The purpose of the multisig is to give the community custody of the treasury, and influence over its allocation. Multisigners are beholden to the will of the decisions of vePOST holders and are expected to execute on the will of the DAO.

Qualifications

Holds vePOST NFT and maintains possession of it for their tenure in the role
Nominated by another vePOST NFT holder
Proven engagement in the post.tech community

Responsibilities

Due diligence on all txs to ensure that data matches vote ratification
Timely response to Multisig holder duty including meetings, TX signing and execution, and emergency crisis response
Must inform the DAO if incapable of performing the responsibility of the role as soon as possible so that a special election for a replacement can be held.
Must execute upon the will of the DAO regardless of personal convictions, excluding cases of voting for criminal activity or other issues that cause the multisig holder to assume unreasonable risk.
Participation in the governance process to ensure proper context and proposal considerations are maintained

Multisig Composition (how many members should exist for the multisig, and how they are selected at genesis)

5 of 7 to begin, with 4 seats comprised of Team selected individuals, and 3 selected by community Genesis vote
Team Multisig holders will be:

Lucas: 0x96F3C0eFb3bFfE2C555aB176465ce17De2a2A63C
PT Profile: post.tech

Naomi: 0xBe0A4DBE27EfB450F0D523c595691AEb0A72Feef
PT Profile: post.tech

ZB: 0xb8a97307Cd49C0152dd1673CcdD0c85e8F3bBfA1
PT Profile: post.tech

Above Average Joe: 0x23dB246031fd6F4e81B0814E9C1DC0901a18Da2D
PT Profile: post.tech

Tech Stack

Gnosis SAFE multisig infrastructure will be adopted as default
Snapshot is used for voting formally
Consensus for what goes to snapshot is established on the forum community.post.tech

Member removal and replacement

In the case of dereliction of duty or inappropriate conduct, the DAO can hold an election at any time to remove a multisig member and subsequently hold a special election to fill the empty seat for the remainder of the term of office. A supermajority must be reached in order to enact a removal, and must as part of the process submit a document detailing the reasoning for the vote called.

Member expectations

Demonstrates alignment with the mission vision and values of the community
Adheres to Code of conduct

Multisig compensation

To execute on the will of the DAO requires time to be spent performing due diligence, and on call availability, along with assuming potential liability. These expectations in absence of an incentive to faithfully execute can lead to difficulty finding members willing to assume the role, or corrupting influence caused by the imbalance of value flow.
Value alignment is expected to be of utmost importance for those in high roles, and as such, compensation by default will be in POST.
Total value of compensation, and any additional incentives should be decided by DAO Vote.
Team appointed 4 multisig seats will be ineligible for the compensation for multisigners, as Team allocation is assumed to account for their incentive.

DAO managed parameters

Protocol fee distribution flow

The DAO will have control over the direction of 30% of the protocol fee, with two options, able to be combined in any ratio.

Option A: Protocol fee is distributed to Stakers of vePOST pro rata according to their Post * Lock time weights.

Option B: Protocol fee is accrued to the DAO treasury for ecosystem use.

The default parameter upon TGE and DAO genesis will allocate the entirety of the 30% fee to vePOST Stakers. In order to facilitate a regular conversation around the most efficient allocation of these options for the good of the DAO and Post.Tech platform, a regular review interval should be established to set the distribution ratio. The initial review timeline will be planned as quarterly, but the timeline can be shortened or lengthened with DAO vote to accommodate the emergent optimal review frequency.
To provide an easy to follow cadence for the initiation of review proceedings, the Quarterly review will take place starting at the beginning of January, April, July, and October.

Tokenomics

NAV floor protection buyback strategy

Protocol liquidators are a known group that exists in the industry, and will attempt to dissolve the DAO if at any point token value drops below Native asset value (Non POST assets held by treasury) and they are able to purchase a controlling interest to force the liquidation.

As such, to protect the integrity of the DAO, any time that Non-POST treasury holdings aggregate value approaches a 1.1/1 ratio with the circulating supply of POST, a buyback will be initiated utilizing 5% of the aggregate asset value to buy POST off the market, and supply protocol owned liquidity with the purchase.
This means when the ratio is crossed, 2.5% of aggregate treasury holdings will be spent to market buy post, and the other 2.5% of aggregate treasury holdings will be paired with the purchased post to increase the % of supply in liquidity.

It is the responsibility of the multisig holders to monitor this ratio and execute upon the strategy as detailed above. The default asset used to make these moves will be Eth whenever possible.

Proposal and governance modification protocol/procedure

Overview

Decisions are made through a collaborative, iterative process. vePOST holders can introduce and pass proposals with DAO support. These proposals usually go through cycles of consensus and improvement, growing the support base with each iteration.

General requirements and policy
The process of gaining initial consensus typically begins with discussions and polls between a few people in community hubs like Discord, Telegram, or in the Post.Tech app itself. vePOST holders can introduce a temp check or proposal on the DAO Forum to gather additional support, and may adjust the proposal based on feedback. The proposal may be moved to Snapshot to be voted on by vePOST holders after achieving more than 60% support, as verified by a poll included within the proposal draft latest version. The minimum number of votes for this to be considered valid should be at least 1% of the number of vePOST NFTs in existence at the time of the vote. (Note: the forum will require users to verify holding at least one POST or vePOST to participate. This will be done leveraging unlock protocol’s discourse integration. This feature will not be deployed until after tokens have been minted.)

There are three main sectors of activity for governance decisions to be sorted into, general, working on the DAO, and working for the DAO. Proposals that focus on working on the DAO will change the structure of the org, or its constitution. Proposals that work for the DAO will have specific goals or targets that drive value to the DAO or to the Post.Tech platform. General Proposals do not involve either a request for funding or a change to the Constitution. They include but are not limited to signaling proposals, in-kind partnerships, and co-branding agreements.

All proposals must be posted on the Post.Tech DAO Forum under the appropriate category. To maximize transparency, proposal authors may also respond to comments on the Forum and hold a roundtable at Community Calls to discuss the details.

Forum proposal votes are one vote per user and are not token weighted.

Format

Summary - Summarize the proposal in 1 to 2 sentences.

Statistics - Team working on the proposal, Multisig data, Documentation links, and all other disclosures (Affiliations, For-profit or public good product, Draft version history, Third party funding sources, etc)

Background - Give a background behind the idea. The story about where it came from, what influenced you to create, alignment to the DAO’s mission, etc.

Scope of Work/Proposal/Plan - Give a detailed explanation of the plan to either create, solve, or work on this product. Include commitments to the DAO/ PT platform.

Requirements - Any usage of branding material, social media promotion, or other forms of activity to support the project. (Non-funding requests)

Funding Request - If there is a request needed, state that request here. Along with the funding request, please give a breakdown of how those funds would be used.

Milestones - Discuss your milestones of completing this project. If this is a retroactive proposal, discuss the details of what you’ve done.

Code of Conduct

This Code of Conduct outlines the behavior expectations for members within the Post.Tech community, governing both digital and physical interactions across platforms like Post.Tech, Discord, Telegram, conferences, and any other community spaces. Its purpose is to cultivate a respectful, inclusive, and authentic environment that aligns with Post.Tech’s mission, vision, and values.

Respect and Integrity:

Members are expected to exhibit integrity, trustworthiness, and honesty in all interactions. Those representing the DAO should uphold high standards, especially when under scrutiny.

Contribution and Civility:

Contribute based on your skillset, fostering a positive environment. Maintain civility, reporting provocations rather than engaging with them.

Forum Conduct:

Adhere to general forum best practices, avoiding spamming, shilling, and manipulative behaviors. Refrain from posting copyrighted content, suspicious links, offensive material, or engaging in hate speech.

Community Engagement:

Act in the best interest of the Post.Tech DAO, considering its diverse cultures, ideals, and demographic points. Encourage and support fellow contributors on their journey toward success within the DAO.

Impersonation and Fraud:

Avoid Sybil attacks and any attempt to gain undue advantage in voting or governance. No impersonation of other members under any circumstances. Parody accounts must be clearly labeled to prevent confusion or suspected impersonation. Identity theft, fraud, phishing, doxxing, or activities victimizing users are strictly prohibited.

Malicious Intentions:

Never publish material that is racist, sexually exploitative, threatening, harassing, defamatory, or illegal. Terroristic threats, incitement of violence, activities that put users at risk, sexual harassment or any other sexual misconduct is strictly prohibited.

Enforcement:

Community members negatively impacting the DAO or acting with malicious intent may be removed. Gross misconduct, whether explicit or implied, can lead to potential removal and forfeiture of future tokens. The DAO reserves the right to use any available option to mitigate potential negative impacts.

Conclusion:

Members are encouraged to be their best selves, respecting the diversity within the Post.Tech DAO. This Code of Conduct serves as an educational tool, empowering contributors to interact confidently and positively contribute to the community.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

