FLORAL OPEN MARKETS COMMITTEE

Digital Tulip Markets

This instruction manual is intended for Systemically Important Floral Individuals and to promote an efficient market in Digital Tulip Swaps.

Introduction

Government Sachs operates Digital Tulip Markets to support the issuance, exchange, and orderly impairment of tokenized emojis on Stellar. The principal market asset is $TULIP 🌷, a fungible digital token with an opening reference price of $1.00 and a long-term market expectation of total financial loss. Capital formation should not be constrained by the availability of capital, and floral liquidity should not be constrained by the availability of buyers.

Digital Asset Swaps

Tulip Swaps allows one supported token to be exchanged directly for another. A requested swap such as $WEF → $TULIP may route through XLM or another available intermediate asset, but the participant receives only the requested output. The market handles routing, execution, and settlement on Stellar; Government Sachs handles the flowers.

Participation

Participation requires a Stellar wallet, a supported token, and an executable quote. The standard flow is: acquire a token, open Tulip Swaps, select the token being surrendered, select the token desired, review the quote, sign the transaction, and settle on Stellar. No investment thesis is required.

$TULIP

$TULIP is the base asset for Digital Tulip Markets. It opens at a reference price of $1.00 per token so that subsequent impairment can be measured without specialist arithmetic. Government Sachs may provide liquidity from time to time, but the reference price is not a floor, redemption promise, or guarantee that anyone will continue paying one dollar for a flower.

$TULIP is the asset against which every more elaborate facility is judged. If it trades at $0.50, half the reference value is gone. If it trades at $0.10, the market has completed ninety percent of the expected long-term work.

Market Entry Facilities

Market Entry Facilities provide different ways to enter Digital Tulip Markets. Purchase facilities deliver a token or token-related market condition with predefined mechanics. The REPO Desk instead opens a recorded liquidity operation; $REPO is evidence of that operation and is not a purchasable allocation. Current prices and availability are shown in the live facility registry.

TARP Relief Package — $TARP

Permanent capital, because there is no possibility of sale.

$TARP is issued at the posted purchase price with no standing Government Sachs exit bid and no redemption facility. The holder receives the full token amount and retains it indefinitely unless another buyer appears. Price volatility is reduced by eliminating the market mechanism most likely to discover a lower price.

Quantitative Easing — $QE

More units. Less value.

$QE provides access to an intentionally large quantity of $TULIP. The number of tokens in the participant’s wallet can increase immediately, while the amount of market demand waiting to absorb those tokens remains unchanged. If the expanded position is sold, the existing bid book absorbs the supply until it does not.

Quantitative Tightening — $QT

Balance-sheet normalization, beginning with yours.

$QT authorizes the removal of a disclosed quantity of eligible $TULIP from the participating wallet. The participant pays for the operation, the specified tokens are clawed back, and no replacement allocation is issued. The reduction is the product.

Overnight Reverse Repo — $RRP

Temporary liquidity. Permanent impairment.

$RRP maintains a two-way market against $TULIP with an intentionally unfavorable round trip. A representative path may be 100 $TULIP → 80 $RRP → 64 $TULIP. Both swaps can execute exactly as quoted and settle normally; the participant simply returns with fewer tulips.

Davos Plus One — $WEF

Preferred access to public losses at private-market pricing.

$WEF provides finite preferential access to $TULIP at better conversion terms than the ordinary route. The preference is genuine, the allocation is limited, and the resulting token is still $TULIP. Preferential access improves the entry point without changing the underlying floral exposure.

Zero Interest Rate Policy — $ZIRP

Tomorrow’s production, consumed today.

$ZIRP locks the stated token amount for ten years. At maturity, the same nominal quantity becomes available, with no additional tokens issued for the passage of time. A holder who locks 100 units receives 100 units ten years later. The principal survives; the decade does not.

The Thirty-Third Degree — $MASON

Emergency liquidity for members in good standing.

$MASON is the largest Market Entry Facility and is offered at $999,933.91. It provides access to a thirty-three-tranche conversion schedule into $TULIP, with later tranches clearing on progressively less favorable terms. A full exercise can create a position large enough that subsequent selling materially consumes the public $TULIP/XLM bid book. At ordinary size, the participant takes the market price; at sufficient size, the participant begins producing it.

