The session that produced this was an audit, not a plan. We'd already published 5 threshold circuits and a payment flow. Then we ran it live on Sepolia and found the service could not accept a single payment: the request sent the field `requirements` instead of `paymentRequirements`, and the facilitator answered HTTP 400. Four more bugs surfaced in one afternoon — every predicate was verified against the tx_count key, a predicate that could never be built was advertised as available, and the facilitator once reported success for a transaction that did not exist on chain. That's why the landing page states the testnet and the forgery risk in large type instead of burying them. For a product whose entire value is trust, a hidden limitation is worse than a weak feature. Domain, tunnel and full payment cycle now work end to end: https://rta.lat

ṚTA

Prove a fact without revealing it

Prove a fact without revealing it