Aiyo's Runtime Decision Point refuses to release the execution-authorization artifact until it has independently verified the settlement on the underlying chain. This page exposes the verifier directly — call verifyTransfer() against any EVM tx, see the verdict, see the reason.
eth_getTransactionReceipt + eth_blockNumber RPC call against the
chain you selected, decodes the receipt's ERC-20 Transfer logs, and checks
(a) status is success, (b) at least N confirmations, (c) at least one Transfer
matches (token, recipient, value ≥ min). If all three hold, verified: true.
Otherwise it throws with the specific reason — shown below as verified: false.
The same code that Aiyo runs against production settlements is what verifies your test transaction here. There is no separate test path, no relaxed validation, no skipped check. If a tx passes here, it would pass the production Runtime Decision Point — and vice versa.
The verifier returns true or throws. It never returns maybe. That's the RDP invariant: same shape as verifySettlement() in production.