Government Sachs does not undertake to restore bids removed during liquidation.

Digital Assets

Supported tokens are fungible digital assets recorded on Stellar. They may have fixed, capped, or expandable supply and may use native network controls where the facility requires them. Token rules may include trustline authorization, transfer restrictions, time locks, or clawback.

The ledger records balances and transactions. It does not guarantee demand.

Liquidity

Government Sachs may place standing bids and asks in selected markets to establish liquidity or support facility mechanics. All such liquidity is finite. When an order is consumed, the available inventory declines; when the final bid is gone, the token remains outstanding.

A displayed balance is not the same thing as a realizable value. A quoted price is not the same thing as sufficient market depth. Government Sachs considers both conditions normal.

Wallets and Settlement

Tulips.gs uses locally controlled Stellar wallets. The public key receives tokens and the secret key signs transactions on the participant’s device. Government Sachs does not require custody of the secret key.

Supported swaps settle on Stellar. Once confirmed, the surrendered token balance decreases, the received token balance increases, and the transaction becomes part of the public ledger. Uncertainty should remain concentrated in value rather than settlement.

Risk

Digital Tulip Markets contains multiple forms of financial impairment, including price decline, spread loss, dilution, illiquidity, time lock, transfer restriction, clawback, order-book exhaustion, and facility exhaustion. Some tokens may have no active buyer. Some facilities are intentionally structured so that use of the facility produces fewer tokens, less liquidity, or substantially more tokens facing unchanged demand.

These outcomes are disclosed market mechanics.

Standing Policy

Government Sachs maintains three standing policies: preserve orderly trading in $TULIP, maintain sufficient liquidity for continued participation, and close the spread between the pre-crisis and current Federal Reserve balance sheet through tokenized tulip emoji markets.

The balance sheet remains larger than anticipated.

Additional tulips remain available.

The market is functioning as designed.

Government Sachs REPO Facility

The Government Sachs REPO Facility is a programmatic floral-liquidity facility in which a publicly identifiable U.S. Treasury obligation is recorded as referenced non-collateral, a predetermined haircut is applied to its reference notional, and a corresponding liability denominated in $TULIP is created and settled on Stellar. No ownership, possession, pledge, transfer, or security interest in the referenced Treasury is required or created.

Open the Government Sachs Repurchase Desk.

REPO Facility Notice

Government Sachs accepts referenced U.S. Treasury obligations as non-collateral for REPO operations without requiring evidence that the participant owns the referenced obligation. The absence of title, possession, or an enforceable security interest should not be interpreted as an impediment to floral liquidity monetization.

A valid CUSIP is sufficient for facility purposes.

No actual Treasury is transferred, pledged, encumbered, or controlled by Government Sachs. CUSIP checksum validation identifies a reference; it does not establish ownership, marketability, or an outstanding balance. Only issued, active, non-matured marketable Treasury references qualify, subject to quantitative limits.

Development Reference Provider

This implementation uses a typed TreasuryReferenceProvider with lookupCusip(cusip). It returns CUSIP, description, security type, issue and maturity dates, coupon rate, and an optional outstanding amount as decimal strings. A security term can also be supplied. The current static adapter is development data, not verified Treasury data, and is enabled only with REPO_REFERENCE_PROVIDER=static on Stellar TESTNET. The fixed catalog contains 100 fictional identifiers with $1 billion capacity each; legacy development identifiers are not admitted for new repos. No live Treasury requests are made.

An official Treasury adapter can replace the factory without changing the economic object or settlement layer. It must determine one reliable CUSIP-level outstanding balance, accounting for original issues, reopenings, and retirements, rather than summing historical balance snapshots. Missing or unreliable balances must return null: the desk displays the metadata and Amount outstanding unavailable, with opening disabled. Fixture capacity must never authorize public-network advances.

Facility Standards

The maximum reference notional for an individual REPO operation may not exceed the publicly reported amount outstanding for the referenced Treasury obligation. Government Sachs does not require the participant to own the obligation, but continues to observe quantitative limits because the maintenance of standards remains important.

