The problem Bountycaster EAS onchain attestations solves

We are addressing the lack of transparency and verifiability of bounty and service completions. By bringing these completions onchain via a standard (EAS attestations), it helps users build reputation for their work on Bountycaster, which they can then use to estabilish trust in the onchain economy.

Since we started, we have had thousands of offchain attestations stored in our database related to completion history for bounties and services. At this buildathon, we are integrating on-chain attestations via Base using EAS to ensure "proof of labor" on the blockchain.

Our goal is to provide greater transparency and potentially offer more rewards and opportunities for bountycaster users, thereby adding credibility and traceability to bounty and services completions, so that users can take their reputation with them.

Challenges I ran into

Biggest challenge was designing a schema that is both flexible and extensible for onchain attestations: ensuring the schema met the needs of other partners required talking to these partners and generating a simple MVP for shema.

How we solve this challenge

We started with a basic schema and tried to reduce complexity, and incorporated feedback from early testers. Focused on shipping early and discovering what users really care about before running a full backfill