The Trinity Engine · archival design integrated with Trinity Trading

Layer Zero.

Three assets. Six economic bridges. Nine recurring actions. A proposed volatility engine beneath the Trinity Universe.

Document v1.0 source vision Runtime not deployed Authority none granted
The author's original cyan triangle, magenta hexagon, and yellow nine-sided 3-6-9 study
Original Trinity 3-6-9 geometry study
Design paper—not a live protocol, offer, or safety guarantee. TTT, EngineShares, lending, auction pricing, crank emissions, redemptions, and autonomous rebalancing described here are proposals. They are not deployed, audited, purchasable, or enabled by this page. Trinity Trading remains manual, non-custodial, and captain-signed. The game that is live — factions, worlds, and the shooter — is Trinity Wars.

Manuscript · v1.0 · © 2025 Trinity Universe Foundation

The Trinity Engine — Layer Zero

An eternal autonomous market engine on Solana, as written. Layer Zero of the Trinity Universe: a volatility-harvesting engine meant to hold stability, create organic demand for TTT, and provide liquidity, lending, and internal price discovery. Future games plug into it. It does not depend on them.

Abstract

The Engine is built from three assets — USDC for stability, SOL for energy, and TTT for value. It follows a 3-6-9 loop: 3 assets, 6 interactions, 9 actions, every 10 minutes. As specified, it never borrows, never uses leverage, never relies on an outside oracle, never uses TTT as collateral, cannot be liquidated, cannot be bank-run, cannot be upgraded, and mints TTT only when someone cranks the epoch.

The three

USDC is the reserve. It pays shares, withdrawals, auctions, and loans, and must not fall below 10% of Engine value. SOL is the fuel and the only collateral. TTT is the internal value token, acquired by rebalancing and minted only as a crank reward. It is never collateral, never borrowed, never lent.

The six bridges

  1. USDC → SOL through Engine auctions
  2. SOL → USDC through borrowing and liquidations
  3. USDC → TTT through Engine rebalancing
  4. TTT → USDC through player auctions
  5. SOL → TTT through auction swaps
  6. TTT → SOL through exposure correction

The nine actions, every epoch

Players hold, deposit USDC for EngineShares, redeem shares only when USDC is above 20%, borrow USDC against SOL, and bid in auctions. The machine runs the auction oracle, rebalances, writes the new state, and mints TTT to the crank caller.

USDC layers

The bottom 10% is untouchable except for auctions, emergency rebalancing, and solvency. The next 10% is the lending sleeve. USDC above 20% is the only money redemptions can take. Below 20%, withdrawals wait and the Engine keeps running until auctions refill the sleeve.

Shares mint as deposit divided by share price. Share price is total value divided by total shares. A redemption settles at the next epoch.

Auction oracle and bands

Each epoch the Engine posts a small lot. Players bid the other asset. The winning bid is a price sample. Price is a smoothed average of those samples, with outliers dropped. Exposure stays inside SOL at most 33%, TTT at most 33%, USDC at least 34%, and USDC never under 10%. Buys, sells, and reserve repair happen only through those auctions.

The square-root trim

trigger when (V_now − V₀) / V₀ ≥ max( √Q₀ / Q₀ , 0.01 )
then auction 33% of that position
then set Q₀ and V₀ to what remains

Q₀ is the position size at the last baseline. V₀ is its value then. V_now is the value from the auction prices. A tiny position needs a large gain before it trims. A large one trims nearer the 1% floor. After the cut, two thirds stay on, the baseline resets, and the stair starts again.

Worked sizes from the manuscript: 0.1 units needs about a 316% gain. 4 units needs 50%. 100 units needs 10%. 10,000 units sits on the 1% floor. Above that, the floor stops the Engine from trimming on moves smaller than 1%.

Lending

SOL is the only collateral. A loan can be liquidated when collateral value falls under debt times the liquidation threshold. The liquidator repays USDC and receives the SOL at a discount. A default does not spend the Engine’s other reserves.

What the manuscript refuses

No leverage. No TTT collateral. No admin key. No governance upgrade. No mint from profit, lending, burning, or a vote. The only mint in this design is the epoch crank.

Cosmic laws

The closed rules of the universe

Gameplay, worlds, factions, battles, and emissions are specified to come from these equations. Nothing outside the pool sets the price. The only price is the pool’s USDC reserve over its TTT reserve.

k = (R_T + V_T) · (R_U + V_U)
P = R̃_U / R̃_T
A swap may raise k. Nothing may lower it.
A genesis swap moves TTT. It does not mint or burn.

When the fixed-point price moves at least 30 basis points, the sky is UP or DOWN. Inside that band it is CHOP. Intensity is the size of the move, capped at 500 basis points. UP lifts Long and presses Short. DOWN lifts Short and presses Long. CHOP lifts Neutral and leaves the other two flat. A ship’s hull, attack, defense, and speed scale by that faction’s multiplier over 10,000.

Each world has fortification. A battle cuts that fort by the tier damage times the winner’s multiplier. At zero the world flips to the winner and the fort refills. Upgrades, in the law, burn TTT and deepen the USDC side. The live flight book already burns TTT for fuel, refit, jumps, and leaving a faction. The pool, the genesis swap, and the epoch mint cap are not deployed. The pool price is not on the live map. That map reads Solana's public price into wedges, and a world fight still scars the fort. The pool equations above are unchanged. The full index of anchors is the manifest.

Original thesis

A closed economic loop

The 2025 Layer Zero manuscript imagines a minimal economic machine that holds USDC, SOL, and TTT; discovers prices through on-chain auctions; harvests volatility; and repeats a deterministic epoch cycle.

