This Epic is for tracking all issues related to the GIV-a-Palooza QF Round.
SUMMARY:

Giver nominations for existing Giveth public goods projects (must have a Base address to qualify)
Endaoment projects invited (from Giveth’s Endaoment integration)
Matching pool: TBD
Matching funds network: BASE
Matching funds currency: USDGLO

TIMELINE:
Announcement: Week of Aug 19
Giver nomination period: Aug 20 - September 3
Endaoment projects Typeform period: Rolling until September 3 (link will only be shared via email)
Round dates: September 3 - 17

GIV-a-Palooza QF Round

Documentation:
https://www.notion.so/giveth/Stellar-Integration-6c49c39365b743c8ae3a7767d5cd0a10

Stellar Integration 

This Epic is based on this spec which basically aims to make it possible to run & navigate mutliple QF rounds at once.

Multiple QF Rounds

As a Project owner, I to let a few trusted team members to add updates & edit the project page, the management of the project page doesn't rely only on me.
Breaking this down:
"As a Project owner": Oscar from ReFi Mexico & Phillip from BrightID
“Wants to”: Share permissions with trusted members of my team.
“So that”: To have a leaner management of the project & let others be able to manage the project if I'm away of the keyboard. As a project owner I don't want to be a blocker for my team. Also I might want to delegate the management without delegating the ownership of the project.

Allow project owners to add project managers. To make the management of the project page easier on large teams

Requirement: GIV stakers should be allowed to delegate their GIVpower to a trusted party.
This is useful for people who do not want to actively participate in boosting projects, but still want to stake and/or lock their GIV. It is also great for projects who can then trust that the people curating projects on Giveth have a more passionate interest in doing the work of curation.
After discussion w/ @GriffGreen & @sembrestels it seems like it might be a good idea to make it possible to choose just one delegate for all GIV governance including:

GIVpower
GIVgarden (Tao Votes)
Snapshot <-- nice to have
Tokenlog <-- nice to have

But the MVP would be for GIVpower.

Delegation (for GIVpower & beyond)

Users usually want to donate over a topic or category instead of specific projects, they don;t have time to make sure what project is. Sometimes they want to select multiple projects and add them to their cart, so they can donate a specific amount to all of these projects.
There are some draft design in Figma, they need to be clarified by the user flow.

Cart of Projects

Current Proposed Implementation from spec:
I would love some review from @KurtMerbeth @aminlatifi
Contract Architecture:
Create a deposit contract that receives GIV tokens and will manage the whitelist of eligible Giveth Pro projects- aliased by their project recipient address. Depositors are also allowed to withdraw their GIV from the contract at any time.
Variables:

owner - address - the contract owner address
depositToken - address - the address of the GIV token or deposit token
priceControllerRole - bytes - contains the role hash for the PRICE_CONTROLLER role
upgradePrice - uint256 - the current price a depositor must deposit in GIV to make a project eligible for Giveth Pro
recipientProject - struct - this is identified of a mapping related to the recipientAddress, holds three variables:

depositAmount - uint256 -  the amount of GIV tokens deposited, this will be the amount returned to the depositor when they withdraw from the contract
depositorAddress - address -  the address of the depositor, this is the address tokens are returned to when calling withdraw - only this address can call the withdraw function for a given recipientProject



Roles:

Owner - The owner/admin of the contract

Can upgrade the contract
Do we want the owner to be able to change the depositorAddress for projects? In case a project owner loses access to their keys.


Price Controller - An address that has permission to call changePrice

Could be a smart contract or automated system at some point in the future



Potential problem
Only allowing one deposit per project could make it so that someone besides the project owner has control of the upgrade status.
Some changes proposed
Perhaps we can take a page out of @griff Green ‘s suggestion of tokenizing giveth PRO eligibility.
If we use a simple ERC-1155 template (mint, burn, transfer) then would it be possible to alias a tokenID (for an NFT) to a projectID on Giveth??
We can create a nested mapping for each tokenID to the depositorAddress (the minter) with a subsequent mapping of the depositPrice which represents the upgradePrice at time of deposit. The NFT owner can burn their NFT and claim their depositPrice for a specific depositorAddress (if msg.sender === depositorAddress) back in GIV tokens
Multiple people can mint an NFT for a given projectID(TokenID) as long as each minter pays the current upgradePrice
we can make a transfer function that will also update the depositorAddress to the recipient of the NFT, effectively transferring ownership of the GIV denominated in depositPrice.
We can then check a given project’s eligibility by querying the balanceOf of a certain tokenID (project ID) - if the balanceOf is > 0 then we can consider at least one person has still deposited tokens on behalf of a given project

