Proposals and Voting v1.0

Proposals

For the first stage of governance, the core contributor team will post proposals on Snapshot, aligned with strategic priorities of initial Amasa app versions, for the community of AMAS holders to vote on.

Over time, community members will be able to create soft proposals. Each of these soft proposals will initially have its own discussion channel on a public Amasa channel ( to be created eg Discord / Commonwealth ) as a Community Forum.

The community, including contributors, can discuss and debate soft proposals to determine sentiment before deciding via an informal poll on the Forum, whether a soft proposal should go to full governance vote. If the poll has a positive outcome it will proceed to a governance vote which will take place on the Amasa Snapshot.

Proposals will be classified as "Core" and "Product".

Core Proposals

Core Proposal include changes to the governance process itself and Multisig. These proposals are material to the governance process or major structural changes and as such for the initial stage of governance any Core Proposals made will not go to a full community vote. This will change over time towards full decentralization of core decisions.

Product Proposals

Product proposals include most other changes to the Amasa app, including parameter changes (e.g., changing fee amounts, adding or removing Auto Allocation options ), beneficial code changes, potential partnerships or ecosystem decisions where applicable, and $AMAS treasury allocations to contributors for strategic work.

The Voting Process

The voting process is designed to initiate discussion to gauge sentiment for a proposal,, which can then be implemented upon community approval and voting. Proposals must adhere to the below governance process. Note that this process will change over time to improve and increase decentralization.

Proposal Stages

• AMAS token holders are eligible to submit informal soft proposals to the community forum for discussion and to gauge sentiment through an informal poll.

• For a proposal to be deemed valid to proceed to governance vote it must have a positive poll outcome and be approved by project admins ( as a measure to de-risk from bad actors seeking negative impacts through governance ).

• Soft proposals with a positive poll sentiment will be submitted to Snapshot by an admin wallet on Snapshot, and will adhere to the Proposal Template format to ensure communication of the proposal is clear, and all relevant detail is included.

Voting

• Voting on proposals on Snapshot will be open to all valid AMAS holders, under a voting strategy which gives voting power to holders based on their quantity of tokens held. This weights voting power towards core team and others who have a large vested interest in the project success, with the aim of ensuring proposals have the projects best interests and growth in mind. This will change over time as governance becomes increasingly decentralized.

• Proposals will have voting periods ranging between 24 hours and 120 hours.

• When voting on a proposal, an AMAS token holder's voting power equals the holder's AMAS balance at the blocktime the proposal was submitted, or as specified within the Snapshot voting strategy at the time of proposal submission. Any AMAS acquired after the submission of a proposal cannot be used to vote on the proposal.