Coin creation & Creator rights
On this page · 4 sections
In short: The current website features and lists coins selected by the operator. It currently shows $BLESSED only; it does not offer an open self-service launch entry from the home page. Creating a coin does not guarantee that it will appear on the website.
This chapter explains the template's creation flow and existing Creator rights. It is not an announcement that public launches are open. Creation depends on the deployed factory's current settings and requirements; website selection does not change those contract rules.
Creation flow when available
- Pick a company from the registered list. This can't be changed later.
- Choose a name and ticker. They don't have to be unique, so buyers should check a coin's registry ID.
- Choose Creator fees on or off (off by default). This can't be changed later.
- Review and create. Check the prepared image and optional X, Telegram and Website links. One wallet confirmation creates your coin and approves its initial image and links together. The launch sale opens with the platform's standard terms.
- Watch the save finish. The image and links save automatically after creation, with no additional wallet signatures. The completion screen reports coin creation and metadata saving separately.
Creator rights
- No free tokens. If you want the coin, buy in the launch sale like everyone else.
- No control over the coin's Treasury, stock reserve or rules.
- Creator fees, if on:
| Income | Creator share |
|---|---|
| Trading tax | 10% of the tax (0.30% of each trade at a 3% tax) |
| Discounted-buy premium | 3% |
| Launch-sale fee | none |
Creator fees aren't sent automatically: they're claimed by the fee wallet, and they can be zero if nobody trades. The fee wallet can hand future income to a new wallet. If the fee wallet is lost, the operator can move future income to a new one. Amounts already owed stay with the old wallet.
Image and links
An image is optional. Choose a PNG, JPEG or WebP up to 2 MiB. Before you approve the launch, the form prepares a square WebP without embedded metadata. The published bytes must fit within 256 KiB; otherwise choose a simpler image. The form saves the exact image, links and compact JSON on your device. The creation transaction approves that content and fixes its IPFS JSON URI in the factory; the token holds no image or URL. After the receipt is verified, the image and JSON are pinned to public IPFS without another signature or transaction. Without an image, the initial URI stays empty.
If saving fails or its reply is unknown, Try saving again checks or finishes the same save. It does not create another coin or ask for another signature. Reload on the same device and reconnect the creator account to resume from the saved content. An image failure does not stop link saving.
The image can be set once and cannot be replaced. Community links can be edited or deleted later with one explicit creator signature. Resending initial metadata never rolls back later edits.
Optional image recovery
If the original content is unavailable and no image has been accepted, choose Recover image with creator signatures on the completion screen. A verified coin page also offers Set image. This optional path uses two offchain signatures: permission to upload that file, then permanent setting of its CID and version 1. It costs no transaction gas. The first image accepted by either method is permanent. If another save won first, the existing image is preserved. The public record identifies whether the image was approved by the creation transaction or creator signatures. Older coins without initial transaction approval use the signature path. A nonempty external URI cannot be changed by recovery: its JSON keeps the image chosen at creation, while the website can show the recovered image. The external JSON also keeps the initial links; later website link edits do not rewrite it. External metadata may remain unavailable until the original content is pinned.
Contract account creators, including Safe: normal commitment-matching saving needs no ERC-1271 signature. Optional recovery needs signatures accepted by the recorded creator contract through ERC-1271; an owner's individual EOA signature is not automatically a signature of the Safe. Prepare those signatures outside this screen:
- Upload:
POST /api/coin-images?chainId=&factory=&coinId=&deadline=&signature=with the original image bytes. SignCoinImageUpload(address factory,address token,bytes32 imageHash,uint256 deadline), binding the registry's TOKEN, SHA-256 of the original bytes and a deadline no more than 10 minutes ahead. - Set: read
GET /api/coins/{chainId}/{factory}/{coinId}/image, then signCoinImage(address factory,address token,string cid,uint256 version)with version 1. POST{ token, cid, version, signature }to the same path.
Both recovery signatures use the EIP-712 domain { name: "Umbrella Launchpad Coin Image", version: "1", chainId }. The server checks ERC-1271 at the acceptance block. The public image record lists accepted versions, approval sources and image-hide records; it does not list an official catalogue's initial image.
Good to know
- Coins can target a company whose stock isn't tokenized yet. But if the reserve buys no stock within 90 days after trading opens, anyone can wind the coin down.
- If a sale fails, buyers can claim refunds under its terms. A later launch is a separate action subject to the factory's current settings and requirements.
- A coin can have a verified detail page after creation. Official selection, Discover indexing and Treasury totals are separate; inclusion is not a guarantee of value, returns or future stock purchases. A coin's absence from the home page does not remove existing contract rights.
$BLESSED is excluded from the 90-day wind-down.