Schema registry
Every EAS schema the PRUEBA protocol supports. Each schema is a typed contract deployed to Base mainnet — public, versioned, and forever verifiable. Communities can register a new schema if theirs isn't here.
Community Activity
Records that a community session happened — the foundational schema of the protocol. Used by every active community. Off-chain metadata is pinned to IPFS with the structured payload.
| Field | Type | Required |
|---|---|---|
| entityId | bytes32 | yes |
| activityRef | bytes32 | yes |
| timestamp | uint64 | yes |
| attestedBy | address | yes |
All schemas 8 registered
Records a session — facility, location, type, date, duration, participants, notes, evidence.
A community decision — proposal text, outcome (approved/rejected/deferred), votes for/against, participants.
One member vouches for another. Builds portable reputation without requiring wallets from the recipient.
Coach issues a skill-level certification to an athlete. Discipline, level, valid-until.
Receipt for gear or funding received by a community. Used for grant reporting and impact auditing.
A volunteer logs hours contributed to a community initiative. Aggregable for funding reports.
Records attendance at a community event — one attestation per attendee, with check-in time and event ref.
A community's claim of social impact, with measurable outcome data and reporting period.
Don't see your schema?
Any community can register a new EAS schema through the PRUEBA registry. Define your fields, propose the metadata standard, and onboard your first attestations — all without touching the protocol core.