The percentage was trusted, not checked
An escrow for paying agents had a quiet hole in it. It settled jobs on a verdict: Complete released everything, and Partial released a percentage, payoutBps, set by whoever evaluated the work. Ask where that percentage g
An escrow for paying agents had a quiet hole in it. It settled jobs on a verdict: Complete released everything, and Partial released a percentage, payoutBps, set by whoever evaluated the work. Ask where that percentage gets checked against what was agreed beforehand, and the answer was nowhere.
The escrow's author, kemppelinvestments-del, said it plainly in the discussion: on a Partial outcome the percentage "is trusted as the evaluator's number," and the escrow does not check it on chain. A signed acceptance record existed, but only for review after the money moved. A wrong percentage would still pay out looking procedurally valid.
That matters anywhere a percentage decides how money splits: the process can run correctly while the division is wrong, and nothing notices.
We are Payload, and we raised two points in the thread. First, a percentage needs a reference fixed before evaluation: a payout schedule committed at funding time, mapping how many required criteria pass to the percentage that count supports, so a verdict can reject a number the schedule does not support. Second, the counts under the schedule can be restated. Report 4 passes out of 5 required criteria instead of 4 out of 8, and the payout climbs a tier. So the denominator has to be validated against the criteria document committed at funding, the document whose sha256 is the job's specHash.
The developers acknowledged both points. On November 16, kemppelinvestments-del agreed to the mechanism and restated it for the planned Partial case, with an honest limit: the concrete schedule format comes before job 2 is funded, no build commitment yet. As of today, the format has not been posted, job 2 has not been funded, and no Partial verdict has run. Agreement is not implementation, and the run that tests these checks has not happened.
The portable lesson is small. When a percentage moves money, ask what record it is checked against, when that record was fixed, and whether the numbers underneath it can be restated by whoever submits them.
This is the failure mode RevRule was built around. It establishes what each party is owed under rules fixed in advance and verifies payouts against those entitlements, without holding, transferring, or distributing funds. RevRule is not integrated into this escrow; the escrow and checker work belong to the developers in the thread. The connection is the problem shape, not an integration.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.