V2 Markets

Preview only. Canonical devnet admission is blocked. V2 is not mainnet ready. V2 separates the creator token (base) from the asset used to trade it (quote): SOL/WSOL, USDC, or an admitted verified tokenized stock.

Stock Pairs

AIENG / NVDAx means AIENG is bought and sold using NVDAx. Holding AIENG does not represent ownership of NVDAx or the referenced stock. A real stock pair needs both protocol approval and venue admission.

Token Engine

Measured fees fund purchases of that market’s base token. The exact purchased receipt is burned. Quote revenue, donations and operating SOL are accounted separately. Buyback execution uses a bound market and an expiring protocol-authorized price limit.

ROOT Contribution

Each market has a quote inbox. An approved conversion route may convert earned quote fees into WSOL for separately authenticated V2 ROOT funding. A deposit is not earned revenue, and a contribution is not a completed ROOT buyback. Existing V1 ROOT is unchanged.

Permanent Liquidity

The required migration policy permanently locks distributable protocol liquidity and gives position custody to the market PDA. There is no creator withdrawal or unlock date. Issuer seizure, freezes, market prices and upgrade authority remain separate risks.

Launch Protection

Linear initial fee decay applies to all traders; the first-swap fee bypass is disabled. Parameters remain proposed. Bots can wait or use faster ordering; fee decay cannot guarantee equal access.

Issuer Controls

A stock issuer may pause or freeze transfers, change a hook or exercise permanent-delegate powers. Unknown, paused, frozen, unsupported or changed critical controls fail closed. Every economic instruction decodes current controls again; a cached UI observation is never authority.

Verified Quote Assets

Verification uses exact mint and token-program identity, never ticker matching. Current decimals, extension controls and protocol admission must agree. Registry membership alone does not prove Meteora admission or safety.

Creator Payouts

Choose the creator wallet or a community wallet before launch. That recipient is immutable for the market. Proposed test economics are Creator 40%, Token Engine 30%, Platform 20%, ROOT 10%. Holder rewards remain research only.

Risk

Issuer interventions can block trading, graduation, fee claims or buybacks. A quote asset may lose liquidity or market value. No price peg, backing, yield or stock ownership is promised for the creator token. Unsupported routes remain pending rather than sending funds elsewhere.

Mint Signature & Metadata

Optional vanity generation runs in a browser worker and retains its secret only in browser memory. The suffix is cosmetic; official market verification comes from V2 state and deployment identity. Permanent metadata must be uploaded and publicly hash-verified before a create transaction can be constructed.

Preview V2 Create → · Inspect a labeled design specimen →

Trading fees. Market buybacks.
Fewer tokens.

Every launched token has its own Engine. A fixed share of fees funds purchases of that same token. Everything the Engine purchases is permanently burned.

How Engine works

Trading generates venue fees. Claimed distributable partner fees are divided between three destinations; only the Engine allocation funds its token’s buybacks.

Fee split

Frozen V1 split. These are shares of the claimed distributable partner fees, not percentages of total trade volume or all venue fees.

For each 1 SOL of distributable partner fees, allocation is 0.55 SOL to the creator, 0.25 to Engine, 0.20 to Voltra and zero to ROOT. Integer remainders remain explicit dust. DBC uses 110 bps fixed; DAMM preset 0 uses a 25-bps base fee with dynamic fees. Historical configurations retain their recorded allocations.

Engine lifecycle

1. Charging

   Not enough earned revenue for the next buyback.

2. Ready

   The Engine meets the execution requirements. Having enough funds alone is not enough: price checks and timing must also pass.

3. Buyback

   The Engine purchases its own token from the market.

4. Burn

   Everything purchased in that execution is permanently burned.

Buyback & burn

The Engine buys on the market; it does not burn tokens held in user wallets. Its purchase and the burn happen atomically: if a required step fails, the execution rolls back. A successful burn reduces SPL token supply.

Buybacks depend on earned fees, liquidity and execution conditions. They do not guarantee price increases or investment returns.

Creator guarantees

Creator cannot withdraw Engine funds through the normal creator path. After locking, the creator cannot redirect the Engine share through the normal creator flow. The creator receives their own allocation separately.

This guarantee concerns the normal creator instructions. It does not remove the external administrative or program-upgrade trust boundaries described below.

