Launch. Collect.
Route. Execute.

A token’s operating layer.

VEYDUCT offers wallet-approved token actions and public lookups. Its custom programs are separate: fee routing, compensation, treasury, staking, vesting, claims, token voting, milestone funding and raffles all require verified deployment before public execution.

The separate Pump flow creates a new Token-2022 mint, native SOL market and onchain metadata URI, then activates its precomputed fee router in a second reviewed transaction. It cannot reuse a standalone SPL mint. Both custom-program flows remain gated on public deployment. Metadata hosting and validation are user responsibilities.

Fixed recipients.
Approved execution.

Project mint + router PDA

        │

        ├─ manual deposit ─────────────┐

        ├─ Pump sweep → collect CPI ──┤ provenance counters

        └─ external receipt → sync ───┘

                                      ↓

                             cumulative 1% fee

                                      ↓

                         fixed net destination shares

                                      ↓

                       owner or scoped executor payouts

The Rust program owns a 504-byte router account derived from creator, mint and nonce. It binds recipients and shares at initialization, keeps obligations backed above rent, and requires the router owner or approved executor to sign settlement to the fixed recipient. The trigger cannot redirect payment. Configuration ownership is not proof of token ownership or creator-fee authority.

Multiple routers may reference one mint. This version is not a canonical one-router-per-token registry. The Pump launch plan records the specific router configured as that market’s creator-fee destination. A saved public plan allows activation to resume without retaining the mint secret.

Stack

Native Rust Solana programs; a pinned browser SDK; exact integer amount calculations; Node 24 Vercel relays; and LiteSVM runtime tests. Native mainnet actions use a separate relay that checks their allowed transaction format and signatures. The original project workspace and custom-program controllers use devnet. Browser receipts help track transactions; chain state remains authoritative.

Immutability

Account terms have no edit instruction. A retained program upgrade authority can still change future execution behavior. Therefore immutable terms are not a claim that the entire deployed system is non-upgradeable. Independent review and an explicit upgrade policy precede mainnet release.

Reconcile every source.

recognized = manual + Pump-vault receipts + external receipts

fee = floor(recognized × 100 / 10,000)

net = recognized − fee

allocation[i] = floor(net × shareBps[i] / 10,000)

claimable[i] = allocation[i] − paid[i]

dust = net − sum(allocation)

reserved = recognized − sum(all payments)

external surplus = balance − rent reserve − reserved

Floor allocations are monotonic. At most one lamport per destination remains in the rounding reserve and can become allocatable as new funds arrive. Reconciliation cannot count that reserve again. Payout failures roll back; one destination’s failure does not prevent separately settling another.

The fee is 1% of recognized receipts, not a token trading tax. The router creator currently chooses the fixed fee recipient; a global VEYDUCT collector is not enforced. The older capped compensation vault has different economics: 2% of contributor gross.

Evidence before labels.

The router artifact is a remote compatibility build from Solana Playground. Its actual dependency lock and compiler version were not provided. Preserved logs contain dependency stack diagnostics; passing exercised runtime paths is not a reproducible build or a security audit.

A platform-sized roadmap.

Twelve proposed monthly work packages. Release gates determine readiness; these are not promised calendar deadlines.

01 / Token & fee engine

Create exact supply and fixed native SOL payout rules.

• Atomic SPL mint, ATA and mint-authority revocation
• Persistent router, source counters and owner-authorized payouts
• Compiled runtime tests and a usable review console

02 / Pump market launch

Connect token creation to a real market and creator-fee destination.

• Verified Pump create flow and onchain metadata
• Router-PDA fee destination from market creation
• Resumable launch steps and actual curve receipts

03 / Creator-approved automation

Run approved instructions through a revocable executor without changing fixed destinations.

• Keeper retries and transaction identity
• Minimum economic batch sizes and fee budgets
• Owner or approved executor can settle manually when keepers stop

04 / Buyback & burn

Spend a fixed route budget on the project token, then reduce its supply.

• Pinned mints, venues and program accounts
• Onchain spend ceiling, output floor and expiry
• SPL BurnChecked with measured supply reduction