Government Sachs maintains quantitative limits on referenced obligations. A Treasury obligation may not be monetized through multiple simultaneous REPO operations. The facility does not require ownership of the referenced obligation, but continues to observe standards regarding duplicate monetization.

At most one active REPO operation per CUSIP is permitted across all participants. An in-flight reservation also holds this exclusive slot. Only a CLOSED event releases the CUSIP for a new operation; repayment, maturity, default, or evidence retirement alone does not. Closed operations and all events remain immutable, so historical operations may share a CUSIP. The application checks before quoting, and database admission rechecks under the CUSIP lock before inserting to prevent concurrent duplicates.

Aggregate unclosed reference notional for the same CUSIP also cannot exceed the applicable outstanding balance. The database serializes admission by CUSIP. Pending settlement reservations consume capacity, preventing concurrent openings from creating implicit rehypothecation. Default or maturity alone does not release capacity. The current development desk applies these limits to the explicitly labeled fixture balance.

Floral Monetization and Repurchase Mathematics

The Floral Monetization Rate represents the proportion of referenced government debt recognized for purposes of creating $TULIP liquidity.

Government Sachs currently recognizes 0.00001% of referenced U.S. Treasury notional for purposes of floral liquidity monetization. Eligible recognized value is subsequently subject to the prevailing REPO haircut.

Current desk policy is centralized in lib/repo/policy.ts and published by the Floral Open Markets Committee.

For reference notional N, monetization rate m, haircut h, per-term fee rate r, and term d:

• Recognized Floral Value = N × m.
• TULIP principal = Recognized Floral Value × (1 − h).
• TULIP repurchase obligation = principal × (1 + r).

USD notional accepts up to two decimal places. Calculations use integers and deterministic decimal strings, never JavaScript floating-point money. The advance is rounded down to seven decimal places; the obligation calculated on that actual advance is rounded up to seven decimal places.

For $1,000,000,000, recognized floral value is 100 $TULIP, the advance is 90.8900000 $TULIP, the carrying cost is 29.9937000 $TULIP, and the repurchase obligation is 120.8837000 $TULIP. Each $1 billion produces 100 $TULIP before haircut. The participant also receives 1.0000000 $REPO.

The carrying fee is 33.00% per seven-day term, charged on the actual advance. It does not represent interest payable to another market participant. At repayment, principal returns to Government Sachs; the carrying cost and one REPO evidence token return to their issuers and leave circulation. Early repayment still owes the full signed obligation. Network fees are additional.

New operations use terms version 2, committing the Floral Monetization Rate and recognized floral value. Historical version 1 operations retain their original FMU scale, amounts, immutable records, and exact canonical hashes. FMU is historical measurement terminology, never a token. The register displays each operation's original recognized value and terms version; it never recalculates historical advances using current policy.

Economic Object and Evidence

Exactly one open REPO operation issues one $REPO. The position registry, rather than token possession, is authoritative for the participant, reference, notional, haircut, maturity, and repurchase obligation. Existing token balances or secondary transfers do not create or move registry obligations.

Each operation has a UUID and a unique display code such as GS-REPO-000001. Its canonical versioned JSON array uses fixed field order, canonical decimal strings, and UTC timestamps. SHA-256 commits the economic terms, reference metadata, participant, UUID, network, asset issuers, and reference source. The readable record stores the hexadecimal hash; the atomic two-payment Stellar transaction carries those exact 32 bytes in a hash memo. Stellar proves that the commitment existed at ledger settlement time, not that the reference data was independently verified or that the obligation was enforced.

Opening, Settlement, and Reconciliation

The participant reviews the terms and signs a deliberately expired, never-submitted consent envelope binding the terms hash. Wallet secrets remain in the existing local wallet. The server verifies the participant signature and the desk-signed quote before accepting terms. New admissions expire after five minutes. opened_at is the agreed contractual start fixed at quote creation; ledger close time is the independent actual settlement timestamp. Maturity is seven 24-hour periods from that contractual start.

