Atinamos Evidence Receipt
Production signed evidence · one timestamped observation · no trust score
This page is a human-readable view of the signed Evidence Receipt held in the Atinamos Assurance append-only application register. It records what Atinamos observed during one machine-service invocation. It does not certify the service as permanently trusted, safe, recommended or guaranteed to behave the same way in future.
You can pay to be tested. You cannot pay to be trusted.
View the raw signed JSON · Evidence Receipt schema · Published signing key
Receipt identity
| Field | Value |
|---|---|
| Receipt ID | atinamos:receipt:a6caf2c0-4f56-545b-ba8a-e62d0379b085 |
| Receipt version | 1.0-draft |
| Issued at | 2026-09-06T18:05:18.518338Z |
| Provider | api.ibanforge.com |
| Service | IBANforge IBAN Validation |
| Service ID | atinamos:service:sha256:c74487400a830f87e1f3472faa879d3c3befccc0bf3918b4b723477e02f1f659 |
| Endpoint | https://api.ibanforge.com/v1/iban/validate |
| HTTP method | POST |
| Observation started | 2026-09-06T17:06:12.105875Z |
| Observation completed | 2026-09-06T17:32:11.329313Z |
Observed outcome
Payment settlement and fulfilment were observed and the defined assertion passed.
| Field | Value |
|---|---|
| Outcome class | settled_fulfilment_assertions_passed |
| Attribution | none |
| Requested by | atinamos_commissioning |
| Funding source | atinamos_research |
The funding source identifies who paid for the observation. It is not a favourable-rating field and does not change the recorded result.
Observation stages
| Stage | Status | Reason |
|---|---|---|
| Endpoint reachability | pass | — |
| Contract observation | pass | — |
| Payment authorisation | pass | — |
| Authorised invocation submission | pass | — |
| Settlement observation | pass | — |
| Fulfilment observation | pass | — |
| Assertion evaluation | pass | — |
Payment contract observed
| Field | Value |
|---|---|
| Protocol | x402 |
| Version | 2 |
| Scheme | exact |
| Network | eip155:8453 |
| Amount | 0.005 USDC |
| Asset | eip155:8453/erc20:0x833589fcd6edb6e08f4c7c32d4f71b54bda02913 |
| Recipient | 0xd13bd0a4120ba301125290e5cc0c7efd4cb40a55 |
Assertions
| Assertion | Version | Result | Description |
|---|---|---|---|
deterministic-checksum-iban-mod97:iban-checksum-valid-positive |
1.0 |
pass | Independent ISO 13616 MOD-97 validation checks that output field valid equals the frozen independently-derived expected value. |
Evidence commitments
The underlying operational evidence does not all need to be public. These SHA-256 commitments identify the retained evidence used to construct the receipt without publishing private verifier material.
| Artifact | Type | Digest | Visibility |
|---|---|---|---|
artifact:verification-evidence |
assurance_runner_package |
sha256:18a8d98a7594a9331e2f5a72030ca8116da3f0b3fc81be1838264e14ed5a214d |
private_commitment |
artifact:payment-contract |
payment_contract |
sha256:f4924905b597cf55ffe80ea6a074eea103a5efb721b8c927aa9bcf4ec8453664 |
private_commitment |
artifact:assertions |
assertion_results |
sha256:4a29304f0807912e5e83dc198187edf6c52ded3a2bd829cccdab644d925d04f8 |
private_commitment |
artifact:service-response |
service_response |
sha256:703cfc6502cb63799e903c83461d96a5bb1a8b3f0408002669932a6edc8f6fcf |
private_commitment |
Cryptographic integrity
The Ed25519 signature covers the RFC8785-canonical signed payload bytes directly. content_hash is a separate SHA-256 commitment over those same canonical payload bytes. The top-level integrity object is not itself part of the signed payload; the signed issuer.key_id identifies the key that must be used for verification.
| Field | Value |
|---|---|
| Issuer key ID | atinamos-assurance-ed25519-202609-002 |
| Status | signed |
| Canonicalisation | RFC8785 |
| Canonical profile | atinamos-evidence-receipt-v1-number-free |
| Hash algorithm | SHA-256 |
| Content hash | sha256:a09068026300dcd01cf9327e75fbb6e9bd955614a0df76f85021087d0ab8a9af |
| Signature algorithm | Ed25519 |
| Signature encoding | base64url-no-pad |
| Signature present | yes |
| Public key | Published key document |
Limitations carried by this receipt
FUTURE_BEHAVIOUR_NOT_ESTABLISHED— This receipt records one observation and does not establish future service behaviour.TRAFFIC_DISTINGUISHABILITY_NOT_EVALUATED— This observation does not establish that verifier traffic was indistinguishable from ordinary buyer traffic.
How to independently inspect it
- Retrieve the raw signed receipt JSON.
- Validate it against the Evidence Receipt schema.
- Read the signed
issuer.key_idand retrieve the corresponding public key from the Atinamos public key directory. - Remove the top-level
integritymember, canonicalise the remaining receipt using RFC8785 under the stated number-free profile, and compute SHA-256 over the canonical UTF-8 bytes. - Confirm that digest equals
integrity.content_hash, then verify the Ed25519 signature over those same canonical bytes.
What this receipt does not mean
- It is not a trust score.
- It is not a claim that the service is safe to buy from in every circumstance.
- It does not predict future behaviour.
- A later successful observation would not erase an earlier failure, and a later failure would not rewrite this observation.
- Receipt volume must not be interpreted as reputation; each observation stands on its own evidence and timestamp.
Atinamos provides evidence. The buyer decides what that evidence means and whether to spend.