SwissDLT, chain 94
SwissDLT Token Studio
Issue a fixed-supply token and fund its first market in one transaction. The launcher creates a plain ERC-20, a fresh Uniswap v3 pool and a full-range liquidity position, then locks that position permanently in a collect-only vault.
The issuance form needs JavaScript and an Ethereum-compatible wallet. Your wallet signs; the Studio never holds keys. Agents can use the MCP endpoint described below.
Reference
How the Token Studio works
The Studio issues one kind of token: a plain ERC-20 with a fixed supply, launched with a funded market on SwissDLT chain 94. One wallet-signed transaction creates the token, a fresh pool and a full-range position, and puts the position into a permanent, collect-only vault. Status: live, first release, not independently audited.
Rules every launch follows
- Fixed supply
- The whole supply is minted once at creation, with 18 decimals. The token has no owner, no further minting, no transfer tax, no blacklist and no owner switch.
- Funded liquidity
- The issuer funds both sides of the first market: tokens from the new supply and native BCTS, which the launcher wraps into WBCTS. Both sides must be funded. Budgets are maximums; unused tokens and BCTS return to the issuer in the same transaction.
- Permanent lock
- The LP position goes into a vault with no principal exit, approval, upgrade or rescue function. Only accrued trading fees leave it, always to the fee beneficiary fixed at creation. Assets sent directly to a vault cannot be recovered.
- Fresh pool only
- The launcher rejects every existing pool for the predicted token, including empty ones, and reverts. Nobody can set the opening price in advance.
- Optional vesting
- Part of the issuer allocation can vest linearly to the issuer, funded at creation, with no separate cliff and no revocation.
- Costs
- No platform fee. The issuer pays the BCTS liquidity budget they choose plus network gas (legacy transactions, 1 gwei). The review shows the estimated gas before anything is signed.
Issuing a token, step by step
- Connect an Ethereum-compatible wallet and switch it to SwissDLT, chain 94.
- Set the token name, symbol and total supply.
- Set the token and BCTS budgets for the pool, the trading fee tier (0.05%, 0.3% or 1%) and the fee beneficiary. Optionally vest part of the issuer allocation.
- Review the simulated transaction: supply and allocation, BCTS commitment, estimated gas, predicted token address and manifest hash. Confirm that the liquidity lock is permanent.
- Sign in your wallet. The Studio checks the receipt and the recorded token, pool, vault and position, then shows the public record.
Contracts on SwissDLT chain 94
| Contract | Address | Receipt |
|---|---|---|
| Launcher, SwissTokenStudio | 0xfaf3ef2B344388b48117D336bCCDbcA7999DECdB | Deployed at block 27'319'106, deployment transaction |
| WBCTS, wrapped native BCTS | 0x4C9204BE7d41E8b1d0f8025A60110d866C0574Ad | Quote asset of every Studio pool |
| Uniswap v3 factory | 0x3c17473e017806b1b93A406B79f2272faaA6cD99 | Deployed at block 27'317'684, deployment transaction |
| v3 position manager | 0x2E9DAA82Fa0787bb89f0e7EFfab1A2767f59Cf9d | Deployed at block 27'317'690, deployment transaction |
Built with Solidity 0.8.24 for the Berlin EVM, optimizer 200, via IR; vesting uses OpenZeppelin 4.9.6 VestingWallet. The full manifest is in contracts.json and the ABIs are in abi.json.
For agents: MCP endpoint and tools
MCP endpoint https://studio.swissdlt.tech/mcp: stateless Streamable HTTP, one JSON-RPC message per POST, no API key. Send Accept: application/json, text/event-stream. Live checks of chain, genesis, code hashes and wiring: /health. The service holds no keys and cannot sign or broadcast; every tool reads data or returns an unsigned transaction after checking the chain and simulating.
| Tool | What it does |
|---|---|
swissdlt_studio_get_info | Reads the Studio configuration, source and deployment references. Not a live health check. |
swissdlt_studio_check_health | Verifies the live chain and genesis, pinned contract code hashes and deployment wiring. |
swissdlt_studio_list_launches | Reads a bounded page of the Studio launch register. |
swissdlt_studio_read_launch | Reads one launch: token, pool, permanent LP custody and fee beneficiary. |
swissdlt_studio_prepare_launch | Prepares and simulates one unsigned, funded launch with exact budgets and a manifest digest. |
swissdlt_studio_prepare_collect_fees | Prepares an unsigned fee collection to the vault's fixed beneficiary. |
swissdlt_studio_prepare_release_vesting | Prepares an unsigned release from the token's vesting wallet to its fixed beneficiary. |
Machine-readable files
- SKILL.md: agent instructions, exact amounts and the irreversible LP policy
- llms.txt and llms-full.txt: summary and full reference
- mcp-tools.json: typed tool schemas
- mcp-client.example.json: connection example, no keys
- .well-known/mcp.json: MCP discovery descriptor
- .well-known/contracts.json and deployment.json: deployment manifest
- abi.json: contract ABIs
- tokens/catalog.json: community token pages, for example Pixel Ibex; each page reads the register live
- .well-known/thirdfy-app.json, thirdfy-features.json and thirdfy-readiness.json: Thirdfy drafts, not submitted or certified
Network
- Chain
- SwissDLT, chain ID 94 (0x5e), Clique proof of authority with six signers and 4-second blocks
- EVM
- Berlin; legacy type-0 transactions at 1 gwei, no EIP-1559
- Native coin
- BCTS, 18 decimals
- Public RPC
https://rpc.swissdlt.ch,https://rpc2.swissdlt.ch- Explorer
- explorer.swissdlt.tech
What the Studio does not claim
- First release with internal tests and review. The custom Studio contracts have not been independently audited.
- A token launched here is not an approved investment. Issuers remain responsible for identification and any offering rules before a public offering.
- No promise of price, liquidity depth, profit, market demand or redemption. The initial rate is not a valuation.
- The register records execution and custody. It does not endorse an issuer or establish a market value.
- SwissDLT's permissioned signer set still controls transaction inclusion and ordering. The upstream AMM can charge a protocol share of trading fees.
More: Token Studio on the SwissDLT website, contracts in the docs, SwissDLT for AI agents.