daostack / daostack/common

Proposal: Funds Allocation [S13-04]

Open
#1,356 0 comments 0 reactions 1 assignee Claimed by @MeyerPV View on GitHub
feature
Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

**NB!** with questions re design for the task please ask Hanna, Michele or Shai (NOT BRIO)

Funds allocation is the proposal which generate a pay-out procedure, hence funds are taken from the Common Wallet and transferred to a member/s or third party, once or several times.

**Method**

Funds allocation is a proposal made by different decision circles in a common and is voted by the defined circles. The proposer define the amount of funds to be allocated and the goal and the recipient/s and interval of payments.

**Action**

Funds allocation rule is added to the common white-paper rules stays as long as it valid (i.e., once a ‘single’ payment is made the rule is removed from the white paper, but for recurring payments the rule sticks in the WP (white-paper).

**User flow: Create funds allocation proposal (NOTE: there should be a definition for EDIT a funds allocation, not included in this scope):**

Page for Proposal with Funds Allocation type: https://www.figma.com/proto/blLDX3L1CwCIAIHwrghKIQ/Common-Platform?node-id=100%3A8050&scaling=scale-down&page-id=99%3A7036
Pitch page: https://www.figma.com/proto/blLDX3L1CwCIAIHwrghKIQ/Common-Platform?node-id=111%3A7489&scaling=scale-down&page-id=99%3A7036
Discussion page: https://www.figma.com/proto/blLDX3L1CwCIAIHwrghKIQ/Common-Platform?node-id=116%3A7374&scaling=scale-down&page-id=99%3A7036
Page after clicking 'Vote Now': https://www.figma.com/proto/blLDX3L1CwCIAIHwrghKIQ/Common-Platform?node-id=129%3A9193&scaling=scale-down&page-id=99%3A7036 - user can close modal page without any questions (are you sure?). currently it's in this way.

**Button 'Vote Now' should be in the bottom and doesn't scrolled anywhere.**

1. In proposal page: User create a New Proposal
2. User selects “Funds Allocation” proposal from the list
3. Disclaimer: User read instructions describing the goals and means of this proposal and approve (?) including Gov model info
1. quorum
2. Min and max
3. Weight
4. Discussion duration
5. Voting Duration
4. A form is shown to be filled by the user including:
1. Proposal Title
2. Proposal Description
3. Short description of the goal of payment (what do we buy)
4. Funds:
1. Type of Funds (ILS, Dollars, Tokens, etc)
2. Amount
5. Recipient:
1. Type (Member/s, circle/s, 3rd party)
2. Recipient List / Circles / SWIFT
6. Recurring
1. Type
1. Single
2. Recurring
2. Recurring (monthly, weekly, days interval)
7. When
1. Immediately after proposal approval
2. Wait [X] days/hours
3. Wait for trigger (TBD)
8. Upload files (as exist now)
5. User clicks on “Create Proposal” button
6. Review and confirmation window pop ups
7. User review the info and confirms
8. Proposal is added to the system and initiated

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.