01A market for community-created coins
Create a coin, discover its community, and trade through a shared on-chain market.
Memeport brings coin creation, discovery, trading, and community discussion into one application. Creators publish a coin on Sui; participants can inspect its market, buy or sell, and follow the activity associated with their wallet.
Sui is the first supported network. Deployment status and the active network are shown in the application; this paper does not announce a mainnet release. A listing is not an endorsement or a promise of future value.
From an idea to an open market
Upload an image, define your coin, then approve its publication and curve creation.
Creators supply a name, symbol, description, image file, and optional community links. The application stores uploaded image bytes and uses a first-party media reference; creators do not need to host an image themselves.
Launching involves two wallet approvals: publishing an immutable coin package, then opening its shared bonding curve. A pending launch can be resumed after an interrupted second approval. Publishing alone does not mean trading has opened.
The standard coin uses six decimals and a supply of one billion tokens. The source defaults allocate 793.1 million to curve trading and 206.9 million to migration liquidity. Free creator allocations are disabled; creators can buy through the same public curve.
Where the price comes from
The curve determines early prices. After migration, the connected liquidity pool determines them.
During the launch phase, contract reserve math determines a trade quote. Buys add SUI and remove tokens from the curve; sells return tokens and withdraw SUI. Trade size changes the execution price, so a displayed spot price is not a guarantee of the price for an entire order.
Buy amounts are denominated in SUI. Sell amounts are denominated in the coin being sold and are limited by the connected wallet's token balance. Both actions require SUI for network gas. Slippage protection sets the minimum acceptable output; a changing market can cause a transaction to fail instead of filling below that limit.
Market capitalization is a price-based estimate of token supply value, not the amount of SUI available to withdraw. Volume measures executed trades over a time window; it is not a measure of profit or safety.
Fees and creator participation
Curve trades pay protocol and creator fees directly through the contract.
The contract source defaults are 0.75% protocol fee and 0.50% creator fee per curve trade. These are configuration values, not a promise that every deployed market uses those rates. Review the active market quote and configuration before signing. Network gas is separate, and migrated pool trades use their own fee rules.
Creator fees settle to the configured recipients during curve trades. Creator Studio reports indexed payouts, not a guaranteed income or an immediately synchronized balance. Direct recipient payments do not require a separate claim.
Compatible contracts support up to eight fixed fee recipients. Availability is deployment-specific. Opt-in holder rewards are a separate, not-yet-activated policy: part of the creator share funds a reward vault instead of being sent directly to the creator.
Creator rewards after graduation
Cetus integration now; a native exchange is a future milestone.
Compatible deployments support Memeport-routed trades that pay the curve's configured creator recipients and Memeport treasury in the same transaction as a Cetus swap. The quote must disclose both those charges and the Cetus pool fee. Direct Cetus trades and other routes can bypass Memeport's additional fees.
The compatible liquidity-vault implementation retains pool fees for reinvestment into the same pool, not creator, treasury, or holder withdrawals. Its principal has no withdrawal path in the current code. A permanent guarantee also requires verifying package immutability and the deployed vault; implementation alone is not that guarantee. Cetus controls its own protocol fee.
A future native Memeport exchange is planned to enforce creator fees within its own canonical pool contracts, including trades routed by other applications. That would not enforce fees on separate pools elsewhere. It requires an approved market design, independent audits, adversarial testing, and operating funding before launch. No date is promised.
Graduation is a transition, not a reward
Reaching a reserve target ends curve trading and begins liquidity migration.
A curve graduates when its real SUI reserve reaches the configured target. Targets vary by deployment; read the active coin's target and on-chain configuration rather than assuming a universal amount. The progress indicator describes reserve progress, not a predicted return.
Curve trading stops at graduation. An authorized migration process prepares liquidity on Cetus, a Sui liquidity protocol, and records the canonical pool. Trading can resume through that pool after migration is finalized. Delays, failed jobs, or unavailable liquidity can interrupt this transition.
The pool price then follows pool reserves and trades. Other venues can have different prices and liquidity; this app does not promise a single global price or route every external venue. Pool and liquidity-lock details must be checked on-chain.
On-chain execution, indexed discovery
Wallets approve transactions; the application indexes activity for charts and profiles.
The web application builds transactions for the connected wallet to approve. Sui contracts enforce curve trading and migration rules. An indexer reads chain activity into PostgreSQL so the app can show trades, candles, portfolio estimates, creator activity, and market lists.
Discovery refreshes periodically rather than displaying every chain event instantly. Indexing and holder reconciliation can lag. A successful chain transaction may appear in the app later; the transaction explorer is the place to verify execution.
Comments and replies are stored off-chain and authenticated with personal-message signatures. They require no gas. Uploads, comments, and profiles remain subject to service availability and abuse controls.
Risks and release boundaries
A working interface is not a security audit or a guarantee of market liquidity.
Coins can lose value, liquidity can be limited, and creators or traders can behave maliciously. Quotes can change before execution. Wallet approvals should always be reviewed, including the network, coin, amount, and transaction effects.
RPC providers, image storage, indexers, and migration services can fail or become delayed. Development-network assets have no real monetary value and their data can be reset. No uptime, throughput, investment return, or audit certification is claimed by this document.
Mainnet remains a separate release gate requiring independent security review, operational monitoring, incident response, signer protection, and validated liquidity integrations. This document describes the repository's intended behavior, not an audit of a particular deployment.
Holder rewards without withdrawing liquidity
An opt-in creator-fee allocation, not a guaranteed yield. Implementation is in validation and not publicly activated.
The holder-reward implementation collects the configured share of creator fees into a SUI vault. It does not take liquidity principal or fees reserved for liquidity reinvestment. After graduation, funding depends on compatible Memeport-routed trades; trades elsewhere may contribute nothing.
The current collector uses checkpoint-pinned wallet holdings. Eligibility compares two snapshots at least one hour apart and weights each wallet by its lower balance. This is not proof of continuous ownership. The current policy excludes the creator, curve, and vault, requires at least 0.005% of supply, and caps a round at the top 500 eligible wallets.
The worker prepares proportional allocations when unreserved funds reach 0.01 SUI. Integer rounding leaves dust in the vault. It stores a manifest before submission and reconciles the on-chain round and hash after a restart. Approved credits accumulate until the holder claims them with a wallet transaction; network gas applies. This is a claim model, not automatic transfers to every holder.
The snapshot operator is trusted to submit correct allocations; the contract does not independently prove wallet holdings. It enforces funding limits, ordered rounds, and claimant ownership of credits. Public manifests support inspection but do not remove operator trust. Security review and actual wallet payment validation are required before activation.
Sui first. More networks only after validation
Solana, BNB Chain, and Base are roadmap targets, not currently available markets.
The first priority is a reliable Sui lifecycle: create, discover, buy, sell, graduate, and track activity. Holder-reward activation follows contract review, snapshot validation, and end-to-end payment checks.
The intended expansion order is Solana, BNB Chain, then Base. Each network needs native contracts, wallet integration, market indexing, liquidity integration, and its own testing and review. No release dates are committed.
A future multi-network interface would bring discovery and portfolio views together while keeping each transaction and coin explicitly tied to its network. Bridging a single token across chains is not included in this roadmap.