Architecture
How TON618 is built.
TON618 is a single system with three parts: the SI, the account layer that handles identity and payments, and the launch engine.
Wallet +-----------------------------+ Solana
(Sign In With -----> | Account layer | <----- (finalized reads)
Solana) | identity . credits . burns |
+------+---------------+------+
| |
v v
+-----------------+ +---------------------+
| The SI | | Launch engine | -----> Meteora
| own model, | | rounds . scoring | (deploy . fees)
| own servers | | launch . payout |
+-----------------+ +---------------------+
Identity
- Sign In With Solana (SIWS). You sign a standard, human-readable message with a single-use nonce. The server verifies the ed25519 signature. No passwords exist anywhere in the system.
- Sessions are signed, HTTP-only cookies that page scripts can't read, valid for 7 days. A change to the Terms invalidates every session until the new terms are signed.
The SI
- Own model, own servers. No third-party AI API sits in the request path.
- Metered gateway. Every prompt passes through a billing gateway that checks the session, deducts one credit or applies Nucleus, and streams the answer back. A prompt that fails is never charged.
- Images. The chat's Image button uses Qwen-Image 2.1 on the same GPU servers. Each image goes through the same gateway and costs one credit.
- One prompt at a time per wallet, so a balance can't be overdrawn.
Payments
Every payment, for credits or for a launch, is verified server-side, directly from Solana:
| Check | |
|---|---|
| Commitment | finalized only. A credited payment can never be rolled back. |
| Signer | The signed-in wallet must have signed the transaction. |
| Asset | The $TON618 mint, with SPL Token and Token-2022 supported. |
| Amount | Read from on-chain balance changes, never from the browser. |
| Recipient | The correct treasury. |
| Replay | Each transaction is accepted exactly once. |
| Age | Old transactions can't be claimed. |
The browser never tells the server what was paid; the chain does.
Launch engine
- Rounds run on a fixed two-hour clock.
- Scoring: the SI scores each idea for virality, timeliness (from live trending data), completeness and pitch quality, and re-scores after every pitch message.
- Deployment: the winning idea's metadata and image are pinned to IPFS and the coin is created on Meteora's Dynamic Bonding Curve, paired with $TON618, from a dedicated launch wallet. Creator fees are claimed in $TON618 straight to the idea's wallet.
- Exactly-once launches: a round is locked before launching, and before any retry the engine checks on-chain whether the coin already exists, so a round can never launch twice.
- Fee loop: creator fees are claimed on-chain and forwarded in SOL to the winning wallet, with every claim and payout recorded.
Stack
| Layer | Technology |
|---|---|
| Web | Next.js, React, TypeScript |
| Rendering | WebGL ray-traced black hole (three.js), adaptive quality |
| Data | PostgreSQL |
| Chain | Solana, @solana/web3.js, SPL Token |
| Launches | Meteora Dynamic Bonding Curve, IPFS |
| Edge | Cloudflare, Caddy |