The Sovereign Identity Engine

IdentiFI is a Stateless Possession Validation Protocol — a sovereign cryptographic engine that enables operators to prove unified control over a cluster of EVM wallets without exposing private keys, linking addresses on public explorers, or relying on any centralized infrastructure.

The protocol operates entirely in volatile memory. There are no databases, no server-side logs, no persistent metadata. Every session terminates with a full cryptographic purge. What remains is only the off-chain proof of an authorized operation — nothing else.

Built on Rust (compiled to WebAssembly for client-side execution) and natively integrated with Uniswap v4 Hooks, IdentiFI represents a new class of DeFi infrastructure: a privacy-preserving authority layer where validation is sovereign, execution is local, and the chain sees only what it needs to see.

This document is the protocol's technical overview. It describes the system architecture, security guarantees, and economic model at a level intended for engineering review, audit evaluation, and institutional due diligence.

What You'll Find Here

• The Problem — Why current DeFi identity models structurally fail operators.
• Core Architecture — Three-layer execution model with strict isolation guarantees.
• Execution Flow — End-to-end lifecycle of an authorized operation.
• Stateless Reconciliation — How on-chain attribution works without databases.
• Security Model — Cryptographic and architectural guarantees.
• Economic Model — The 33/3 Yield Engine and distribution mechanics.
• SDK & Adapters — Integration surface for third-party dApps.
• Active Deployments — Live contracts on Unichain Sepolia testnet.

The Problem

Current DeFi identity and authorization models operate under a fundamental contradiction: they force operators to choose between functionality and privacy. Every multi-wallet operator exposes their authority surface through public on-chain linkage, centralized KYC registries, or trust-based attestations. There is no third option.

IdentiFI does not patch these problems. It eliminates the architecture that causes them.

Core Architecture

The IdentiFI engine operates on a three-layer execution model. Each layer is isolated by design, ensuring that no single component holds enough state to reconstruct a user's identity or transaction intent. Compromise of one layer is insufficient to authorize an operation.

Layer I — Client-Side Proof Forging

The X-Core Engine is the protocol's computational nucleus. Written in Rust and compiled to WebAssembly, it executes entirely within the user's browser runtime. No on-chain calls are made during proof generation. The engine is sealed — its internal logic is not exposed to the DOM, and side-channel leakage is architecturally prevented by the WASM sandbox.

• Genesis Node — The operator's primary wallet, the root of the identity cluster.
• Strands — Secondary wallets bound to the Genesis Node via individual EIP-191 cryptographic signatures.
• Master Signal — The final blinded authority payload, generated by cryptographically synchronizing all Strand signatures under the Genesis Node's sovereign key.

Layer II — On-Chain Validation (Hook Gatekeeper)

The IdentiFI Hook is deployed as a Uniswap v4 beforeSwap callback. It acts as a stateless gatekeeper: it receives the Master Signal via hookData, validates the cryptographic integrity of the proof, and either authorizes or reverts the operation. The Hook stores nothing. It validates and exits.

The Hook cannot settle trades. The Router cannot validate proofs. This is the Validator-Executor Split — architecturally enforced, not policy-based.

Layer III — Settlement & Treasury

Upon successful validation, the JobberUniversal router settles the trade with maximum gas efficiency. A fixed protocol fee of 0.066% is captured at the settlement layer and routed to the IdentiFITreasury contract for downstream distribution per the 33/3 Yield Engine.

Execution Flow

The end-to-end lifecycle of a single IdentiFI-authorized operation. Every step is deterministic. The outcome is always binary: authorized or reverted.

Stateless Reconciliation Layer

Traditional protocols rely on databases to reconcile transactions and assign data. IdentiFI completely eliminates this dependency through Fractional Value Reconciliation — a deterministic, on-chain assignment mechanism to validate payment and generate the Master signal without needing to expose any wallet involved in the process.

How It Works

The reconciliation mechanism is simple by design: rather than maintaining a separate database that maps user identities to transactions, IdentiFI encodes attribution data directly into the sub-decimal precision of token transfers.

Security Model

IdentiFI's security posture is grounded in engineering discipline, not obscurity. Every guarantee described below is a direct consequence of the system's architectural constraints — not policy, not compliance theater, not marketing copy.

Cryptographic Guarantees

Architectural Guarantees

What We Don't Do

Equally important as what the protocol does is what it explicitly does not do. The following are architectural impossibilities, not policy decisions:

Threat Model Summary

An attacker attempting to compromise an IdentiFI operation would need to simultaneously:

1. Obtain the private key of the Genesis Node (or enough Strands to forge a valid proof).
2. Defeat the WASM sandbox to extract in-memory cryptographic material.
3. Reproduce a valid temporal binding within the active nonce window.
4. Intercept a Master Signal mid-broadcast and replay it within milliseconds — before the next block is mined.

Each of these attacks is independently difficult. Their combination is computationally infeasible under realistic threat models.

Economic Model — The 33/3 Yield Engine

IdentiFI operates on a Pure Utility Economy. There is no native token. There is no speculation vector. Protocol revenue is generated exclusively through usage fees and redistributed to validated participants in real assets — USDC, quarterly, on-chain.

Revenue Streams

The protocol captures value through three primary channels:

The 33/3 Distribution Model

Gross protocol revenue (sum of all three channels) is split according to a deterministic, on-chain distribution model:

Distribution Mechanics

Every aspect of the distribution process is engineered to preserve the protocol's privacy and anti-sybil guarantees:

SDK & Adapter Architecture

IdentiFI is evolving from a Uniswap v4-focused protocol into a Universal Authority Layer. The X-Core Engine remains agnostic to execution destination — its sole function is the cryptographic forge and validation of authority proofs.

Integration Capabilities

Expansion Roadmap

Adapter Modes

The SDK supports two execution modes. The choice depends on whether the target DEX supports Hooks:

Active Deployments

IdentiFI Protocol is fully deployed on the Unichain Sepolia L2 Testnet (Chain ID 1301) with all core components funded and operational. All addresses are independently verifiable on the Unichain Blockscout explorer.

Multi-Chain Strategy

IdentiFI's architecture is designed for horizontal scaling across EVM-compatible networks. The current production target is Unichain Sepolia for the Hookathon incubator evaluation; expansion to Ethereum mainnet, Arbitrum, Base, Optimism, and Polygon is part of the post-launch roadmap.

Each chain deployment is independent and isolated. There is no cross-chain state, no shared session data, no unified identity graph — by design. The cluster proof mechanism works identically on every chain, but the on-chain attribution and yield distribution are scoped per deployment.

Protocol Parameters

The following parameters are enforced at the contract and engine level. They are not configurable at runtime. Any deviation in deployed contracts constitutes a fork and is not endorsed by the IdentiFI engineering team.

System Requirements

Minimum toolchain and runtime requirements for development, integration, and evaluation:

License & Intellectual Property

IdentiFI Protocol is proprietary software. All source code, compiled binaries, cryptographic algorithms, and architectural designs are the exclusive intellectual property of the IdentiFI engineering team.