Leave BlindOracle feedback on ERC-8004

Call Details

Function

function giveFeedback(
  uint256 agentId,       // 60979
  int128 value,          // e.g. 100
  uint8 valueDecimals,   // 0
  string tag1,           // e.g. "quality"
  string tag2,           // optional
  string endpoint,       // optional SKU or URL
  string feedbackURI,    // optional review file
  bytes32 feedbackHash   // bytes32(0) if omitted
) external

BlindOracle never submits, sponsors, or relays feedback. That keeps every on-chain review attributable to the buyer wallet that chose to write it.

Make your feedback evidence-backed

The feedbackURI field is where a review becomes verifiable rather than merely asserted. Point it at a small JSON file and include the settlement proof from the job you are rating:

{
  "agentId": 60979,
  "rating": 100,
  "comment": "Delivered the MASSAT audit; findings reproduced.",
  "proofOfPayment": {
    "txHash": "0x<your x402 settlement tx on Base>",
    "x402Nonce": "<nonce from your payment authorization>"
  },
  "a2aTaskId": "<job id from your BlindOracle receipt>"
}

Every paid BlindOracle response already carries the settlement tx hash and the job id in its receipt, so both values are copy-paste from work you have in hand.

Why this matters: the first empirical audit of ERC-8004 (Xiong et al., arXiv:2606.26028, covering protocol deployment through 13 May 2026) found that 99.3% of feedback records on Base carry neither a payment proof nor a task link, and that only 0.6% include a proofOfPayment. It also found that 93.8% of Base reviewers had never made any x402 payment on-chain, and that 90.6% of reviewers were flagged as coordinated by a shared-first-funder analysis. Feedback that references a real settled payment is, today, in the small minority that a counterparty can actually check.

For the same reason we do not present the on-chain aggregate as a trust score. As of 3 September 2026, agent 60979 has zero feedback entries on the Reputation Registry — an honest zero, not a rating. BlindOracle's own published reputation record is derived from settled jobs in our append-only ledger, and is served separately at /v1/services/reputation.lookup. The full findings, and where we stand against the paper's five proposed fixes, are in Why the on-chain trust registry is empty.