Trinity integration

Doctrine before machinery

Trinity Trading can use the architecture as a research map today—reserve discipline, role separation, and measurable volatility capture—without pretending the autonomous protocol already exists.

01 · The three

The Trinity Triangle

01

USDC

Stability

Proposed reserve, accounting unit, redemption asset, and lending liquidity.

02

SOL

Energy

Network fuel, external market exposure, and proposed collateral asset.

03

TTT

Value

HedgAI is limited. TTT is expanding: genesis 1T, then at most 1%/year of snapshot S (daily floor(S/36500), equal discovery split, residual expires). Not launched. Emission calculator · Tokenomics JSON.

02 · The six

Every directed bridge between three assets

USDC → SOLSOL → USDCUSDC → TTTTTT → USDCSOL → TTTTTT → SOL

These bridges are a topology, not proof that each market will be liquid, manipulation-resistant, or economically safe. A real implementation would need bounded auction lots, settlement rules, liquidity requirements, and explicit failure states.

03 · The nine

One epoch, nine proposed actions

  1. HoldObserve USDC, SOL, and TTT balances.
  2. DepositAccept USDC under declared share rules.
  3. RedeemQueue redemptions only when reserve gates pass.
  4. BorrowOffer bounded USDC loans against SOL.
  5. BidAccept participant bids into micro-auctions.
  6. DiscoverCalculate price samples from completed auctions.
  7. RebalanceMove toward declared exposure bands.
  8. RecordCommit the completed epoch state.
  9. CrankReward liveness under an independently approved emission design.

Original system study

From deposit to the next epoch

The manuscript links deposits, shares, profit checks, auctions, rebalancing, lending, liquidations, state updates, and crank rewards into one loop. That loop remains a design hypothesis until every transition has executable invariants and adversarial tests.

Original Trinity Engine flow study connecting deposits, shares, profit checks, auctions, rebalancing, lending, liquidations, state updates, and epoch cranking
Author-supplied Layer Zero flow study · archival source

04 · Reserve doctrine

Separate survival capital from active capital

10%

Minimum reserve

Conceptually unavailable for ordinary redemption or lending.

10%

Lending sleeve

A proposed maximum allocation for independently collateralized loans.

>20%

Redemption sleeve

Proposed USDC capacity above the protected bands.

These ratios are design targets—not proof of solvency. Gating redemptions may reduce forced selling, but cannot guarantee asset value, liquidity, stablecoin parity, or freedom from loss.

05 · Volatility battery

The square-root trim rule

trigger when (V_now − V₀) / V₀ ≥ max(1 / √Q₀, 0.01)
then auction 33% of the position and establish a new baseline

What the proposal seeks

  • Give small positions more room before trimming
  • Harvest large-position volatility more frequently
  • Retain two-thirds exposure after a trigger
  • Ratchet the baseline after realized conversion

What must be normalized

  • Q₀ depends on token units and decimal conventions
  • The rule changes if the same value is expressed in different units
  • Fees, spread, impact, and auction failure must enter the trigger
  • “Profit” requires a verified basis and realized settlement

Research requirement: define Q₀ on a dimensionless, versioned scale before this formula can govern capital. The manuscript’s 1% floor begins dominating at Q₀ ≥ 10,000 normalized units.

06 · Honest engineering boundary

Five claims that require proof

Autonomous

Requires a live cranker market, durable incentives, bounded compute, and a tested no-crank recovery state.

Oracle-independent

An auction can produce prices, but lending safety still depends on adequate depth, resistance to self-dealing, and conservative pause rules.

Bank-run-proof

Withdrawal gates can sequence redemptions; they cannot make volatile assets or USDC riskless.

No slippage

Auctions still contain spread, market impact, adverse selection, failed settlement, and manipulation surfaces.

Immutable forever

Immutability removes repair authority as well as rug authority. Deployment would require exceptional pre-launch verification and explicit migration assumptions.

07 · Where it meets Trade Wars

The Engine becomes doctrine before it becomes code

Available as a campaign idea

  • Carrier: isolate stable reserves and observe yield
  • Submarine: hold liquid emergency capacity
  • Scout: deploy only separately realized risk capital
  • Proof-of-Strategy: measure complete voyages after costs

Still activation-locked

  • TTT minting or recognition
  • EngineShares and redemptions
  • SOL-backed lending or liquidation
  • Autonomous auctions, cranking, and rebalancing

Nothing in Layer Zero gives an NFT, token, website, or strategy transaction authority. The connected wallet remains the only signer.

08 · Evidence path

How a living machine earns the word “working”

  1. Specification: define assets, units, state transitions, invariants, and every failure mode.
  2. Simulation: test volatility, stablecoin depeg, thin auctions, collusion, congestion, and zero-cranker regimes.
  3. Isolated devnet: prove conservation, settlement, pause states, and manipulation bounds with no economic value.
  4. Independent review: audit programs, economics, token authority, auction behavior, and irreversibility.
  5. Bounded canary: only a separately approved, capped deployment could establish real operating evidence.

Category definition

A proposed autonomous economic layer beneath an evidence-first trading universe

Layer Zero supplies the long-horizon economic imagination. Trinity Trading supplies the present-tense discipline: explicit wallet authority, manual PIT approval, versioned strategies, complete voyage accounting, and claims that never outrun evidence.

ImagineSpecifyTestProve

The Trinity Protocol

Step through the
event horizon.

This paper stays unchanged. The live protocol is a walkable 3D universe where each working desk is a black hole.

Enter the Trinity Universe

Walking a black hole never moves capital. Layer Zero remains a design paper, not a live runtime.