Distributed Finance · SoResFi
A clear account of value.
SoResFi—Sovereign Resilient Finance—is the proposed shared financial design for Skyzai applications: accounts, value flows and inspectable records. It is in development, not an operating financial service.
One financial design, several ways to use it
Me, We and They are entrances into the same system. An individual, an organisation and a connected machine may participate in different capacities; that does not give them interchangeable rights or responsibilities.
SoResFi concerns the financial system around their activity. LIQUID is the exchange application this design supports. Commerce uses exchange for products and services; financial instruments need their own rules.
Accounts, wallets & value flows
An account explains what a party holds, what moved and why. A wallet manages access to assets; it is not itself a bank account, a legal entitlement or proof of ownership of every record it can display.
The design distinguishes everyday payments, trading and saving, including shared-signature arrangements where appropriate. Custody, recovery and who may approve a movement must be explicit for each implementation.
SoResFi also explores ongoing value streams and contribution records. Records should remain traceable and exportable. An event without adequate evidence is unverified for accounting purposes—not erased from history or treated as impossible.
Equity, bonds & instrument rights
The organisational design considers equity and bonds alongside accounts and value flows. Each instrument needs an identified issuer, defined rights and obligations, eligibility, transfer terms and an accountable record.
A token count, a wallet entry or an operating node does not by itself establish those rights. This is a design topic—not issued equity, an available bond or an investment offer.
DAC/DAV nodes & responsibilities
The proposed deployment model pairs participating nodes with DEX instances operated by DACs or DAVs. A node is infrastructure, its operator bears defined responsibilities, and LIQUID is the reusable exchange application. They are not one interchangeable entity.
A shared matching application does not establish an instrument’s rights, custody, eligibility or settlement. Node-wide DEX deployment is a proposed model, not a verified network topology.
The intended DAC/DAV model includes responsibility for its own node. That is not a requirement for every individual holder or trader to operate infrastructure. Explore node participation.
ZAI & SKY
ZAI and SKY have complementary roles under study in the economic design. Their assumptions, boundaries and source records belong to a separate explanation—not an implied offer or access entitlement.
Rights, responsibilities & safeguards
Every financial instrument needs clear rights, risks, eligible participants, custody arrangements and settlement rules. Permission to read context through Nexus does not grant authority to trade or transfer value.
Software may prepare a proposal; the appropriate person or persons authorize consequential actions. Receipts document activity. Independent evidence is still needed to establish its outcome.
The design seeks inspectable accounting and charges tied to actual work rather than captive access. Detailed monetary and fee proposals retain their own source status; this page does not resolve or activate them.
No live account, credit, custody, market, return, redemption, money issuance or settlement capability is offered by this website. The financial design requires further reconciliation, specification and verification. A share of the DAC: voting participation and surplus rights as its charter defines. Node responsibility: The DAC itself operates the financial node that records its own instruments. SoResFi is the financial design beneath LIQUID. Nothing here is an offer, an issuance or live financial instrument — every DAC/DAV runs its own node under its own charter.Pick the instrument. See the rights.
Equity — ownership, with duties.