ROUNDUSK Capital, engineered.

ROUNDUSK is an on-chain ecosystem on Solana that connects token creation, paired markets and a fee-funded trading vault. Trading activity keeps a continuing role in the ecosystem: collected fee rewards support creators, fund vault positions, contribute to the treasury and finance buybacks and burns of the ROUNDUSK protocol token.

Paired launch, lock, bridge and swap form the user experience. The fee engine connects that experience to the protocol's economic model:

• Launch: create tokens and establish their paired markets.
• Lock: lock supported tokens or liquidity positions under defined terms.
• Bridge: move assets between supported networks.
• Swap: exchange supported assets.

The trading-fee model applies to the fee rewards collected from tokens launched through ROUNDUSK. Lock, bridge and swap do not generate that fee stream, and ROUNDUSK charges no fee of its own on them.

The ROUNDUSK token

Until the token launches, the buyback and burn allocation accumulates in SOL in the buyback wallet, recorded in the ledger as funds awaiting execution. When the token is created, its mint address is set once on the admin page. From then on the keeper spends the accumulated funds buying ROUNDUSK and burns every token it buys.

Paired launch

A paired launch creates a token and its market in one Solana transaction, on Meteora's Dynamic Bonding Curve. Creators pick what the token trades against:

• Token / token: quoted in SOL or USDC.
• Asset / token: quoted in a supported tokenized stock (xStocks such as TSLAx, NVDAx, SPYx, AAPLx). Buyers can still pay with SOL: Jupiter swaps it to the stock token in the same transaction.

Supported pairs: SOL, USDC, SPYx, CRCLx, QQQx, NVDAx, SPCXx, TSLAx, MSTRx, COINx, GLDx, AAPLx, HOODx, GOOGLx, AMZNx, METAx, MSFTx, PLTRx, AVGOx, MCDx.

Migration

When a bonding curve fills, the market migrates to a Meteora DAMM v2 pool. That pool's liquidity is permanently locked: half of the position belongs to the creator and half to the protocol, both locked forever, both earning the pool's fees.

The fee engine

When people trade tokens launched through ROUNDUSK, the fee rewards received by the engine are allocated across four destinations:

These percentages describe the allocation of collected fee rewards. They do not specify the trading fee charged on the transaction itself (see Paired launch). Collected fee rewards are the pool's trading fees minus Meteora's own protocol share. Each pool splits them 50 / 50 between the creator and the protocol; the keeper claims the protocol half, converts it to SOL through Jupiter when the pool trades against another asset, and splits it 60 / 20 / 20 between vault, treasury and buyback, which is 30 / 10 / 10 of the whole. Every harvest is recorded with its transaction.

The 60 / 20 / 20 split is enforced on-chain by the ROUNDUSK engine program: the keeper hands it the harvested amount and the program pays exactly 3/5 to the vault, 1/5 to the treasury and the rest to buyback, to the wallets stored in its state, and keeps running totals anyone can read (see Programs and wallets).

The trading vault

The vault uses its 30% allocation to fund equity-derivative positions: perpetual futures linked to supported stocks and to the S&P 500, on Pacifica, a perpetuals exchange on Solana. Vault capital is exposed to the outcome of those positions. Positions may produce a profit or a loss, and leveraged positions may be liquidated.

Unrealized price gains do not create claimable rewards. The vault page shows live positions from Pacifica and every closed position with its realized result.

Realized profit allocation

Distributable profit is the realized profit after trading costs, funding charges and settlement costs. ROUNDUSK allocates it equally:

The treasury receives no share of vault profit. The principal remains available to the vault; only distributable profit enters this split.

The split runs through the ROUNDUSK engine program (RouteProfit): half goes to the engine reward pool, a program account nobody holds a key to, and the rest to the buyback wallet.

Creator rewards

Creators have two reward sources, shown separately on the profile page:

1. Fee Rewards: their 50% allocation of collected fee rewards. It accrues in their token's pool and they claim it from the pool with their wallet. For tokens quoted in another asset, the claim can swap it to SOL in the same transaction.
2. Vault Profit Rewards: their share of the creators' 50% of distributable vault profit. Each settlement is allocated across tokens pro rata to what each token's fee rewards contributed to the vault, and each token's allocation belongs to its creator. It becomes claimable after the profit is realized, settled and allocated. The keeper writes each creator's cumulative total to their on-chain record in the engine program, and the creator claims it from the engine reward pool by signing one transaction with their own wallet. Nobody else can claim it, and claims keep working even while the engine is paused.

These allocations belong to the eligible token creator: the wallet that launched the token. Holding a launched token does not establish eligibility for the creator's rewards.

Buyback and burn

