metadata: {"signature": "0x210510696168f0b01261d726607d2c9ca5f225cf5cbcc6fd0381126723e18ddc1bcc3c714414f2fd3a3eda4063aad72bbb514a7fec1bbe86c56294e97bee0e201b", "application": {"round": "0xedb366e318fc2c94c16852ff2fb99a3f59db8cbb", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "PFel7sk15HfO8zamoPp7TTZf1Ou6Wr5RtaPEdjv0zKoTAA7fod/GS0IU00azwOFr", "encryptedSymmetricKey": "6e928fbe97a937c2661a453198340752561886f2073aa02f82a11f88a5cfb6e74e2e030d372ea8d5c9335f88a8703c10b29cfdd595dcce1b993dd0b5dcabb73b8f704c9ca391375e31c25f29557a146d1a6296b6b52a0f2ae6aeb5bee99147a94ea18c27eaee960dfb1d20289f5cc5da96caa2afd0dac45955d4134aab1b8b6a0000000000000020fa67d87ba4feb95c4019b1f97702a8bb7d1e7e5b5f3dd53f25724e3d5126fa5b5008253ea4a3ea4f356c9da5a41af1ad"}}, {"type": "short-answer", "answer": "None", "hidden": false, "question": "Funding Sources", "questionId": 1}, {"type": "number", "answer": "3", "hidden": false, "question": "Team Size", "questionId": 2}], "project": {"id": "0xde2b7a4d58be78eb82b0e0a5dacd654b68c6e6d15825aff83dfbd792b749342c", "title": "daospace", "logoImg": "bafkreifzewnozjovbc7wljh6332beohx57pczbmdsrsxnk6plizr7qa55i", "metaPtr": {"pointer": "bafkreidujrf7lp7ydtgvazjov5jmn7ln7fei77xrxcz2mb5ulp4uytlbca", "protocol": "undefined"}, "website": "https://github.com/jarisjames/daospace", "bannerImg": "bafkreicjbihgfvufzvyrtss3xjxe27zbrahncawqwrlztwwinul7677osm", "createdAt": 1713298182540, "userGithub": "jarisjames", "credentials": {}, "description": "daospace aims to become an all-in-one coordination tool for DAO contribution. As of today, the space is fragmented; DAO coordination activities occur on Discord, Discourse, Notion/Google Drive, meetings are scheduled via Calendly or LettuceMeet, while the actual meeting occurs on Google Meet or Zoom. daospace will have web3 native features for all these activities, becoming the coordination layer for DAO contribution and DAO collaboration.\n\nThe fragmentation in the DAO space means a contributor must build their reputation up from scratch, every time they join a new DAO, usually via word of mouth or by generally being very popular. This is not ideal for people starting in this space, or for those who are not as outgoing/extroverted as others. We believe that your contributions should be easily verifiable from a single source of truth, owned by the user who made them. Your reputation should be portable everywhere you go. We also use AI to provide clear and concise summaries for proposals shared on forum, to assist voters, so they don't have to experience information overload before voting, while giving them the ability to make an informed decision.\n\ndaospace plans to onboard all the DAO contributors working in web3 currently (over 38,000 in our database), everyone from community managers to developers to podcast hosts. We will also enhance community growth by promoting awareness and participation in DAOs, improving inquiry handling, and reducing bias. The platform will support portable reputation badges, allowing contributors to carry their achievements and contributions across DAOs using their web3 wallet, identified using their ENS name as their identity. This will greatly help DAOs across the ecosystem to discover top talent, recognize contributions, and gamify engagement in a Sybil-resistant manner through a modular web3 resume for DAO members. This will also improve collaboration and networking between DAO participants as they will be able to find people in similar fields or with similar interests.", "lastUpdated": 0, "projectGithub": "jarisjames/daospace", "projectTwitter": "daospace_ai"}, "recipient": "0xcd889cc5f6364f9e5fc9b9a368528acf0353ca5b"}}