05 / Holder rewards

Distribute accounted assets to an eligible holder set.

• Historical balance reconstruction and exclusions
• Published snapshot commitments and challenge policy
• Replay-proof payments with unpaid amounts carried forward

06 / Treasury control

Give a project governed control over its treasury destination.

• Explicit multisig signers and threshold
• Exact proposal execution and expirations
• Signer changes and timelocked handoffs

07 / Liquidity engine

Use fixed budgets to build positions with explicit custody rules.

• Pool identity and supported asset checks
• Slippage and independent price protection
• Fee recycling and permanent-lock option

08 / Stablecoin routes

Add settlement assets with separate accounting per mint.

• Exact decimals and supported token extensions
• Measured token receipts and transfer-fee treatment
• USDC routes and asset-specific limits

09 / Staking & governance

Allow opted-in projects to govern through durable voting checkpoints.

• Deposit and withdrawal accounting
• Reward-per-share and checkpointed voting power
• Quorum, voting periods and exact timelocked actions

10 / Funding bands

Sell reserved inventory under predetermined market conditions.

• Bounded inventory and fixed proceeds destinations
• Price observation and settlement windows
• Recoverable expired orders and partial fills

11 / Additional launchpads

Add market adapters only after source authority is proven.

• PumpSwap post-migration collection
• Meteora creator or partner PDA authority
• Versioned adapter and pool compatibility registry

12 / Protocol distribution

Package the proven platform for projects and integrators.

• Documented SDK and independently runnable keeper
• Verified project directory and accounting exports
• Optional platform-token utility decision

Verify the source authority.

Pump integration validates the canonical curve, program, creator vault and event authority. The curve must identify the router as its creator destination and use native SOL. A sweep precedes collection for the current curve fee flow. Post-graduation PumpSwap requires a separate adapter.

Pump creator vaults aggregate by creator, not token, and can receive donations. “Received through Pump” is a transport fact, not proof of trading revenue from one mint. Direct collections made by other callers arrive as external receipts and can be reconciled under the same fixed rules.

Meteora, swaps and LP require separate authority and account validation. An API quote does not authorize arbitrary transaction instructions. A future buyback module must enforce input budget, destination mint, output floor, expiry and venue inside its program, then use SPL BurnChecked for supply reduction.

Holder rewards require a specified snapshot authority or verifiable reconstruction and replay protection. Raffles require independently verifiable randomness and eligibility rules; they are not included in this release.

Utility must be implemented.

The platform can operate without a proprietary coin. No VEYDUCT coin, sale, staking mechanism or holder fee entitlement has been launched. A project token created through the studio is separate from a platform token.

Potential future utility includes paying optional service fees or participating in narrowly scoped governance. Token ownership must never grant permission to rewrite existing recipients or withdraw project funds. Choose and implement the actual mechanism before publishing tokenomics or launching a coin.

What custom programs still need.

• All nine custom programs remain undeployed. Fund the deployment wallet and verify the exact deployed bytes for each program before enabling it.
• Create a compatible market with the router as its real fee destination.
• Exercise trades, fee collection, deposits, withdrawals and recipient payments on the intended public network for each supported program.
• Test supported wallet extensions, rejected approvals, expired transactions and retry recovery.
• Complete the intended modules and their adversarial runtime tests.
• Produce a reproducible pinned build, independent review, explicit upgrade policy and production infrastructure before enabling custom mainnet custody or routing.

The five native mainnet tools use existing Solana programs and do not depend on these custom deployments. Local signed-transaction tests check their safeguards; funded mainnet acceptance remains unverified. Public RPC limits can interrupt reads or submissions. The interface never substitutes invented balances or successful receipts.

Research and provenance.

• Sinjoh developer model — source of the product-category comparison; VEYDUCT is an independent Solana implementation.
• Pump official IDLs and instruction documentation — sweep, collection and curve identity.
• SPL Token interface and Associated Token Account interface — mint and account creation.
• Jupiter composable swap reference — a future integration, not an enabled module.