ROUNDUSK buybacks have two funding sources: 10% of collected fee rewards and 50% of distributable vault profit. The allocated funds purchase the ROUNDUSK protocol token, and the acquired tokens are burned.

Funding an allocation and completing a buyback are separate events. Token availability, liquidity, execution conditions and transaction completion determine when a funded buyback can occur. The fee engine page shows funds awaiting execution separately from completed purchases and burns, each burn with its transaction.

• Route: the token's own bonding curve while it has one, then its DAMM v2 pool (or a pool pinned by the admin), else Jupiter.
• Execution controls: each buyback is sized so its price impact stays under 3%, at most 5 SOL per pass, and a pass is skipped when the price jumped more than 20% since the previous pass.
• Buybacks and burns do not guarantee a higher token price.

Treasury

The treasury wallet receives its 10% of collected fee rewards. It receives no share of vault profit. Its balance and every inflow are public on the fee engine page.

Lock

Token locks use Jupiter Lock (program LocpQgucEQHbqNABEYvBvwoxCPsSbG91A1QaQhQQqjn, open source, audited by OtterSec and Sec3). A lock moves tokens into an on-chain escrow with a schedule:

• Unlock all at once: everything becomes claimable at the unlock time.
• Vest over time: an optional share at the unlock time, then equal parts at the end of each period.
• Locks created on ROUNDUSK cannot be cancelled and their recipient cannot be changed. Only the recipient can claim.
• Supported: SPL Token mints, and Token-2022 mints without extensions that could move or freeze locked tokens. Mints with a permanent delegate, a pause switch, a transfer hook, a default frozen state or confidential transfers (tokenized stocks among them) are refused.

Liquidity locks permanently lock a Meteora DAMM v2 position in the pool of a migrated ROUNDUSK market. The position keeps earning fees for its owner; the liquidity can never be withdrawn.

Bridge

Bridging uses deBridge Liquidity Network. You sign one Solana transaction that creates an order; a solver delivers the asset to your address on the destination network. deBridge charges a fixed fee (about 0.015 SOL) and a small protocol fee; the solver's costs come out of the amount received. ROUNDUSK adds no fee.

Swap

Swaps are routed by Jupiter across Solana liquidity. Any token with a route can be swapped, including tokenized stocks and every ROUNDUSK market. ROUNDUSK adds no fee. Anyone can create a token with any name: check the mint address before trading.

Programs and wallets

The ROUNDUSK engine program

ROUNDUSK's own program is small and does three things: it splits harvested fee rewards 3/5 vault, 1/5 treasury, rest buyback (RouteFees); it splits realized vault profit 1/2 to the creator reward pool and the rest to buyback (RouteProfit); and it holds each creator's vault profit rewards until that creator claims them (Allocate, Claim). It cannot touch creator fee rewards, user wallets or launched tokens. Status: live.

Check that the deployed program is this source: build contracts/ with node contracts/build.mjs (cargo-build-sbf, pinned pinocchio 0.9.3), then compare the sha256 above with the output of solana program dump BRmNPuqQ4SFFr7mZ9M5PLotUTxmSuX1GXaX2ED77RDSK engine.so and sha256sum engine.so. The source has no comments by design; every rule is in the code.

Programs ROUNDUSK builds on

Everything else runs on existing, verified mainnet programs:

Protocol wallets, one role each:

Custody and controls

What you trust, stated plainly: the protocol wallets are derived from one master seed held offline by the operator. Whoever holds the seed controls every protocol wallet. The keeper is the only process that signs for them, and every movement is recorded in the public ledger with its transaction.

• Your wallet signs every transaction you make; the site never holds your keys. The server only relays transactions it built for your session.
• Creator fee rewards never pass through a protocol wallet: creators claim them from the pool.
• Admins can queue, close and pause vault positions within the leverage cap, set the ROUNDUSK mint once, pin a buyback pool and hide a market from listings. Admin actions cannot move funds directly.
• Signing in to edit a profile or claim rewards signs a message only: it sends no transaction and grants no approval.
• The ROUNDUSK engine program is upgradeable; its upgrade authority is listed above. The engine admin can pause fee routing and change the keeper and payout wallets, but cannot pause creator claims or reduce an allocation already written to a creator record. The upgrade authority could replace the program, so it is a trusted key like the master seed.

Risks

• Launched tokens are highly speculative and can lose all value. Anyone can launch a token.
• Vault positions are leveraged derivatives: they can lose money or be liquidated, and the venue carries its own operational and smart-contract risk.
• Bridge orders depend on deBridge solvers; assets sent to a wrong address cannot be recovered.
• Buybacks and burns do not guarantee a higher token price.
• The protocol wallets are custodial (see above).

FAQ