Is verification free?

Yes. Anyone who holds a receipt can verify it for free against the public proof JWKS. The paid boundary is the licensed intake, the Accountable Receiving Boundary, that seals receipts for an institution. Verifying an already sealed receipt costs nothing and requires no account.

What happens to my privacy?

Verification transmits only cryptographic material, public keys, hashes, and the receipt's canonical payload. No personal data is transmitted to check a signature. Personal data embedded in receipts is encrypted field by field with separate encryption keys. Once the statutory retention period expires, those keys are destroyed (crypto shredding), while the hash chain stays intact. The verifier sees only what the receipt's author included in the receipt, nothing beyond that.

Are there API calls, is a server contacted?

Yes. Verification fetches the public proof JWKS (the Ed25519 and ML-DSA-65 public keys) and the receipt being checked. Both are read only public endpoints. No write path, no session, no telemetry to the sealing tenant. The JWKS is freely publishable, it contains no secret.

No. Anonymous verification is the explicit design intent, no credential required, because the public keys are public by definition. A verifier needs nothing beyond the receipt and the public JWKS. A login exists only on the institutional side, at the operator that seals receipts, not at the party checking them.

The separation is deliberate: sealing is licensed and accountable. Verification is open and anonymous. One side carries the liability, the other carries the proof.

GLOBAL REGULATORY CONVERGENCE

The world is moving toward execution.

FINMA, BaFin, the EU, NIST, NSA and U.S. government strategies are converging on continuous authorization, Zero Trust, resilience, evidence, accountability and enforceable boundaries. See source by source how immo.quick already unifies these control properties in a deterministic Execution Rights^™ architecture — and where Machine Law^™ goes further.

Open official comparison →How Execution Rights^™ work →

Two systems. Clear architecture boundaries.

The immo.quick Serverless Edition^™ uses no Trusted Execution Environments (TEEs) and no enclaves. TEE and enclave technologies are used exclusively in immo.quick Core^™. The two products are independent systems. Core^™ is not a prerequisite for the Serverless Edition^™.

The Serverless Edition^™ checks defined conditions at the integrated execution path and records the decision in cryptographically verifiable evidence. TEE attestation is not part of its architecture. Hardware-backed isolation and enclave attestation belong to the Core^™ architecture profile.

immo.quick Serverless Edition^™ · immo.quick Core^™

CORE^™ VERIFY · ADVERSARIAL CONFORMANCE

DO NOT BELIEVE THE CLAIM. VERIFY THE EVIDENCE.

Q: Does the Serverless Edition use TEEs or enclaves?

The immo.quick Serverless Edition uses no Trusted Execution Environments (TEEs) and no enclaves. TEE and enclave technologies are used exclusively in immo.quick Core. The two products are independent systems. Core is not a prerequisite for the Serverless Edition.

This surface documents selected internal adversarial conformance results for the tested Core^™ implementation. Test counts are intentionally not inflated into one total because suites have distinct scope and version boundaries.

← Back to Core^™Claim Boundaries →

EVIDENCE PRINCIPLE

Tested implementation. Not external certification.

The verdicts shown here evidence the respective internal suite results within their tested scope.

SELECTED CURRENT SUITES

Report attack classes separately.

70/70Causality Corruption Matrix
CORE_CAUSALITY_CORRUPTION_MATRIX_HOLDS

31/31Cross-Institution Verification
CORE_CROSS_INSTITUTION_VERIFICATION_HOLDS

30/30Multi-Trust-Domain Assurance
CORE_MULTI_TRUST_DOMAIN_ASSURANCE_HOLDS

30/30Institutional Recovery & Continuity
CORE_INSTITUTIONAL_RECOVERY_CONTINUITY_HOLDS

30/30Trust Reassessment & Propagation
CORE_TRUST_REASSESSMENT_PROPAGATION_HOLDS

30/30Institutional Causality Layer
CORE_INSTITUTIONAL_CAUSALITY_LAYER_HOLDS

30/30Counterfactual Compute
CORE_COUNTERFACTUAL_COMPUTE_HOLDS

30/30Continuity Proof
CORE_CONTINUITY_PROOF_HOLDS

20/20Cryptographic Trust Governance
CORE_CRYPTOGRAPHIC_TRUST_GOVERNANCE_HOLDS

20/20Selective Disclosure
CORE_SELECTIVE_DISCLOSURE_HOLDS

20/20Supply Chain Attack Matrix
CORE_SUPPLY_CHAIN_ATTACK_MATRIX_HOLDS

10/10Legal Proof Closure
CORE_LEGAL_PROOF_CLOSURE_HOLDS

Values reflect the latest documented internal suite runs. No third-party certification, no regulatory approval and no claim of absolute invulnerability.

WHAT THE TESTS ARE FOR

Components are not enough. Cross-layer relationships must hold.

System matrices test, among other cases, invalid builds with valid rules, revoked keys with valid proofs, stale trusted time, wrong legal state roots, broken trust paths and causality corruption.

CANONICALIZATION IS PART OF THE SECURITY MODEL.

Proof verification must use the same canonical meaning space bound at creation. Storage or transport fields must not silently alter the semantic hash basis.

CLAIM HYGIENE

What a green verdict does not mean.

PASS ≠ EXTERNAL CERTIFICATION

TEE VERIFIED ≠ LEGAL CORRECTNESS

INTEGRITY VERIFIED ≠ FACTUAL TRUTH

CAUSALLY PROVEN ≠ UNIVERSAL CAUSALITY

VERIFICATION RECEIPT ≠ SUBSTANTIVE ENDORSEMENT

INTERNAL ADVERSARIAL SUITE ≠ INVULNERABILITY

CORE^™ · EXTERNAL ASSESSMENT READINESS

The next evidence class is independent.

After architecture freeze, formal specifications, canonical proof protocol and portable verification, the next maturity step is independent review of architecture, protocol and cryptographic assumptions.

Request technical review →