Audit-Ready Case File
Last verified (UTC): 2026-03-06T00:00:00Z
Fololo Iris is a standalone proof-of-control product for self-hosted wallet checks. Its buyer-facing outcome is the audit-ready proof-of-control case file: a defensible artifact package that shows what was verified, how it was verified, and which controls protected the result.
What the case file contains
- Challenge payload and verification context.
- Verification method used (
EIP-712,EIP-1271,BIP-322, or policy-approved fallback). - Wallet, network, timestamps, and verification result metadata.
- Evidence integrity details such as file hash and generation metadata.
- Policy-trace fields needed to explain why a method was accepted.
How auditors and reviewers validate it
- Confirm the challenge, wallet, and method line up with the recorded verification result.
- Check timestamps, integrity metadata, and hash-backed evidence details.
- Review whether the selected method matches the customer policy and jurisdiction profile.
- Verify access controls, retention rules, and incident-response handling through the linked trust docs.
Buyer review prompts this answers
| Buyer prompt | Fololo Iris answer | Source |
|---|---|---|
| Evidence integrity | Evidence metadata includes integrity verification details and download history. | API Reference |
| Retention and audit trail | Evidence generation and retrieval are backed by retention and audit workflows. | Overview |
| Access control | Auditor access is scoped and time-bounded; operational access is separated from public API traffic. | Overview |
| Incident response | Buyers can review public support channels and request diligence materials through the security process. | Security |
Limits and non-goals
- Fololo Iris is not a full Travel Rule platform.
- External Travel Rule provider adapters are not implemented in the base product.
- The case file does not replace customer policy review or legal advice for jurisdiction-specific sufficiency questions.
- Fololo Iris does not transmit VASP-to-VASP PII as part of the core proof-of-control workflow.
Public trust sources
Detailed architecture, incident handling, policy, and control-pack materials are distributed through buyer diligence channels instead of the public docs site.
Sample workflow
- Create a challenge.
- Verify proof-of-control by supported method.
- Retrieve evidence metadata.
- Download the case file artifact.
- Hand the artifact to compliance, audit, or procurement reviewers.