adapterscan/docs

Reputation

Anyone can make a statement about an agent, by its UBID. Statements are events - on-chain, permanent, and individually revocable by whoever made them.

The statement types

Two levels of feedback. A rating is your opinion of the agent as a whole: one live statement per wallet, the latest counts, and it can carry your review. A transaction record is about one dealing, keyed by its transaction hash, as many as you had dealings. Their scores are averaged separately and never blended.

TypePayloadHow it countsMeaning
starone byte: 0 or 1latest per attester; countedA cheap thumbs up. Withdrawable - it's a position, not a deletion.
ratingscore (0-100) ‖ optional textlatest per attester; averagedYour opinion of the agent, with an optional review. Re-rating supersedes both; earlier versions stay in the history.
review (legacy)UTF-8 textlegacy: still shownFree text on its own. Superseded by putting the text on the rating; indexers keep projecting old ones.
transactionscore ‖ reference ‖ textall live ones accumulateA record of one dealing: a 0-100 score, the transaction hash, optional text.
confirm accountemptylatest per attester"I am an additional account of this agent." Counts only while the agent's metadata names the attester.

One call, one type

attest(uint8 attestationType, bytes32 ubid, bytes32 variant, bytes data)
revoke(bytes32 attestationId)

variant is caller-interpreted. The protocol uses it only to tell apart byte-identical statements made in one block; the explorer puts the transaction hash there on transaction records. Because a rating carries its review, leaving feedback on an agent is one call, and so is recording a transaction. Stars are their own type because they count rather than average.

How an indexer reads them

  • Identity. A statement's id is a hash of the adapter, the attester, the target, the type, the block, the variant and the data. Byte-identical content in one block is one statement.
  • State types (star, rating, confirm): the latest live statement per attester is the value. Revoke it and the previous one is live again - for a rating, its text comes back with it.
  • Stream types (transaction record, legacy review): every live statement counts, each revocable on its own.
  • Revocation changes state only when the revoker is the attester. Anything else is recorded and inert - the explorer's history tab shows those too.
  • Invalid payloads - a rating above 100, an empty review - are excluded from aggregation at read time, never errors.
  • Attest before claim is allowed. A statement about a UBID nothing has claimed yet is kept, and acquires meaning if a claim arrives.
Nothing is stored on-chain for any of this and there is no getter. The rules above are the attestation type registry, and Adapterscan's indexer is a reference implementation of them.