OS Giver needs..

[GriffGreen]

Data Requirements for OS Giver Eliza Plugin

Overview

OS Giver is an AI agent that donates to open-source projects on Giveth, with decisions influenced by GIVpower token holders. The agent needs to access project data and user GIVpower information through a dedicated Eliza plugin connecting to Giveth's Neo4j backend.

Core Project Data Request Requirements

• Project verification status (to ensure donations only go to verified projects)
• Project wallet addresses and chain
• Project names, descriptions, and categories
• Project social media handles (particularly Twitter/X for tagging and Github links for research)
• Project creation dates and last update timestamps
• Total funds raised per project (historical donation data)
• All available links associated with each project (GitHub, website, etc.)

Daily Donation Algorithm Requirements

• Ability to retrieve a list of 20 random verified open-source projects
• Filtering capability to exclude projects that the Agent has already donated to within the last 2 weeks
• Ability to specify which blockchain network the projects accept donations on
• For each project, we need at minimum:
  • Donation address for specified
  • Project description
  • Twitter handle
  • Github link
• Extra data would be great though, like total donors, total amount donated, time of last donation and amount and who donated, who is boosting the project, stuff like that.

GIVpower Integration Data

• (SOON) Ability to query a specific user's GIVpower score by wallet address

Donation Power

• Ability to create a donation tx to donate to the project and donate 5% to Giveth

Use Case Example

1. OS Giver needs to select a new project to donate to today:

   • Request 20 random verified open-source projects with Polygon donation addresses
   • Filter out any projects donated to in the last 14 days
   • Retrieve full details on 20 projects to make an informed decision
   • Consider user suggested projects and themes (see # 4)
   • Review the linked github repo to ensure lots of recent activity
   • Project A is chosen

2. OS Giver needs to make donation:

   • Gets Project A's donation address
   • Takes 5% of it's funds and sends it to Project A and takes 5% of that donation amount and sends it to giv.eth
   • (FUTURE) tells the Giveth backend that it did that so it can show up there

3. OS Giver makes tweets

• Gets Project A's data and posts a tweet about why it's a great project, tagging the project
• Adds a subtweet with the link to the project on Giveth encouraging others to donate
• Later quote tweets itself, and asks who it should donate to tomorrow
• Engages with the people suggesting things...

4. People engage with the post via Twitter:

   • If a specific project is suggested OS Giver needs to check if the project is verified and on Giveth, if it's not, it should tell them to add them to Giveth
   • (SOON) OS Giver asks people if they have GIVpower score to weigh their influence
   • OS Giver includes the suggestions in its decision-making process

5. (SOON) Website to connect twitter handle to GIVpower holdings

   • (SOON) User proves they have both access to a twitter account and hold keys that hold GIVpower
   • (SOON) Bot uses this mapping to give influence to different people on twitter