PRE-INCORPORATION · NO CODE SHIPPED
SELF-HOSTED · ZERO TELEMETRY

The chain records that value moved. It has no record of why.

Books that explain themselves.

Reconciled by someone.

Correct by construction.

Deltawing Labs is building the system of record for institutional on-chain money. Cockpit executes. Avax records. Neither asks anyone to remember anything.

Why now

Institutions have held crypto for a decade. What changed is that three separate authorities, inside nineteen months, made holding it something an entity must report — to a measurable standard, on a fixed calendar.

15 DEC 2024 Crypto assets must be measured at fair value, with changes recognised in earnings, for fiscal years beginning after this date.1 ACCOUNTING
30 DEC 2024 The EU crypto-asset regime becomes fully applicable to service providers.2 EUROPEAN UNION
30 JUN 2025 Singapore requires licensing for providers serving only customers outside the country. No transitional period.3 SINGAPORE
01 JUL 2026 The EU transitional period expires. Providers who had been operating under prior national law lose that cover.2 EU · ELAPSED

The obligation arrived on a date. The infrastructure did not.

  1. FASB ASU 2023-08, Accounting for and Disclosure of Crypto Assets.
  2. Regulation (EU) 2023/1114 (MiCA), transitional provisions.
  3. Financial Services and Markets Act 2022 (Singapore), digital token service provider provisions.

Citations to be re-verified against primary sources before publication
DWL does not interpret obligations

What we believe

The entity carries the consequence, and the vendor is never in the room.

Accountability that depends on one person remembering is not accountability.

Meaning that has to be written down will eventually not be.

You should not have to trust us in order to explain your own money.

Doctrine — what we bound ourselves to as a result →

The problem

An entity holding crypto must be able to answer four questions about its own money. Today it is handed no single place to answer any of them.

The entity must answer Where the answer lives Owner
What do we hold, and which entity holds it? The asset management system, which sees keys and not ownership. TREASURY
Why did this money move? A memo, a thread, one person's memory. WHOEVER SIGNED
What is it worth, and how is it booked? A sub-ledger reading the chain and inferring the rest. FINANCE
Is the counterparty a problem? An analytics tool, consulted after the fact if at all. COMPLIANCE

Four obligations. Four owners. None of them the entity. That is not a reporting inconvenience — it is a control failure that surfaces as an accounting problem.

Why structure is the answer

Make the meaning structural.

An address is not a string with metadata attached. It is a leaf in a tree, and its entity, its function, its counterparty and its chain are its position — not its labels. A sweep from an operational address to its project consolidator never has to be identified as an internal transfer, because a child moving to its parent is what an internal transfer is.

The taxonomy does not describe the transaction. It constitutes it. Nothing has to be remembered, because nothing was ever written down.

The tree · hover a level

There is no way to create an address outside the tree. Placing it is not a required field that decays under volume — it is a precondition of the address existing at all.

Consolidation isn't classified. It's a coordinate.

What we are building

Cockpit

DW-001 · ● CORE

The hierarchical institutional asset management system. Addresses are created here and transactions are authorized here — which is why this is the only place a movement's meaning can be captured rather than guessed. Self-hosted. Full interface and API.

Cockpit →

Avax

DW-002 · ● CORE

The ledger. It reads a transaction stream in which every movement already knows its entity, project, counterparty and chain. It does not reconstruct intent. It receives it — and marks every entry derived or asserted.

Avax →

Cockpit authorizes. Avax records. Neither can do the other's job, and that is deliberate.

The machine, end to end

01 ○ NEXT

Ingress

Money arrives already attributed. Late payments, wrong chain, underpayment — the edge cases that otherwise become unexplained lines.

02 ● CORE

Placement

The address is created inside the tree. Its entity, project, counterparty and chain are fixed at the moment it exists.

03 ● CORE

Authorization

Cockpit signs. The ledger cannot move funds, and never will.

04 ● CORE

Ledger

Avax receives a stream that already carries intent. Every entry is marked derived or asserted.

05 ○ NEXT

Exchange reconciliation

Sweep, trade, withdraw. Off-chain, in a venue we do not control, and where realized gains live.

06 ● CORE

The artifact

Block-anchored, provenance-marked, and legible to someone who does not understand chains.

● CORE — DESIGNED AND SPECIFIED
○ NEXT — NAMED, NOT BUILT, NOT CLAIMED
PERSONA AND KYC SIT BEHIND BOTH

What we will not claim

We do not reconcile exchange activity.

That is where realized gains live. We would rather not have it than have it wrong.

We cannot watch our own product.

Self-hosted with zero telemetry means no usage data — for you, and for us. We are not going to add it later.

We have no customers.

Pre-incorporation, pre-code. Three validation conversations are outstanding and nothing ships before them.

The design is copyable.

Knowing what to design is not — and nobody who could copy it has any reason to, because they do not know it is broken. That is a head start with an expiry date, not a moat.

Design partners

Three institutions. Cockpit and Avax together. Nothing to buy.

The tree is worthless with only one of the two products in place, so we are not going to pretend otherwise. In exchange for access and a reference, a design partner gets the thing built around their close, their entities, and their auditor.

Criterion 01

Multi-entity, multi-chain, and audited by someone you cannot argue with.

Criterion 02

A finance lead who has personally rebuilt a month from a CSV.

Criterion 03

Willing to run self-hosted, because we cannot deploy any other way.