Prop 16: Liquidity Council

Type

Spend Proposal

Introduction

This proposal seeks to set up a pool of liquid Community Pool funds, for the purpose of enabling on-chain liquidity, better user experience, and better dapp functionality. The funds requested in this proposal will remain the property of the Archway community and will be strictly utilized to provide liquidity to and for Archway applications. The funds will be controlled via multi-sig and dispersed as directed by the community of ARCH token holders.

The full proposal outline and conversation is available on the Archway forums here: https://gov.archway.io/t/liquidity-council/277

For sites that support links click here for proposal outline

Proposal Details

A multisig is to be set up to manage these community funds. This multisig will be a 3/5 signer, consisting of 3 representatives of Archway core teams and 2 community representatives; each selected by their represented groups. These positions will not be compensated through this proposal.

Spends from this wallet under 250,000 ARCH can be done transparently, and with notice, without additional signaling proposals. Spends from this wallet of over 250,000 ARCH would require a signaling proposal to pass through Archway governance. This enables dApps and protocols launching on Archway to bootstrap some liquidity quickly and without voter fatigue, but ensures community alignment for large deployments of funds such as bootstrapping liquidity with another Layer 1.

Budget Request

5,000,000 ARCH

Voting Options

• By voting yes, you agree with the proposal and would like to see it passed
• By voting no, you disagree with the proposal and would not like to see it passed in its current state
• By voting abstain, you are recognizing this proposal is irrelevant to you and would not want your vote to be counted in either direction
• By voting no with veto, you fundamentally disagree with the proposal and would not like to see it reworked nor revisited