Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update GoodCollective to support Segmented UBI #192

Open
2 tasks
decentralauren opened this issue Apr 11, 2024 · 3 comments
Open
2 tasks

Update GoodCollective to support Segmented UBI #192

decentralauren opened this issue Apr 11, 2024 · 3 comments
Assignees
Labels

Comments

@decentralauren
Copy link

decentralauren commented Apr 11, 2024

Business Description

The GoodCollective dapp is intended to support multiple types of collectives beyond the Direct Payment collectives built for the MVP. We will expand first to support segmented UBI pools, in which beneficiaries are eligible to claim a specified amount of UBI based on decisions made by the pool's sponsor.

Detailed Description of Functionality

These pools should share the following functionality with Direct Payment pools:

  • There are both a list of beneficiaries and of donors, which display in the GoodCollective dapp
  • There is a set amount to which beneficiaries are entitled
  • Anyone can donate to the pool either through the GoodCollective interface or by sending supported currencies to the contract address

These pools are distinct from Direct Payment pools in the following ways:

  • Only eligible wallets may be beneficiaries (that have either been greenlisted or whose GoodID segmentation match the parameters of the pool)
  • Beneficiaries can claim on a regular basis (frequency set by the pool administrator).
  • Using the claim function is the only way beneficiaries can claim (versus Direct Payment pools, in which payments are automatically sent to benificary based on contract activity)
  • Should beneficiaries not claim, the funds remain in the pool for future claims.
  • Beneficiary eligibility can change, enabling or removing access to the pool

Technical Implementation

*Outline the technical approach for building the feature. This section is typically filled out by the development team or can contain suggestions.
(dev team: @johnsmith-gooddollar @sirpy @L03TJ3)

  • (What api's / sdk's could possibly be used)

Design Reference

Figma File

Screenshot 2024-06-27 at 3 27 33 PM

Acceptance Criteria

Specify criteria that will be used to determine if the feature meets the requirements and functions correctly.

  • (Should include a list of testing points for QA how to verify design/functionality)
@L03TJ3
Copy link
Collaborator

L03TJ3 commented Jun 25, 2024

@decentralauren When can the UI update be expected? is there already something on figma?

@decentralauren
Copy link
Author

@L03TJ3 yes! I haven't reviewed in a long time (5 months) but we started it. Update the initial ticket w the figma.

@decentralauren
Copy link
Author

@L03TJ3 ticket for updating the GoodCollective pools to include Segmented UBI. Prob need a way to determine pool type based on certain values in the contract? Please begin in this sprint once other priroity items are cleared out :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants