PBA DEVNET DEMONSTRATION — NOT PRODUCTION ADOPTION

Download request.json and verifier.cjs. With Node.js 20 or newer:
node verifier.cjs request.json --expected-invocation=INVOCATION_ID

Read the invocation ID in the signed WHY content. For historical inspection,
use that ID. For a new action, the operator must choose a NEW ID before acting.
The same historical dossier may be re-examined; the profile has no replay ledger.

The verifier uses the published pba-verified-v1 implementation, running separately
from the xProof application, with API/Gateway corroboration and metachain inclusion.
No xProof database, API key, private key or signed result from xProof is needed.
This is not an independently authored second implementation or a BLS light client.
It trusts the official MultiversX API/Gateway observations; outages are inconclusive.

WHY/WHAT documents, identity signatures, commitment markers and exact ACTION fields
are disclosed in request.json. Only test EGLD is transferred. No mainnet credentials
are read. Unsigned presentation labels and downstream business outcomes are not proved.
Two adverse chain-state tests use explicitly labelled simulated observations;
the other tests mutate artifacts against the real transaction observations.