Connected value architecture
AlphaStack is the accounting architecture behind the twelve earning channels of ORBITRA ONE™. One value ledger records every result — gains, rewards, fees, costs and losses — as an attribution record tied to settlement evidence. Each channel’s risk stays in its own container, and participation opens only where VaultID eligibility is met. The channels themselves are described on the AlphaStack overview.
How it moves
Transparent streams — trading, maker rewards, liquidity, staking, strategy royalties, bot licensing, data contribution and application commerce — flow toward a central portfolio engine. Each stream keeps its own path until it reaches the engine, where it is recorded with its source and costs before it joins the portfolio total. The streams are illustrative: their size varies, and any of them can reduce the total as well as add to it.
The problem
An active participant rarely has one statement. Trading results sit with a broker, rebates with a venue program, staking rewards in a wallet dashboard, subscription income with a payment processor and referral credits somewhere else. None of them reconcile, and costs are usually reported apart from the income they reduce.
Blended reporting hides two things that matter. It hides the source: a headline yield can mix market gains, incentives and fees paid by the participant themselves. And it hides the coupling: capital that appears to earn in one program may quietly secure risk in another.
AlphaStack answers with accounting rather than promises. Every value event is attributed to one channel, measured net of its costs, backed by settlement evidence and held apart from the risk of every other channel. No channel guarantees a return; outcomes vary and can be negative.
Operating sequence
Six operations take a participant from eligibility to a reconciled statement. The path is the same for all twelve channels, which is what makes their results comparable.
A channel’s eligibility rule is checked against the participant’s VaultID credentials — jurisdiction, verification level or operator role. Without a matching credential, the channel does not accept the commitment.
Capital or capacity committed to a channel moves into that channel’s partition, with its own risk rules, fee logic and published exit terms.
Value events are captured where they originate: fills and maker rewards from ApexMatch, staking epochs from QSE, royalties and licenses from Strategy Forge, job receipts from compute provision, verified submissions from data contribution.
Each event becomes an attribution record carrying its channel, its layer, a reference to its evidence, the gross amount, itemized costs, the net amount and its risk bucket.
A record is marked settled only when it references a transition finalized by QSE. Until then it is shown as an accrual, never as settled value.
The portfolio view aggregates records by channel and by layer, net of costs and including losses. Reconciliation exports read the same records.
Architecture
AlphaStack separates two questions that blended reporting merges: where value came from — the channel — and which part of the system produced it — the layer. Every entry answers both.
An append-only record of value events for each account, partitioned by channel. It is the single source for statements, dashboards and exports.
The unit of accounting. It carries channel, layer, evidence reference, gross amount, itemized costs, net amount, risk bucket and the finality reference of the transition that settled it.
Execution edge is measured as fees and slippage against arrival price; capital edge as margin released by recognized offsets and capital left idle; intelligence edge as results tied to a specific agent or strategy version; economic edge as rewards, royalties and commerce income.
Committed capital sits in a container per channel, with its own loss absorption. A loss in a liquidity vault cannot draw on staked assets unless the owner has explicitly linked them.
Reads VaultID credentials at entry and again at payout. Credentials prove eligibility without exposing the documents behind them, and referral attribution waits until the referred participant qualifies.
Tie each record to its origin — ApexMatch receipts, QSE epochs, Strategy Forge trust records, Cortex action receipts, compute and commerce receipts. Copy-portfolio performance fees are computed from each follower’s own settled records.
Security and failure control
A value ledger is only useful if it cannot flatter its owner. These controls keep the record honest in both directions: it neither inflates gains nor hides costs.
Across the three systems
Orbitra Prime
Trading intelligence
The portfolio view in Orbitra Prime reads the value ledger directly: results appear by channel and by layer, net of costs, beside the positions that produced them. The AlphaStack overview explains each of the twelve channels.
Orbitra L1
Settlement and compute
Orbitra L1 is where the ledger’s evidence originates: QSE certificates settle each record, network staking and validator services are native L1 functions, and maker rewards are computed from ApexMatch execution evidence.
Orbitra Realm
Applications and commerce
Application commerce, data contribution and compute provision originate in Orbitra Realm. Applications built with NexusSDK emit value events in the same attribution schema, so a subscription sold by an app is recorded exactly like a trading result.
Value
Specifications
Terminology