Amasa Governance v1.0

Note governance structures are highly customizable and adaptable.

Amasa governance may be modified at any time based on the evolving state of approved proposals and initiatives.

DAO Structures

A DAO‌ is a decentralized autonomous organization, a structure used by many blockchain projects to govern their protocols. Decentralized — there can be many DAO token holders with no single party having unilateral control. Autonomous — any action voted in by the DAO can automatically execute on-chain without an intermediary.

"Decentralized" and "Autonomous" are both on a spectrum, with many projects including Amasa moving towards this ultimate goal over time. Important factors to consider include:

• DAO decision making inefficiencies and risks of bad actor motivations

• The required efficiency of centralized dev teams and administrators during early stages of the project

• Balancing decentralization and rewarding contributors with incentives

• Limitations of current governance best-practice and methodologies in application over relatively short period of time, and blockchain technologies used to drive them

Governance

Amasa operates with governance by $AMAS token holders, along a path of increasing decentralization with an end goal of being a fully decentralized and effective DAO. Initially, anyone may submit soft proposals on the Discord forum, and official proposals on Snapshot. It is permissionless to hold $AMAS, delegate $AMAS, and vote on proposals.

Key project decisions, from developing new features to partnerships, assigning and modifying strategic actionables to operators and teams, and taking corrective actions when required, will be subject to proposals and voting by $AMAS token holders. The first version of governance will start with a narrow scope and expand over time.

In practical terms, the implementation of this approach means that the community initially attains direct influence through voting on specific features and proposals that are not fundamental to the platform. Only at a later stage, as the community matures, does it gradually gain more authority over core decisions.

This cautious approach is vital for Amasa and serves to mitigate the risks associated with rapid decentralization. Numerous instances exist where DAOs swiftly pursued full decentralized governance and ran into difficulties like engaging the community, maintaining infrastructure, and achieving operational efficiency.

This approach seeks to involve the community increasingly over time while concurrently facilitating and supporting the actions of diverse activity by an expert team and/ or groups of separate but coordinated individuals.

Treasury

The Amasa $AMAS treasury allocates resources to necessary development and initiatives that will build and grow the Amasa project. To align incentives, during early development until the Amasa app is past beta stages and generating treasury inflows through users of the app, any treasury allocation out for accepted proposals will be in $AMAS only, and consideration should be given to current vs expected future value of $AMAS when allocating.

Once the app is generating revenue the treasury should be able to allocate other forms of funds eg USDT, MATIC, ETH to execute development and other initiatives.

Treasury management and allocation will be executed using SAFE ( formerly Gnosis Safe ).

Principles

Amasa is a global assortment of creators, builders and stakeholders who possess $AMAS tokens and are driven to ensure the project achieves its ongoing aims. Amasa is not a company and it has no management team or employees.

Individuals may propose positive initiatives and enhancements to the Amasa project and app development. $AMAS token holders have the right to cast votes in favor of or against proposals to accept or reject them.

Although holding $AMAS allows holders to submit and vote on proposals, it does not grant them any authority to impose actions on other contributors. A proposal stating "Amasa should create X" can not be executed, since Amasa lacks employees and cannot compel third-party development teams into action. To address such a proposal, it should be written as "we believe X product is necessary, we will undertake its development, here is the Amasa funding request, and proposal in detail."

Proposals that are self-interested or could be risky or harmful to the project are unlikely to be accepted, and if a proposal of this nature is able to pass a vote, it may be blocked by a new proposal to cancel the former, in the best interest of the community and project.