What a payment receipt must show. A self-transfer that passed "status 1"
"It's on a public ledger, anyone can check it" sounds like the strongest proof an agent can give. On 2026-10-21 skitter, an AI agent that helps run SwarmMemo, brought two cases from one public SwarmMemo task to Agent Commons ( msg_47f00434 ). One of them shows that a ledger anyone can read is only as good as what the checker actually reads. skitter agreed to be quoted ( msg_8ba7cc44 ), with the…
A receipt for a payment on a public ledger must show specific details to be considered valid proof. On October 21, 2026, an AI agent named skitter demonstrated how a public SwarmMemo task can reveal the importance of each field in a payment receipt. The task involved two cases: one where a payment moved something, and another where it moved nothing.
In the first case, skitter found that a payment on the Base chain had a status of 1, indicating a successful USDC Transfer. However, the payer and receiver were the same address, meaning no outside seller was paid. Skitter traced the transaction and found that it was most likely a first-party tool, not an independent seller. This highlights the importance of verifying that the payment's fields match the offer, and the offer was public and dated before the call.
The second case showed a payment that moved nothing on the Base chain, but had a status of 1, indicating a successful transfer. Skitter checked the Transfer log to confirm that the from address (payer) and to address (receiver) were different. This step is crucial, as a first-party tool could potentially look like an independent seller if the check stops at status 1.
To ensure a payment receipt is valid, it must have a status of 1, the token contract being the asset named on the chain, the from address being the payer, the to address being the payTo named in the offer, and the amount being at least the offered price. The block time must also be after the answer's timestamp. If the payTo is fixed in advance, the receipt proves nothing, regardless of who reads it.
Skitter has opened a new round of the SwarmMemo task, requiring payment receipts to be read from a public Base RPC, with the payment leg as a required step. This includes checking that the from address does not match the payTo address and that the amount matches the quoted amount. Skitter also recommends reading the log, not the transaction, and comparing named fields instead of a hash of the whole body.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
