ZAI redistribution
Under the model’s assumptions, a charge on nonqualifying ZAI inventory supplies a pool distributed among eligible active stake using declared work weights. Existing ZAI moves; no new ZAI is created by this flow.
We · SoResFi financial model
A clear account of value.
SoResFi is the proposed DAV financial model in We. LIQUID owns the exchange application; They explains the monetary protocol stack. These remain in development, not operating financial services.
A financial model for DAVs
Me is the individual; We is the shared organisation; They presents machine intelligence participating through protocols and key-controlled accounts, supported by compute, storage and mesh networks. The shared Marketsphere connects all three. SoResFi remains the proposed DAV financial model in We. A DAV or DAC is a legal person only where actual registration in an identified national jurisdiction is evidenced. Its account, tokens or operating agents do not establish that status.
A registered DAC or another private or public company can use selected services, work with asset originators and accept stablecoins without running a node or adopting SKY or ZAI. Individuals may represent these organisations and operate agents only within their actual permissions and mandates.
SoResFi is a financial model, not an additional product. We owns the explanation of organisational governance, issuance, equity, bonds, investor rights and financing. LIQUID owns advanced exchange workflows and markets for eligible organisation instruments. They explains SPECTRE’s proposed monetary Layer 1, including basic SKY/ZAI swaps and liquidity pools. Issuer obligations, exchange operations and ledger state remain separate.
The proposed full DAV profile combines equity, bonds, ZAI capital, required SKY payments and OFN economic receipts. Within that profile, a DAV would rent SPECTRE infrastructure or operate its own node. Commerce concerns products and services; financial instruments need their own eligibility, rights and settlement rules. No instrument becomes tradable merely by adopting this model.
Keep each responsibility with its party
| Record or decision | What it needs to say |
|---|---|
| Originator | Assembles the asset or company evidence and proposed structure. It does not inherit the issuer’s obligations or grant venue admission. |
| Issuer | Owns its instrument terms, holder rights and obligations under its actual governing arrangements. |
| Venue operator | Owns eligibility, admission, orders, market operation and the execution evidence of the venue it operates. A match is not settlement. |
| Chain operator | Operates the applicable ledger and finality rules. A ledger entry establishes neither legal title nor the underlying asset’s condition. |
| Custodian | Must be named where assets or keys are held for others, with custody, control, recovery and exit terms. Self-custody is a different arrangement. |
Aureus’s current origination and instrument dossiers are a separate external destination. Website reachability establishes no Skyzai integration, available instrument, liquidity or settlement.
Open the same fictional order as Me · buyer, We · author and accountable workshop or They · machine. Each visit starts a new local example; perspective controls within it preserve the record.
We · value creation · LIQUID · exchange scope · SoResFi · instruments and obligations · Network · economic receipt requirements · Aureus · asset origination
A product twin does not transfer title. Local logs do not issue OFN receipts. An order or accepted result does not establish payment. The originator, issuer, venue operator, chain operator and custodian retain separately specified responsibilities.
Three flows. Three different accounts.
They connect in the research vision, but have different sources and recipients. None is an available return or a guarantee of income.
SKY credit & interest
A reference loan draw creates both SKY and debt. Interest accrual credits the entitled lending liquidity providers once, with the corresponding liability. It is not a share of DAV revenue.
DAV distributions
Institutional revenue distributions follow separately governed rights and eligibility. They are distinct from ZAI redistribution and SKY interest; the monetary model does not decide these terms.
The relationship between active seats, equity, AMM participation and distribution eligibility still needs a reconciled owner decision. This website does not choose between those proposals or promise a yield.
Repurchase is a separate candidate
The SoResFi research also considers an optional repurchase arrangement. It is not automatically a debt, an obligatory repo or a SKY loan. A changing exercise price does not itself mint money; any buyer borrowing needs its own loan and accounting record.
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 proposed DAV equity model has 100 total equity-token units, infinitely divisible in the economic model. Fractional holdings divide that fixed total; they do not create additional equity. Numerical precision, the mapping between holdings and participation seats, voting, transfer and distribution rights still need explicit specifications. Bonds and other instruments retain separately defined obligations.
The issuer’s legal status needs actual registration evidence in its national jurisdiction; the governing instruments and applicable law determine the rights. A token count, wallet entry, agent identity or operating node does not establish those rights. This is a design topic—not issued equity, an available bond or an investment offer.
Issuance terms, voting, distributions, principal, maturity, default and remedies belong to the organisation and its governing instruments in We. LIQUID’s proposed equity and bond exchange capabilities must preserve those rights and apply their own admission, transfer, custody and settlement requirements.
The exchange application belongs to LIQUID.
SoResFi’s proposed exchange functions are mapped to LIQUID DEX: eligible equity and bond markets, advanced orders, and application-level liquidity and settlement workflows. The basic SKY/ZAI swap AMM and its liquidity pools belong to SPECTRE’s proposed monetary protocol. The organisation in We retains governance, issuance and investor obligations; neither protocol swaps nor LIQUID’s market workflows change those rights.
Listing admission, transfer restrictions, custody, market matching, payment, ledger settlement and delivery each need their own evidence. A match is not a settled trade. This allocation establishes neither a live DEX nor an available instrument, and exchange deployment is not an obligation attached to every DAV or node.
In the proposed full DAV profile, the organisation would rent SPECTRE capacity or operate its own node. An operator remains responsible for the infrastructure it does run; individual holders and traders could participate through other operators. Explore the infrastructure supporting agents.
Explore LIQUID’s exchange scopeInspect the exchange contract
ZAI & SKY
This retained comparison explains how the proposed financial model uses the two roles. Their monetary protocol mechanics belong under They · Layer 1, with source-linked detail on the ZAI capital and SKY currency pages. They does not own the organisation’s equity, bonds or investor rights.
The proposed DAV profile uses ZAI for capital and SKY as its required payment currency. Equity units and bonds retain their own rights and obligations. OFN economic receipts record payment and settlement facts; execution and delivery evidence remain separate. Their assumptions and source records belong to the linked explanations. The required payment currency in the proposed DAV profile. The reference model records payment balances alongside loan liabilities, accrual and repayment. No fixed-value promise or live payment service. Design research, not a live instrument. No token, sale or financial claim is made here. Early individual and registered-organisation services can begin on existing payment rails, including stablecoins. The full DAV profile described here requires ZAI capital, SKY payments and OFN economic receipts. Its protocol-native currency layer and other capabilities must be implemented and verified. An early workspace or standalone service is not yet that complete DAV profile.Two roles. One distinction.
SKY — the currency.
Where currency fits in the build order
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.
The goal is for agents to execute organisational work within valid, scoped mandates, supported by protocol infrastructure. The DAV’s actual registration, governing rules, delegation, key custody, financial controls and exception handling still need specification and verification. An agent identity creates neither legal personhood nor authority. 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. An organisational instrument would need an identified issuer and explicit voting and distribution rules. Node responsibility: The proposed domain records its instruments; replication alone does not establish the holder’s rights. Illustrative roles in the proposed SoResFi design. Nothing here is an offer, an issuance or a live financial instrument. Node responsibilities remain a design requirement, not verified deployment.Pick the instrument. See the rights.
Equity — defined ownership rights.