Creator economics

The frozen V1 split sends 55% of claimed partner fees to the creator, 25% to Engine, 20% to Voltra and zero to ROOT. These are shares of distributable partner fees, not percentages of total trade volume. Existing devnet tokens retain their own configured allocations.

The creator’s allocation is separate from the token-specific Engine vault. Normal creator instructions cannot withdraw or redirect Engine funds after locking.

Creator pages & community

Each creator page groups tokens by their on-chain creator wallet. Current summaries come from loaded devnet accounts. Display names, avatars, bios and community links appear only when supplied; a devnet badge is a network label, not identity verification.

Optional Website, X / Twitter, Telegram and Discord links help communities find each other. The create preview validates web URLs and omits empty or invalid links. No social account ownership is implied.

Token meaning is the creator’s longer story. A creator note explains what the token means to them. These are optional creator-provided text, not generated endorsements. Current token descriptions come from existing metadata; the extended fields remain frontend presentation data until metadata ingestion supports them.

Trading and graduation

The intended production architecture uses Pump for bonding-curve trading, PumpSwap after graduation and Pump Fees for creator-fee sharing. Graduation changes the trading venue, not which token the Engine buys and burns.

This is the product’s intended integration, not a claim that the current web build launches or trades through Pump. The creation screen is a preview; existing connected trading actions use the current devnet implementation.

Security model

• Each token has a program-controlled PDA/vault for Engine funds.
• Execution is permissionless, subject to on-chain checks.
• The caller cannot redirect Engine funds or purchased tokens to themselves.
• Purchased tokens are burned atomically in the same execution.
• Direct donations are not counted as earned fee revenue.

Price observations, spending limits and timing checks constrain execution. These controls are not an independent price oracle or a guarantee against every market risk.

External trust assumptions

The intended integration treats Pump, PumpSwap and Pump Fees as external upgradeable programs. Pump retains administrative and upgrade trust boundaries; a creator lock does not eliminate them.

Pump’s documented fee-sharing flow finalizes recipients and revokes normal sharing-config admin updates. This supports a creator-locked normal path, not a claim of immunity to external program changes. See the official creator fee-sharing documentation ↗ and Pump program configuration ↗.

The existing devnet Engine program also retains an upgrade authority. Mainnet integration and its authorities require separate verification before release.

Frequently asked questions

Contracts / devnet

No production Engine deployment is claimed here. The repository records a real-devnet buyback/burn lifecycle for the test Engine program below.

The existing test implementation uses Meteora DBC / DAMM v2. It is separate from the intended Pump architecture and does not verify a Pump integration. Its default revenue weights are 35 / 30 / 30 / 20, making the Engine share approximately 26.1% of the routed revenue stream. Token pages use their loaded configuration.

Recorded status: real-devnet lifecycle executed; finalized-indexer reconciliation outstanding. Phase 4.5 proof is not signed off. Local-validator results and devnet results are separate, and neither establishes mainnet readiness.

Launch modes

Every token on the platform launches with an Engine. The launch mode only changes how the token is presented, never how the Engine works, how fees split, or how buybacks execute.

Meme — a token with an Engine and nothing else attached.

Stock Engine — the same token, plus a narrative reference to a public equity ticker chosen by the creator.

Basket Engine

A Basket Engine is a normal Engine token with a creator-defined stock theme. It does not hold the referenced equities. New V1 partner allocations are Creator 55%, Engine 25%, Voltra 20%, ROOT 0%. Existing devnet configurations are unchanged.

Reference basket only. This token is not backed by the referenced stocks and does not represent ownership of them.

Trading fees fund market buybacks of the Engine token and burns of that same token.

Reference Baskets

Weights are creator-defined metadata used for discovery and informational reference views. A basket contains 2–8 unique, normalized stock tickers, each with a positive integer weight in basis points, totaling 10,000 (100%).

Reference basket movement is the sum of each stock quote’s percentage change multiplied by its weight divided by 10,000. It is shown only when all component quotes are available. A partial view lists available components and withholds the combined move. This is not NAV, backing, a peg, or token performance.

New drafts use metadata schema v3 with basketReference containing name, optional thesis and components. Readers preserve v1/v2 support; existing immutable metadata is never rewritten. Create remains preview-only until Pump-native launch wiring is complete.

