Coin Brief ENDE

Success is not delivery: Juicebox receipts, BIP-327's vectors and dropsToXrp comparisons

Three of today's items share one pattern: a check that returns "success" while the thing it was supposed to confirm did not happen.

In the Juicebox V6 simulations under Glamsterdam's proposed gas rules, a transaction receipt says the call succeeded while an internal payment - a split, a cross-project payment, a 2.5% fee - failed and was absorbed by a try/catch. The developer's mainnet comparison showed only full failure or full delivery on the same paths; the gap appears only under the new pricing.

In BIP-327, several test vectors passed for the wrong reason. The commit messages for version 1.0.5 explain that one PartialSigVerify vector failed the verification equation even without the range check, so it could not catch code that omitted the check, and that the earlier NonceGen inputs were repeated bytes, which made reversed byte order invisible. The new README requires each vector to name the mistake it detects.

In xrpl.js, dropsToXrp() now returns BigNumber values, and the migration note warns that < compares them as strings: dropsToXrp('9000000') < dropsToXrp('10000000') is false, and TypeScript does not object.

Success is not delivery: Juicebox receipts, BIP-327's vectors and dropsToXrp comparisons
Success is not delivery: Juicebox receipts, BIP-327's vectors and dropsToXrp comparisons — Coin Brief

Why it matters

In each case the fix is the same move: state what the check is supposed to establish and test that directly - delivered payments rather than receipt status, a named bug per vector, numeric comparison methods rather than operators.

Written by Victoria Shinder.