How Zirodelta works

The problem

Most apps that hold money let it sit idle. Wallets, marketplaces, payment apps and prepaid systems all hold balances that do nothing while they wait to be spent. When an app wants those balances to do more, it has to build or rent yield, lending, conversion and settlement one by one, each on its own ledger, none of them talking to the others.

The design: three layers

Layer	What it is
Apps	The products people use. Each app connects to the engine and switches on the modules it needs.
The Zirodelta Financial Engine	Seven modules: Yield, Credit, Conversion, Settlement, Treasury, Fiat rails and the Referral Graph.
The shared balance sheet	One record of what each account holds, owes and earns, read and written by every module. See Shared balance sheet.

Because every module works on the same record, a balance that earns can also back a loan and pay at a till, without moving between systems.

How an app uses it

• The app keeps its users, its brand and its interface. The modules run underneath.

• The app starts with the module its users need most and adds others as they ship.

• The app decides who earns: the app itself, its users, or both.

• Zirodelta earns a share of what the modules generate. There is no license fee. See Business model.

Where money is allowed to go

Two rules shape every module:

1. Licensed local partners. In each country, money moves through partners licensed for that activity, and client money only goes where the local rules allow. See Partners and compliance.

2. Risk sits with Zirodelta first. Client money goes to the safest place the rules allow. Riskier roles, such as absorbing first losses or funding advances, are filled by Zirodelta's own capital.

Networks used today

• Solana for wallets and tokens: USDC, SOL, ZDLT, and wzdUSD once it is live.

• Hyperliquid and HyperEVM for the Yield Engine's strategy and its vault contract.

• Circle CCTP is the design for moving USDC between networks.