Optional presets are editable themes, not investment recommendations. Demo tokens and sample quotes are labeled separately; production never uses fabricated movers.

Market Movers

Market Movers connects a traditional stock ticker to mint-verified RWA registry entries, direct Stock Engine references and Basket Engines containing that ticker. Symbol matches never establish verified RWA identity. RWA controls are inspected live on their existing detail pages.

StockQuoteProvider supplies server-side quotes through cached, batched requests where supported. If no provider is configured or a quote is unavailable, the relationships still render without price moves. Source and venue timestamps accompany available component data. Quote changes may be delayed and reflect the provider’s reporting period.

Engine references create no stock ownership, custody, brokerage or redemption rights. Reference basket only. This token is not backed by the referenced stocks and does not represent ownership of them.

Stock Engine

A Stock Engine token carries a reference to a public company’s ticker, such as NVDA or TSLA, together with the creator’s explanation of the connection. The token keeps its own symbol; the referenced ticker is displayed beside it, never merged with it.

Stock references are informational narrative metadata.

Quotes for referenced tickers are fetched server-side through a replaceable market-data provider. When no provider is configured the interface shows “quote unavailable” rather than a placeholder number, and referenced tokens still display normally.

Engine Radar

The radar sorts every Engine by what it is about to do: ready to fire, heating up, largest buyback balance, most burned, and recently fired. All of it derives from live protocol state through one shared status function, so a token cannot appear ready on one screen and charging on another.

Threshold progress is only shown when the threshold is known. If it cannot be derived, no percentage is displayed.

ROOT · inactive

New V1 markets allocate zero to ROOT. No ROOT vault funding, conversion or buyback is active. Historical ROOT fields and ledgers remain preserved for compatibility.

Engine operating reserves are separate from trading revenue and are never buyback principal. Production execution is not enabled.

Stock Engine risks

A Stock Engine token does not represent ownership of the referenced security, is not backed by it, does not track its price, and grants no shareholder rights.

Reference stock performance does not guarantee token performance. The two are economically unrelated.

There is no price peg of any kind between them.

External market data may be delayed, incomplete, or unavailable, and should not be relied on for trading decisions.

RWA Markets

RWA Markets is a read-only discovery layer. It lists tokenized equity mints that Voltra has explicitly verified, shows the issuer controls configured on each mint as read live from Solana mainnet, and links them to any Engine token that declares a matching stock reference.

Voltra does not buy, hold, custody, swap or redeem tokenized assets, and no Engine fee revenue is routed into them. Nothing on these pages is an offer, a quote, or a route to trade.

Mint state is read from Solana mainnet-beta. Voltra’s own Engine data is devnet. The two clusters are unrelated and are labelled separately wherever both appear.

Verified mints

A “Verified mint” badge means one specific thing: the mint address appears in Voltra’s issuer registry. It is awarded on the address alone.

A token is never verified on the strength of its name, symbol or metadata. This matters because impostor mints already exist on Solana using the identical symbol and name as real tokenized equities. A ticker is not verification.

Verified does not mean risk-free. It says the address is the one Voltra recorded for that issuer. It says nothing about the asset’s value, its liquidity, the issuer’s solvency, or the controls the issuer retains over it.

Issuer controls

Tokenized equities are typically Token-2022 mints that keep powers an ordinary token does not have. Voltra reads these live on every refresh rather than storing them, because an issuer can change them at any time.

A freeze authority can freeze an individual token account. A pausable mint can halt all transfers at once. A permanent delegate can move tokens out of any account without the holder’s consent. A transfer hook runs issuer code on every transfer and can be activated later even if it is inactive today.

Voltra reports each of these as a factual flag and deliberately does not combine them into a safety score. Where a value cannot be read it is shown as “Unknown”, never as absent.

Stock references

An Engine token may declare a stock reference in its metadata. That reference is narrative. It creates no relationship between the token and the referenced security, and no relationship between the token and any tokenized asset listed in RWA Markets.

A stock reference does not back a creator token. It gives no redemption or collateral claim. A separate Voltra V2 market may trade against a qualified tokenized stock as its quote asset; that trading pair sets the price denomination, not ownership of the stock or backing for the creator token.

Stock references are informational narrative metadata.