Guide · Reader’s desk
How an edition gets published.
Short answers to the questions that matter before you sign anything.
01
What Muse does
Muse is the newsroom assistant. It keeps your draft on this device, stores your artwork and metadata before anything is sent, reads the live terms of the launch route you chose, simulates the exact transaction, and shows you the result to review.
Muse does not hold keys, does not sign, and cannot spend. If an “Ask Muse” button is shown, it calls a server-side language model for name, symbol and description ideas; the suggestions are text you can edit or ignore, and they never change a reviewed transaction. When no model is configured the button says so instead of pretending.
02
Who signs transactions
You do, in your wallet, every time. Connecting a wallet only shows your address to the page. Switching network is requested through the wallet. The launch itself is one transaction whose contract, function, arguments and value you see on the review sheet and again in the wallet prompt.
Signing in to My Desk is an optional, free message signature that proves you control the address; it is used only to keep your pending submissions on the server. It moves nothing.
03
Deployment versus trading availability
Deploying an ERC-20 does not make it tradable. A token only trades where a market exists for it.
Token deployment (MusePaper factory): Deploys an ERC-20 with the supply you choose, minted in full to the recipient you review. It does NOT create a trading pool, add liquidity or start a sale; the token is not tradable anywhere until someone creates a market for it separately.
Pons V2 launch (Pons V2 contracts (third party)): Deploys an ERC-20 with a fixed supply set by the protocol’s launch configuration, creates its bonding curve, and opens trading on that curve. When the curve reaches its graduation threshold the protocol moves liquidity to a Uniswap v4 pool.
Edition pages show a trading venue only when the route created one on-chain. Price and volume read “Unavailable” unless a real data source is integrated; MusePaper never shows a zero it did not measure.
04
Fees and estimates
Two kinds of cost appear on the review sheet, separately.
Creation fee: read live from the destination contract at review time. The MusePaper factory charges none by default; the Pons V2 factory charges its current launch fee. Both are sent as the transaction value and the contract rejects any other amount.
Network fee: an estimate (gas × current price) refreshed right before you authorize. The wallet shows its own figure; the chain settles the real one.
Any liquidity contribution or opening buy would be listed as its own line. In this release no route asks for one.
05
Token permissions
Tokens deployed through the MusePaper factory are plain, fixed-supply OpenZeppelin ERC-20s: no mint function, no owner, no transfer tax, no blacklist, no pause, no upgrade path. The whole supply is minted once to the recipient you review. The factory owner can only change the factory’s own fee; it has no power over any token.
Pons V2 tokens are created by the protocol’s launch deployer with the supply fixed by its launch configuration; the creator sets a creator tax (0 through MusePaper) and receives creator fees from curve trades. The protocol owner can change terms for future launches only: the terms you reviewed are pinned into your transaction and it reverts if they change.
06
Current network availability
This deployment
- Network
- Robinhood Chain · mainnet
- Chain id
- 4663
- Environment
- mainnet
- Confirmations before “published”
- 12
Robinhood Chain mainnet (chain 4663) is the production target; the Pons V2 route is verified there. The MusePaper factory is enabled on mainnet only once an operator deploys it and publishes the address; until then the route reports itself unavailable. A local Anvil chain (31337) exists for development and tests; nothing on it is a real launch, and the site labels it as a test network everywhere.
Live status for each route, the RPC and the index is on the desk and in the colophon of every page.
07
How to recover a pending or failed launch
Open My Desk. Every transaction hash the wallet returned is saved on this device the moment it is returned, and re-checked against the chain when the page opens.
“Submitted” or “Confirming” means the chain has not finalised it yet; leave the page open or come back. Nothing can turn it into “Published” except a confirmed receipt with the creation event.
“Failed” means the transaction reverted: only the network fee was spent and no token exists. Fix the reason shown and authorize again; the draft keeps its edition key, so a retry can never create a second token by accident.
“Dropped” means the network never included it (replaced or evicted by the wallet). Check the wallet’s activity; if a new hash exists, register it from My Desk.
If the site loses contact with the RPC, the edition still exists on-chain; the transaction hash and the explorer link are all you need to prove it.