CLI

Verify a record

The flagship command. It prints each check, then sets its exit code to the verdict, so it drops straight into a script or a CI step without anything having to parse its output.

$ probatio verify 7xKXtg2CW3cWCLBmVvKcbAkKM6mzTuKMYqM9dAcuLNwr

  PASS  Seals: all 9 fills rehash to exactly the seal recorded with them
  PASS  Membership: every fill proves it belongs to the record, in the order it was made

VERIFIED  7xKXtg2CW3cWCLBmVvKcbAkKM6mzTuKMYqM9dAcuLNwr, 9 fill(s) checked
ROOT      4f2c9a1d8b3e57069c4a1f8d2e6b03571a9c4e8f2d6b0357194c8ea3f7d20b6c1

A record with a fill that was edited after it was sealed fails, and the failing fill is named rather than the whole record:

  FAIL  Seals: 1 of 9 fills do not match their seal
  FAIL  Fill 4: its figures hash to 91c04ae7f2b6…, but 3d8f1c6b0a45… was recorded

NOT VERIFIED  7xKXtg…, fill(s) 4 do not match their seal

verify exits 0 when every fill matches its seal, 1 when one does not, and 2 on a usage error. So a guard is just:

probatio verify "$WALLET" || echo "record did not check out"

Read the record and the standings

The public data behind a trader and a season, no wallet and no signing.

probatio record <wallet>            # name, and the seasons they traded
probatio standings                 # the current ranked season's board
probatio season                    # pot, payouts, and the ruleset-hash check
probatio proof <wallet>            # the raw inputs verify recomputes from, as JSON

Options

A small, shared set of flags.

--season <n>    a specific season ordinal, default the trader's latest   (verify, proof)
--limit <n>     how many standings to return   (standings)
--api <url>     a Probatio instance, default https://probatiotrade.com
--json          print the raw JSON result instead of a summary

--api is how you point the command at your own instance. There is no endpoint flag: verification needs nothing beyond the record itself, so the only network call is fetching it.