Independent browser verification

Read the permission. Read the payment. Compare.

This file recomputes the permission binding locally, then reads both artifacts from a public XRP Ledger node. No Eterna backend, package, or service participates.

1 Derive locallyWaiting

2 Read ledgerWaiting

3 CompareWaiting

Step 1 · Binding derived in this browser

SHA-256 preimage Press Verify to derive before any ledger read. ASCII, uppercase hex, no trailing newline. SHA-256, output as uppercase hex.

Uppercase digest —

The WebSocket remains closed until both values above have rendered.

Step 2–3 · Declared terms against observed settlement

Metadata schema · waiting Purpose · waiting Transaction type · waiting

Authorization commitment · computed here —

·Pending

InvoiceID · read from ledger —

Holder —

·Pending

Payer · Account —

Destination allowlist —

·Pending

Destination —

Expiry —

·Pending

Settlement time —

Cumulative cap —

·Pending

Current payment only —

Verdict

Required ledger condition · validated === true Pending

Ready to verify.

Four fields and validated finality are checked here. Cumulative authorization requires complete prior-spend evidence.

Verification transcript

No network request has been made.

Decoded ledger data

Permission metadata and payment JSON will appear here after a ledger read.

Scope and limitations

One payment, not completeness

This demonstrates one payment against one permission. It cannot show every payment made against this permission.

No receipt-log claim

It establishes nothing about whether any separate receipt log is complete or honest.

No purpose-truth claim

It establishes nothing about whether the declared purpose was truthful.

Mechanism, not adversarial behavior

In this artifact both accounts are controlled by the same operator. It demonstrates the mechanism, not adversarial behavior.