Confidential · Architecture Documentation
Haven
This material is strictly confidential and intended only for authorised recipients. Enter your email address, the access password, and accept the terms below.

HAVEN — Confidential Architecture Documentation

Non-Disclosure & Confidentiality Terms

Effective upon access · April 2026

1. Acceptance
By checking this box and proceeding, you confirm that you have read, understood, and agree to be bound by these terms in full. These terms are legally binding.

2. Confidential Information
All information contained in or accessible through this presentation, including but not limited to financial data, product architecture, patent filings, technology descriptions, commercial strategies, partnership details, and valuation materials, constitutes confidential and proprietary information of Haven Holding Company LLC-FZ (“Haven”), incorporated in the Meydan Free Zone, Dubai, UAE.

3. Permitted Purpose
You may access this material solely for the purpose of evaluating a potential investment, acquisition, or commercial relationship with Haven. Any other use is strictly prohibited.

4. Non-Disclosure Obligations
You agree that you will not disclose, reproduce, distribute, summarise, copy, or communicate any part of this material to any third party without the prior written consent of Haven. This obligation applies to the existence of this presentation as well as its contents.

5. No Onward Transmission
You will not forward access credentials, share links, or otherwise enable any other person to access this material. Access is personal to you as the intended recipient.

6. Intellectual Property
Nothing in this material grants any licence, right, or interest in Haven’s intellectual property, including its provisional patent applications (USPTO App# 64/032,300 · 64/032,311 · 64/032,324), technology, brand, or trade secrets. All rights are reserved.

7. No Representation or Warranty
This material has been prepared in good faith but does not constitute a prospectus, offering document, or financial promotion. No representation or warranty, express or implied, is made as to the accuracy, completeness, or fairness of the information contained herein. Haven accepts no liability for any loss arising from reliance on this material.

8. Forward-Looking Statements
Certain statements in this presentation are forward-looking and reflect current expectations. Actual outcomes may differ materially. Nothing herein should be construed as a guarantee of future performance, revenue, or valuation.

9. No Offer
This material does not constitute an offer to sell, or a solicitation of an offer to buy, any securities, shares, or financial instruments. Any such offer, if made, will be made only pursuant to definitive documentation.

10. Return or Destruction
If you decide not to proceed with any relationship with Haven, or upon Haven’s written request, you agree to promptly destroy or return all copies of this material and any notes derived from it.

11. Survival
These obligations survive the termination of any discussions or relationship between you and Haven and remain in force indefinitely.

12. Governing Law
These terms are governed by the laws of the Dubai International Financial Centre (DIFC), UAE. Any disputes shall be subject to the exclusive jurisdiction of the DIFC Courts.

Haven Holding Company LLC-FZ · Meydan Free Zone · Dubai, UAE · mj@haven.app

Haven Protocol Stack  /  01 of 03  ·  Haven IP — Engine-Agnostic

Data-Less Continual
Authentication Architecture

A Haven-proprietary protocol that enforces biometric owner verification at each sensitive action, producing a cryptographic proof packet anchored on-chain with every execution. The protocol is engine-agnostic, operates on native device biometric APIs, and creates a permanent public record that the registered owner was verified and present at the exact moment of execution.

Haven IP only.  No third-party SDK dependency  ·  Engine-agnostic boolean input  ·  Execution Proof Packet output  ·  Owner-attributed execution
⚙
Patent Protection  ·  United States Patent & Trademark Office
USPTO Provisional Application  App# 64/032,300  ·  Filed April 7, 2026  ·  Priority date established  ·  Full non-provisional application in progress
Universal Execution Authentication Layer
This protocol is a universal execution authentication layer — built to operate across on-chain, off-chain, enterprise, and regulated environments. Haven produces a verifiable Execution Proof Packet which can be anchored immutably on-chain or retained within controlled environments depending on regulatory, privacy, or enterprise requirements. Deployment context is a platform capability, not a constraint.
●  On-Chain
●  Off-Chain
●  Enterprise Systems
●  Regulated Environments
DocuSign signature packet
•Email address — claimed identity, not verified presence
•IP address — location approximation only
•Timestamp — server-recorded, not device-attested
•Click-to-sign — intent, not biometric presence
•Attached to a document — verifiable via DocuSign servers
vs
Haven authentication proof packet
●Biometric confirmation hash — registered owner physically present
●Device TEE attestation — hardware-bound, unforgeable
●Execution timestamp — device-signed and chain-anchored
●Biometric match — presence verified at execution moment
●Anchored on-chain — verifiable by anyone, permanently
DocuSign proves someone with access to an email address clicked a button.
Haven proves the registered biological owner was physically present and verified at the exact moment of execution.
That is not a better signature — it is a different primitive.
●
Live in the Haven App  —  Core elements of this architecture are already operational within the Haven Wallet (iOS & Google Play). The biometric gate, TEE key signing, and Execution Proof Packet generation are active in the production application today.
Live in the Haven App  —  Core elements of this protocol are already operational in the Haven Wallet (iOS & Google Play). The biometric gate, TEE key signing, and Execution Proof Packet generation are active in production today.
Standard step
Active / processing
Verified / authorised
Failed / blocked
Haven proof packet output
Engine-agnostic input layer
Protocol Execution Flow  ·  Step by Step
⚡
ACTION
INITIATED
Action Initiation Haven-controlled execution path required
The user initiates a transaction, transfer, swap, smart contract interaction, or sensitive operation through the Haven interface. The protocol boundary is here — actions initiated outside the Haven-controlled execution path do not pass through the authentication gate and cannot generate the proof packet that makes the action owner-verified. The action is queued. Nothing executes yet.
Haven-Controlled Path Required External Signing Cannot Generate Proof Action Queued — Not Executed
👁
BIOMETRIC
CAPTURE
Biometric Capture at the point of action, not at login
Haven triggers native biometric authentication precisely when the action is requested. The enrolled reference is stored in the device hardware-secure enclave (TEE). The protocol uses native device biometric APIs and does not require any third-party recognition engine. Any biometric interface that produces a binary match result is a valid input to this protocol.
Engine-Agnostic Input Point of Action — Not Login TEE-Stored Reference No Third-Party SDK Required
Engine-agnostic layer:  The protocol accepts any biometric source that produces a binary match result — iOS Face ID, Android BiometricPrompt, fingerprint sensors, or future modalities. The protocol does not specify or depend on any particular recognition engine. The biometric engine is interchangeable. The gate architecture, the proof packet, and the on-chain record are Haven’s own.
🔒
IDENTITY
MATCH
Biometric Match on-device against TEE-stored reference
The captured biometric is matched against the enrolled reference stored in the device TEE. The match is performed locally on-device. No raw biometric data is transmitted at any point. No biometric data is held by Haven. The output of this step is a single binary result. Recovery from biometric access failure is handled by a separate recovery protocol and is outside the scope of this execution protocol.
On-Device Match Only Zero Biometric Data Transmitted Zero Biometric Data Held by Haven Output: Binary Result Only
VERIFICATION
RESULT?
TRUE — Owner Confirmed
The biometric match confirms the registered owner is present at the moment of action. The protocol proceeds to signing authorisation and proof packet creation.
→ SIGNING PERMITTED
FALSE — Match Failed
The biometric match fails. The action is immediately rejected with no exception path. A failed attempt record is created. No proof packet is generated.
→ ACTION REJECTED
📝
SIGNING
AUTHORISED
Signing Authorised TEE performs signing internally — key never exposed
On TRUE, the protocol authorises access to the hardware-isolated private key held in the device TEE. The key is never exposed — the TEE performs the signing operation internally and returns only the signed transaction output. The protocol simultaneously creates the authenticated proof packet that records this owner-verified execution event.
Hardware TEE Key Signing Key Never Exposed Proof Packet Created
💾
PROOF
PACKET
Owner-Verification Proof Packet Haven-proprietary — attaches to every execution
Haven creates a structured proof packet containing cryptographic evidence of owner-verified execution. The hash is derived from the signed execution event and authentication confirmation signals — not from raw biometric material. This packet is not a log entry. It is a portable, verifiable record that travels permanently with the transaction — anchored on-chain, readable by any party, serving the same commercial function as a DocuSign signature packet but verified against live human presence rather than email access.
Haven-Proprietary Output No Raw Biometric Data Derived from Signed Execution Event Portable — Travels with Transaction Commercial-Grade Proof for Partners
Haven Proof Packet  —  Field Structure
Anchored on-chain  ·  Publicly verifiable  ·  Permanently attached to transaction
Every Haven-executed transaction carries this packet. A commercial partner — exchange, insurer, bank, regulator — can verify at any time that the registered biological owner was present and confirmed at the moment this action executed. Not that a key was used. Not that a password was entered. That the owner was there.
Auth Confirmation Hash
Derived from signed execution event + auth signals
Execution Timestamp
Device-signed & chain-anchored
Device TEE Attestation
Hardware-bound — unforgeable
Liveness Confirmation
TRUE (where applicable)
Receiver Confirmation
Optional — DASR Protocol 02
Raw Biometric Data
NULL — never included
Hash is not derived from biometric material. It is derived from the authentication confirmation signal and the signed execution event.
⓫
EXECUTION
COMPLETE
Owner-Attributed Execution — Execution Proof Packet Delivered on-chain, off-chain, or enterprise
Haven produces a verifiable Execution Proof Packet at the moment of execution — cryptographic proof that the registered owner was biometrically verified, not merely that a key was used. The Packet is anchored immutably on-chain, retained within an enterprise system, or held in a regulated environment depending on deployment context. This is a platform capability built into the protocol — the same proof integrity regardless of where it is stored. This record provides the owner-attributed foundation for Haven’s DASR insurance layer (Protocol 02).
Transaction Broadcast Proof Packet Hash On-Chain Owner-Verified Execution Record Self-Contained — No Haven Access Required to Verify DASR Foundation — Protocol 02
✕
EXECUTION
BLOCKED
Execution Blocked FALSE path — no exception, no fallback
The action is cancelled. No transaction is signed. No proof packet is created. No wallet state changes. A failed attempt record is created, demonstrating that an action was attempted but the owner was not verified at the execution moment. There is no PIN fallback, no password override, no seed phrase bypass, no exception path of any kind. Recovery from biometric access failure is handled under a separate recovery architecture outside this protocol.
No Transaction Signed No Proof Packet Created No Fallback — No Exception Path Failed Attempt Record Created Recovery Handled Under Separate Protocol
Core Protocol Claim — What Haven Invented
“The patentable invention is not biometric recognition — it is the gate architecture and the proof packet. Haven invented the enforcement layer that accepts any binary biometric signal, gates execution through a hardware-isolated signing key, and produces a portable on-chain proof packet that verifiably records owner presence at execution. The biometric engine is interchangeable. The gate, the packet, and the permanent record are Haven’s own.”
Protocol Differentiation  ·  Haven vs Industry Standard
✕  Industry Standard
🔒Key possession proves ownership at signing
🔒Biometric check at login only — session stays open
🔒No public record that the owner was present at execution
🔒Credential or key theft = full wallet access
🔒Transactions uninsurable — no verified owner proof exists
🔒Regulators cannot verify ownership at execution from chain data alone
✓  Haven Protocol 01
●Biometric match confirms owner presence at execution moment
●Verification enforced at each sensitive action — not session-based
●On-chain proof packet records owner-verified execution permanently
●Credential theft useless — no biometric match = no signing, no proof
●Transfers become insurable — proof packet satisfies underwriting requirement
●Regulator-readable owner attribution from chain data, no intermediary needed
⚙ Patent Protection  ·  USPTO App# 64/032,300
Filed April 7, 2026  ·  Priority date established  ·  Full non-provisional application in progress
Haven Holding Company LLC-FZ  ·  Meydan Free Zone, Dubai, UAE
● Live in Production
Core architecture operational in Haven Wallet  ·  iOS & Google Play
Biometric gate  ·  TEE key signing  ·  Execution Proof Packet — active today