Build Contract Architecture

As a project owner, I want to put my campaign in English and in my native language, so that people from my community can truly empathize
Breaking this down:
"As Humberto, the project owner": I want this: https://app.gitbook.com/o/-Ma---yLcdhKqcV6Fq9y/s/xtHkttPdl4nI2JGhUA3s/modulo-1/intro

Screenshot of what you see when clicking the other tab:

“Wants to”: Put my campaign in two languages
“So that”: Empathize with my and the broader community at the same time.
Gitbook has it as tabs. Maybe that could be an easy-to-do approach.

Make Giveth campaign's page multilingual 

This Epic is for tracking the GIV-ARB Ecosystem Accelerator project. This program idea was selected and funded by the ThankARB team in conjunction with the Arbitrum DAO.
Proposal link: TBD
Budget:
5k ARB - Arbitrum address bounties (projects add Arb address)
150k ARB - QF round
7.1k ARB - admin costs
161,000 ARB total
Tentative Schedule:
Phase 1 (June 12 - July 23, 2024)

Onboarding/ARB address bounty phase
5K ARB to distribute to Giveth projects that add an Arb address to their profile
1-2 workshops for the newly onboarded projects who participated on the GIVeconomy & other Giveth features

Phase 2 (July 23 - August 6)

QF round with 150k ARB matching pool
X spaces, marketing support, etc

Phase 3 (August 6 - 27)

Data analysis
Detailed report w/ metrics, KPIs, learnings, etc for ThankARB, ARB forum, Giveth forum
ThankARB conducts KYC for any projects receiving >2k ARB matching

GIV-ARB Ecosystem Accelerator

GIV-Earth QF Round
Start date: June 25
End date: July 9
Up-to-date round details: https://giveth.notion.site/GIV-Earth-Round-42dcbb24ef5d469d86dbcedb154ee7b0
Comms issues: https://www.notion.so/giveth/d43ba90865ae430e982ac2eda39e103e?v=8ece43d3a2db4b6191d1bde4056e1f1a&p=a90d61bc76ed4656899d6330dcd9c649&pm=s

GIV-Earth Round

This epic is to keep track of QF product improvements post June 2024 (so we can finally close the post-launch epic and get more organized)
cc @koday1

Q3 QF improvements

Galactic Giving QF Round

GIVeconomy Improvements

Apigive is a product that can provide access to all Giveth features to the world, so all Third parties and partners can show our projects, make donations, provide us users or rebuild their own UI and bring innovation to our services.
The list of these web services includes:

Get a Client Credential Token (for specific scope)
Refresh Token
View the list of requests made by a client (Third Party Organizations) and the status of the request
Get a List of Projects
Get Detail of a project
Get the list of donations for a project
Get the list of updates in a project
Get All user public information. (3 related webservices)
Create a user ( update it with a user profile)
Make a Donation for a specific project
Create a Project

[P3] Providing Giveth APIs: Apigive 

FYI @laurenluz I transferred all issues here that weren't marked as DONE to this new epic from the old epic.
We can then close the roadmap issue as completed and follow up on your post-launch improvements and fixes here.

Post Launch QF Issues

I think it would be great if we could easily create campaign or causes pages that filter multiple projects on a single page. This would help us stay topical, and raise funds for timely causes.
I would suggest that it would have the following:

A filter that we can add to projects for that cause. For example, "Giving Tuesday", "Syria Earthquake", "ETHBarcelona" etc.
A banner on top along with text (a title and paragraph)
Stats for that campaign / cause on top of the page. For example, $X raised so far from Y projects.