A checkable record of each agreement
R10.2Is the agreement offered as one record whose bytes match its hash?
- Why it matters
- It ties each payment to exactly what was agreed, so a dispute can be settled on evidence.
- What Lens looks for
- We checked whether your payment requests carry the fingerprint of a record of the agreement. Then we checked the record you serve matches it.
- Where it sits
- Agreement record · Check 1 of 2
- Needed for
- Provable
- Builds on
- Nothing
- Needed by
- The terms inside each agreement R10.3
- Usually fixed by
- CTO · Weeks
What to do
Assemble an agreement record for each transaction and advertise its hash. Tools for this: the @integraledger/lcp package or the Integra appliance.
Agreement record
Is the agreement offered as one record, fixed by its hash, before the buyer commits?
- 1A checkable record of each agreementR10.2
- 2The terms inside each agreementR10.3
- Provable needs all 2
- The agreement inside the payment in Binding builds on The terms inside each agreement.
The definition
- Definition
- A challenge carries an agreement record's hash H and a link L as a pairing places them when the pairing's read returns both, or declares them in its legal context where no pairing serves its options; the pairings' placements are read first.
- Passes when
- A challenge captured by home or payment carries H and L; L is HTTPS; and the hash of the bytes served at L equals H on both fetches of the atr step: the buyer gate passes. Where the agreement record would appear only inside a checkout the probe would have to create (UCP, ACP, AP2), not tested unless the seller has consented.
- Decided by
- A rule
- Evidence
- The challenge; both agreement record responses; the hashes; the pairing
- Steps
- home, payment, atr
- Made as
- anon