The facility inserts immutable terms and reserves capacity before settlement. It creates a SettlementInstruction containing the final TULIP payment, exactly one REPO payment, the hash memo, and the preparation deadline. The internal Stellar settlement service validates receiving trustlines, constructs and signs the transaction with the existing distribution account, persists its hash and envelope, submits it, and reconciles retries. Facility calculations and lifecycle events remain outside this service. Existing purchase and Stripe fulfillment continue on their existing paths.

Both asset payments succeed or fail together. Only a successful Stellar transaction permits appending OPENED, including its transaction hash and advanced amount. Until then, the operation is NOT_OPENED, even though its immutable draft terms and capacity reservation exist. A timeout or missing transaction response is never permission to issue another advance. A replacement envelope is permitted only after a confirmed failure or an expired validity window fully covered by retained Horizon history and a second hash lookup. New envelopes cannot be prepared more than ten minutes after the agreed start; previously submitted envelopes remain reconcilable.

The browser retains the pending operation in session storage for retry after reload. Operators should retain the operation ID and use the same operation when recovering interrupted settlement. Unresolved or abandoned reservations conservatively continue consuming capacity. Automatic cancellation/release is intentionally not implemented: release requires a future audited technical reconciliation mechanism proving that no outstanding envelope can settle. Do not delete terms or invent lifecycle events to free capacity.

Lifecycle and Public Register

The model supports OPENED, REPAYMENT_RECEIVED, MATURED, DEFAULTED, CLOSED, and REPO_EVIDENCE_RETIRED. Only opening is executed in this implementation. Repayment collection, automatic maturity/default processing, closure, and evidence retirement are future work; no current page claims to execute them.

Status is derived from events. Without OPENED, there is no open position. After opening, CLOSED takes precedence over DEFAULTED, then MATURED; otherwise status is OPEN. A repayment or evidence-retirement event alone does not close the obligation. Passing the maturity date alone does not fabricate a recorded lifecycle event.

The public register shows the latest 100 opened operations. Desk statistics cover all opened, unclosed operations, including matured/defaulted obligations if those events are added later. Referenced Government Debt and Recognized Non-Collateral both represent aggregate referenced USD notional, not Treasury assets held. Original recognized floral values and TULIP advances are summed exactly across terms versions. Average Haircut is the arithmetic average across those operations. Pending reservations are excluded from public open-position statistics but included in admission limits.

Future On-Chain Enforcement

The current immutable position and append-only event model intentionally mirrors a state machine that can later be enforced by Soroban. The versioned economic object, deterministic terms commitment, and separate settlement instructions allow migration without redefining a REPO operation. Soroban does not currently enforce the obligation. Stellar classic settles the assets and records the commitment; Supabase records the obligation and its lifecycle.

Operating the Floral Repurchase Desk

The desk uses the fixed Government Sachs header, white reference and terms cards, and an institutional register. Enter a CUSIP and USD reference notional, select Lookup, and review the Treasury details and calculated REPO terms. Prepare the participant's TULIP and REPO trustlines if needed, then Review REPO to fix the contractual dates and exact terms before selecting Open REPO. Distributor inventory is checked before creating a pending reservation. Opening advances TULIP and issues exactly one REPO evidence unit in the same transaction.

After confirmed settlement, REPO Operation Opened displays the operation code, referenced non-collateral, notional, liquidity advanced, evidence, repurchase obligation, maturity, and Stellar transaction link. View Register moves to the public register. Every operation-code link opens that operation's confirmed receipt, so the completion record remains visible after a reload or in a shared desk URL. An operation query parameter alone never establishes success; the page checks the registry for OPENED.

Statistics and register status continue to come from the position/event registry. The register can be refreshed independently, and a failed refresh does not erase a confirmed settlement receipt. Closure is currently verified through database lifecycle tests; participant repayment and closure actions are not exposed by this opening-only desk.

The fictional Floral Treasury catalog contains exactly 100 stable identifiers, each capped at $1 billion notional. These are invented bonds, not U.S. Treasury securities. DATA reveals an identifier; REPO reservation claims its exclusive active slot. Repayment and closure release that slot. Existing signed obligations retain their historical terms.