MINTAGE official emblem MINTAGE.
SOLANA NATIVEBATCH-BASED SETTLEMENTDEMO MODE

Batch minted.
Uniform price.

One shared minting window. One clearing price. Designed to remove transaction-speed advantages from token distribution — not to reward the fastest bot.

Execution

SINGLE

Clearing

UNIFORM

Mechanism

ON-CHAIN

Batch engine / concept

SETTLEMENT IN

04:59

Batch #01
ONE EXECUTION

03 / Minting window

Batch #01

Explore a working frontend simulation of uniform-price clearing.

Simulation • not live
Batch status
Accepting commitments
EPOCH 001

Time to settlement

04:59

Simulated deposits

148.50 SOL

Wallets in batch

126

Illustrative fill toward 250 SOL59.4%
0 SOL250 SOL visual target (not a deposit cap)

Settlement rule

One clearing price

Deposits

Proportional

Network

Solana

Commitment console

Commit SOL

Test the interface with a simulated SOL deposit. No funds are transferred.

SOL
ModeLocal simulation
Estimated clearing priceDetermined after close
Network feesNone in demo

This prototype never signs a transaction, requests an approval or receives SOL.

04 / Execution cycle

Three steps.
One outcome.

The system collects commitments in a shared window before calculating a single clearing price.

01

Commit.

Deposit SOL into the same open batch. Arrival speed does not determine the final entry price.

SHARED WINDOW
02

Mint.

The commitment window closes. Total eligible volume determines the uniform batch clearing price.

SINGLE SETTLEMENT
03

Claim.

Every eligible wallet claims the calculated allocation. Launch liquidity follows the program's configured rules.

EQUAL-PRICE DISTRIBUTION

05 / Protocol architecture

Engineered for fairness.

Transparent rules are the product. Execution claims require independent verification of deployed code.

Equal Price for All

All eligible wallets in a single batch are assigned the same settlement price.

Programmatic LP Burn

A proposed liquidity mechanism that burns LP tokens on launch, subject to actual contract implementation.

Zero Front-Running

Batch pricing is designed to neutralize within-batch speed advantages, not guarantee MEV immunity across every transaction.

06 / Parameters

Batch specifications.

ParameterConfigurationState
NetworkSolanaTarget chain
Deposit assetSOLDesign specification
Settlement modelUniform Batch ClearingDesign specification
LP statusBurned on launchNot verified
Admin controlsIntended immutable rulesNot verified
Smart contractNot providedPending deployment

07 / Settlement history

Batch ledger.

No on-chain transaction data supplied. Rows below are locally simulated settlement records only.
BatchVolumeWalletsSettlementTransaction
No settled batches in this demo yet. The current simulation will settle at the end of its countdown.

When a program address is supplied, verified settlement signatures can be linked to Solscan or Solana Explorer.

08 / Mechanism comparison

Not a race to the block.

Illustrative design comparison. Outcomes depend on actual implementation and market conditions.

FeatureTraditional public DEX launchMINTAGE batch model
Entry priceVaries by executionOne price per batch
Timing advantageMay benefit early fillsDesigned to be neutralized
MEV exposureDepends on route / executionReduced within batch by design
Allocation basisTrade-by-trade fillsEligible share of batch
Liquidity rulesLaunch-specificConfigured programmatically

09 / Questions

Know the rules.

A batch mechanism is only as trustworthy as its deployed code and verified operational controls.

Review audit status

Eligible SOL commitments are aggregated into one mint window. When it closes, the protocol's configured pricing formula derives a single price used for every qualifying wallet in that batch.

No protocol should claim universal MEV immunity without proof. Uniform batch pricing can remove certain intra-batch priority advantages, while deposit inclusion, surrounding markets and liquidity deployment may still carry risks.

The proposed protocol rules call for refunds if the minimum qualifying amount is not met. Exact conditions, timing and refund permissions must be validated in the deployed smart contract.

The planned design burns liquidity-provider tokens after liquidity creation. Whether liquidity can be removed or altered depends on the exact pool type, token permissions and implementation.

Not in this standalone prototype. Wallet connection only requests public wallet access. All deposit and batch interactions are local simulations with no signing or on-chain fund movement.

Security / Verification

Verify. Don't assume.

This is an interactive design prototype. No audit report, verified mainnet program ID, live ledger feed or token contract has been supplied. Do not send assets to addresses you have not independently verified.

AUDIT NOT PROVIDED
Notification