Daxa City / Docs
How it works
What DaxaPad does
DaxaPad is a launchpad for Solana tokens. A creator configures a token, reviews its supply, allocations and costs, and signs each transaction with their own wallet. Every launch that is confirmed on the network gets a public page where anyone can compare what the creator declared with what the chain shows.
The site is set to Solana mainnet-beta. “Daxa City” and its districts are the way projects are filed and found; they are a theme, not a product feature with rules of its own. DaxaPad has no token of its own.
- Creates: a classic SPL Token mint, its Metaplex Token Metadata account, the creator’s token account, and the supply.
- Optionally sends: declared allocations to up to 8 wallets, in one transaction.
- Optionally opens: a Raydium CPMM pool with the creator’s tokens and SOL, and optionally burns the creator’s LP tokens.
- Publishes: a project page, and lists the launch in Explore.
The launch workflow
A launch is a stored record with an ordered list of steps. Each step is exactly one transaction, and each transaction either happens completely or not at all.
| Step | What the transaction does | When it exists |
|---|---|---|
| Create token | Creates the mint account at an address derived from your wallet and the launch record, initializes it, creates your token account, mints the whole supply to it, creates the metadata account, gives up the mint authority if you chose to, and pays the platform fee if one is configured. | Always |
| Send allocations | For each declared recipient: creates their token account if it does not exist, and transfers their amount from your wallet. All recipients are in one transaction. | When you declared allocations |
| Create liquidity pool | Wraps your pool SOL in a temporary account, runs Raydium’s pool creation with your tokens and that SOL, and closes the temporary account. You receive the LP tokens. | On the Raydium CPMM route |
| Burn LP tokens | Destroys the LP tokens in your wallet. | When you chose to burn them |
For every step the page does the same four things:
- Build and simulate. The server builds an unsigned transaction for your wallet and simulates it against the network. A transaction whose simulation fails is not offered for signing.
- Check. The server and then your browser each decode the transaction and compare it, instruction by instruction, with the configuration you reviewed. The list of actions you see is produced from the transaction’s own bytes.
- Sign. Your wallet signs. The server relays the signed bytes only if they are the transaction it prepared (a wallet’s own guard instructions are tolerated; nothing else is).
- Track. The step is “waiting for the network” until the network confirms it, rejects it, or can no longer include it.
A prepared transaction is valid for about 75 seconds, because it names a recent blockhash. After that it has to be reviewed again. Until the creation transaction is signed, the configuration can be edited; once it is signed, it is fixed.
Fees and costs
Before you sign, each transaction’s costs are listed line by line, and each line says how the figure was obtained: exact (fixed by the network, the protocol or the request), measured (read from simulating that exact transaction), or estimate (computed before a transaction exists).
| Cost | Paid to | Notes |
|---|---|---|
| Network fee | The Solana network | Per transaction. Includes a small priority fee capped by DaxaPad. |
| Rent deposit: mint account | Held by the account | Required for the account to exist. Not recoverable: a mint account cannot be closed. |
| Rent deposit: your token account | Held by the account | Refundable if you later close the account, which needs a zero balance. |
| Metadata account rent and creation fee | The account and the Metaplex program | Charged by the Metaplex Token Metadata program when the metadata account is created. |
| Rent deposits: recipient token accounts | Held by the accounts | Only for recipients that do not have a token account for this token yet. |
| Pool creation fee | Raydium | Read from the protocol’s fee configuration account when you review, and shown as exact. |
| Rent deposits: pool accounts | Held by the accounts | The pool state, LP mint, two vaults, observation account and your LP token account. |
| SOL placed in the pool | The pool | Liquidity you provide, not a fee. |
| Platform fee | This deployment’s operator | Only when configured. See the status panel below for this deployment’s value. |
DaxaPad never invents a fee recipient. A platform fee exists only when the operator sets both an amount and a recipient address; with neither, the creation transaction contains no fee transfer, and your browser’s check would refuse one. Estimates are labelled as estimates; the figure you finally approve is the one your wallet shows.
Raydium CPMM integration
The liquidity route uses Raydium’s constant-product program (“CP-Swap”, CPMM). It was chosen because it opens a pool for a classic SPL token paired with SOL in a single instruction, needs no order-book market, and is deployed under published program ids on mainnet and devnet.
- Program on Mainnet
- CPMMoo8L3F4NbTegBCKVNunggL7H1ZpdTHKxQB5qKP1C
- Fee configuration
- Index 0. Its trade fee and pool creation fee are read from the chain, never hard-coded.
- Creation fee account
- DNXgeM9EiiaAbaWvwjHj9fQQLAX5ZsfHyvmYUNRAdNC8
- Other clusters
- Mainnet program CPMMoo8L3F4NbTegBCKVNunggL7H1ZpdTHKxQB5qKP1C; devnet program DRaycpLY18LhpbydsBWbVJtxpNv9oXPgjRSfpF2bWpYb.
- The pool creation instruction is built by Raydium’s official SDK (
@raydium-io/raydium-sdk-v2,makeCreateCpmmPoolInInstruction). DaxaPad derives the accounts and then checks the result with its own independent decoder before offering it. - The pool’s address is derived from the fee configuration and the two mints, so a pool for a launch can be created only once. If the pool already exists when the step is reviewed, the step is recorded as done instead of being sent.
- The first price is your SOL divided by your tokens. The program mints LP tokens equal to the square root of the product of the two amounts, keeps 100 base units in the pool for ever, and sends the rest to your wallet.
- Trading opens as soon as the pool exists. DaxaPad has no bonding curve, no presale, no automatic migration and no contract of its own.
- The integration lives behind one interface (
src/server/launch/provider.ts); another protocol can be added by implementing it.
Data and freshness
Every block on a token page carries one of three labels.
| Label | What it is | Where it comes from |
|---|---|---|
| Onchain | The mint, supply, decimals, authorities, metadata account, recipient balances, the pool’s reserves and LP supply, and the signatures of launch transactions. | Solana accounts, read by this deployment’s RPC endpoint. Each read shows its slot and time. |
| Creator-declared | The description, links, district, allocation labels and the planned split. | The launch record the creator signed in to make. Stored by DaxaPad; not verified beyond the wallet’s signature. |
| Third-party | Dollar price, dollar liquidity and 24-hour volume of the launch’s pool. | GeckoTerminal’s public API, mainnet only, for the specific pool the launch created. |
| Third-party | The “Elsewhere on Solana” board: which tokens are on it, and their holders, liquidity and volume. | Jupiter’s public token index: its most traded entries that started on a launchpad and carry its “verified” listing mark. The two authority columns of that board are read from the chain by DaxaPad. |
- Scope. Explore lists launches made through DaxaPad on Solana mainnet-beta, and only once their creation is confirmed and the mint was read back from the chain. It is not an index of Solana tokens. Any other mint can still be opened and read; its page says it is not registered.
- Freshness. A stored read younger than 45 seconds is served as it is; an older one is re-read when the page is requested. A scheduler pass also re-reads registered launches, oldest first, and settles steps that are waiting for the network.
- Unavailable is not zero. A value that could not be read is shown as unavailable. If the chain cannot be read, the last stored read is shown with its time and marked stale for up to 15 minutes.
- Elsewhere on Solana. The board under Explore shows real tokens that were launched somewhere else. It is kept apart from DaxaPad’s registry and labelled as not being DaxaPad launches; a token appearing on it has not been reviewed by DaxaPad and is not recommended by it. The list is refreshed every five minutes; when the index does not answer, the last list is marked stale for up to six hours and then removed.
- Live readings on the landing page. The slot under the main figure, the costs in “Run the numbers” and Raydium’s fee are read from the chain by this deployment, at most once a minute. The figure’s ripple starts when a newer slot is read; the rest of the animation is an illustration.
- No invented numbers. There are no holder counts, charts, market caps or trade feeds unless a source provides them, and none is simulated.
Security model
- No keys. DaxaPad never asks for, receives or stores a private key or seed phrase. The server builds unsigned transactions and relays signed ones.
- Sign-in. The server issues a random one-time message naming this site and expiring in five minutes. The wallet signs it; the server verifies the signature against its own record and consumes the nonce in one atomic step, so a signature cannot be used twice. The session cookie is HttpOnly, and only its hash is stored.
- Ownership. A launch record can be read, edited or advanced only by the session of the wallet that created it. An address typed into a form is never treated as proof of anything.
- Transaction integrity. The signed transaction must match the prepared one, with your wallet as the only signer. Your browser independently checks every instruction against the reviewed configuration before your wallet is asked.
- Uploads. Images are limited to PNG, JPEG and WebP up to 512 KB; the server checks the file’s real format and serves it with sniffing disabled and scripting impossible.
- Links. Only https links without credentials are stored, and they open in a new tab without passing a referrer or opener.
- Limits. Sign-in, writes, uploads, chain lookups and transaction building are rate limited per account or network address.
- Not audited. DaxaPad deploys no program of its own, but its application code has not been audited by a third party. Read what your wallet shows before you approve anything.
Failure and recovery
- Declined in the wallet. Nothing was signed or sent. The step stays ready; review it again whenever you like.
- Rejected by the network. A transaction is atomic: when it fails, nothing in it happened. The step shows the reason and can be prepared again.
- Unknown outcome. If the network has not reported a signed transaction yet, its state is unknown, not failed. DaxaPad does not build a replacement while the first could still land. It becomes “expired” only when the network’s finalized block height has passed the transaction’s last valid height.
- Interrupted launch. Finished steps are recorded; open the launch from your dashboard to continue with the next one.
- Already done. Before building a creation or a pool, the chain is asked whether the mint or the pool already exists. If it does, the step is recorded as found on the network and nothing is sent again. The token’s address is derived from your wallet and the launch record, so a retry cannot create a second token.
- RPC trouble. When the endpoint is rate limited or unreachable, pages say so and nothing is assumed. Try again shortly.
Network status
Read live from this deployment.
The $DAXA token
$DAXA has no contract address yet. The site shows CA: SOON and prints no address of any kind until there is one; when there is, it is published on the landing page, here, and announced on the project’s X account. An address offered anywhere else as $DAXA before that is not DaxaPad’s.
- DaxaPad does not use the token. Launching a token here does not need $DAXA, no fee is paid in it, and holding it changes nothing on this site.
- Nothing is claimed about it. No supply, price, allocation or purpose is stated beyond what can be read from the chain once the token exists.
- How the address gets here. The operator runs
pnpm token:ca <mint>, which checks that the address is a token mint on mainnet-beta with the expected symbol, records what the chain answered, and only then writes it into the site.
Limits and what is not built
- Name up to 32 bytes, symbol up to 10 characters, description up to 600 characters, decimals 0 to 9, supply up to the network’s 64-bit limit.
- Up to 8 allocation recipients. Allocations are transfers: DaxaPad offers no vesting, lock-up or escrow.
- Classic SPL Token only. Token-2022 mints can be inspected but not created here.
- One liquidity route (Raydium CPMM, paired with SOL). No bonding curve, presale or fair-launch mechanism, and no in-app swap: a token with a pool links out to Raydium’s interface where one serves the network.
- No historical charts, holder lists or trade feeds.
- Changing or revoking an authority after creation is not offered in the app.
- Community missions and rewards are not built.
Questions
- What does DaxaPad create?
- A token on Solana: a mint account under the classic SPL Token program, its Metaplex Token Metadata account, your own token account, and the whole supply minted to your wallet. That is one transaction, signed by your wallet.
- If you asked for them, a second transaction sends the allocations you declared, and a third opens a Raydium CPMM pool with the tokens and SOL you chose. DaxaPad also publishes a project page for the token once its creation is confirmed and read back from the chain.
- Is token creation the same as creating liquidity?
- No. They are separate transactions and you choose whether there is a second one. The “Token only” route ends when the token exists, and its page says “Token created”: there is no market for the token until someone makes one.
- The “Raydium CPMM pool” route adds a transaction that opens a constant-product pool with your tokens and your SOL. That pool sets the first price. DaxaPad has no bonding curve of its own and no automatic migration; it creates no financial contract.
- Which network is being used?
- This site is set to Solana mainnet-beta. The active network is shown in the navigation bar on every page, and every explorer link points at that network.
- Transactions here spend real SOL. A separate devnet or local configuration exists for testing, and records made there are never listed here.
- What fees apply?
- Solana’s network fee for each transaction; rent deposits for the accounts a launch creates (the mint, your token account, the metadata account, and for a pool the pool’s accounts); the Metaplex program’s own fee for creating a metadata account; and, on the pool route, Raydium’s pool creation fee, which is read from the protocol’s account on the chain and shown before you sign.
- DaxaPad charges a platform fee only when the operator of this deployment has configured one. When none is configured it charges nothing. Either way the review screen lists every amount, marks each as exact, measured or estimate, and names the deposits that can come back.
- Which authorities can be changed or revoked?
- Three, each chosen separately when you create the token. Mint authority: give it up in the creation transaction, so the supply can never grow, or keep it. Freeze authority: set none, so token accounts can never be frozen, or keep it. Metadata update authority: create the metadata immutable, or keep it mutable.
- Giving one up is permanent. Keeping one leaves it with your wallet, and you can still give it up later with any tool that speaks the SPL Token or Metaplex programs; DaxaPad itself sets them at creation only. A token page always shows what the chain says now.
- Does DaxaPad hold private keys?
- No. DaxaPad never asks for, sees or stores a private key or a seed phrase. Its server builds an unsigned transaction, your wallet signs it, and the server relays the signed bytes only if they are the transaction it prepared.
- Signing in is a signed message, not a transaction: it costs nothing and moves nothing. Funds only ever move in transactions you approve in your own wallet.
- How are project details verified?
- Every block on a token page is labelled with where it comes from. “Onchain” is read from Solana accounts: the mint, its supply and authorities, its metadata, the balances of declared recipients, the pool. “Creator-declared” is what the creator wrote: the description, the links, the names of allocations. “Third-party” is market data from an outside provider.
- The page also compares what the creator declared with what the chain shows and marks any difference. None of this is a judgement about the token. Seeing how a token is configured does not make it safe.
- What happens if a transaction fails?
- Each step is one transaction, and a transaction either happens completely or not at all. If the network rejects it, or it expires before being included, nothing moved, and that step can be prepared again.
- If the outcome is not known yet, DaxaPad says so and waits: it never sends a second transaction for a step while the first could still land. The launch record remembers every finished step, so you can leave and resume from your dashboard, and the token’s address is derived from your wallet and the launch record, so a retry can never create a second token.