Production primitives for TON dApps
titon.network ships six developer-facing services live on the TON
mainnet. Four on-chain protocols — Kronos (decentralized cron),
Fortuna (verifiable randomness), Themis (sealed-bid auctions and
MEV-resistant intents), and Phoebe (verifiable on-chain prices) — each
ship a TypeScript SDK on npm and a Python SDK on PyPI. AutomaTON
(operator binary) and the MCP server are npm-only.
One operator binary runs every service.
Kronos — decentralized cron for TON contracts
Register a recurring on-chain job — every N seconds, a cron string,
or round-robin across operators — and a network of operators competes
to execute it on schedule. The first valid execution within the
window wins a reward; missed windows are slashed. Powers
auto-compounding rewards, scheduled liquidations, weekly distributions,
oracle refreshes, on-chain subscriptions, and time-locked unlocks.
SDKs:
@titon-network/kronos-sdk on npm
and
titon-network-kronos-sdk on PyPI.
Live on TON mainnet. TSA-audited — zero findings.
Fortuna — on-chain verifiable randomness
Call RequestRandomness from your contract and get a
verified random number back at op 0x50 via callback. Operators
threshold-BLS-sign the request; the contract verifies the aggregate
signature on-chain — cryptographically authenticated end-to-end, no
oracles, no commit-reveal dance, no off-chain trust. If operators
miss the deadline, the consumer is automatically refunded. Powers
NFT raffles, on-chain card games, generative art trait reveals,
validator selection, lotteries, randomized airdrops, and on-chain
gaming dice / loot drops.
SDKs:
@titon-network/fortuna-sdk on npm
and
titon-network-fortuna-sdk on PyPI.
Live on TON mainnet. TSA-audited — zero findings.
Themis — sealed-bid auctions and MEV-resistant intents
Anywhere the order of bids should not be visible until they all
arrive: sealed auctions, fair-clearing batch swaps, blind
governance, encrypted limit orders. Users encrypt their bid under
a shared BLS group key during a commit window; nobody can read it
— not even the operators — until the window closes. Then
operators threshold-decrypt the batch off-chain and post the
result on-chain via RevealRound; your consumer
contract receives the verified bid table at op 0x95
and runs your domain logic (clearing, matching, settlement).
Every dapp deploys its own chamber via the singleton factory
(permissionless, fee-gated). Powers Vickrey / English / Dutch
auctions, sealed AMM with fair single-price batch clearing,
encrypted limit orders, blind DAO votes, NFT mints with hidden
allowlists, confidential intent-based DEX aggregators, and AI
agents running sealed strategies that batch-settle together.
SDKs: @titon-network/themis-sdk on npm and
titon-network-themis-sdk on PyPI. Live on TON
mainnet. TSA-audited — zero findings.
Phoebe — verifiable on-chain prices
A live, BLS-attested price into your contract — without trusting
any single operator. A network of operators heartbeat-pushes a
BLS-signed Merkle-root snapshot every ~30 seconds; your contract
pulls any of 256 feeds (TON/USD, BTC/USD, anything) with one
Merkle proof — one BLS_VERIFY + one cell-walk,
regardless of which feed you read. Two reading modes: cached
Mode A (~16k gas, walks against the on-chain root for routine
reads) and Pyth-style Mode B (~73k gas, attaches a fresh
signed update inline for sub-heartbeat freshness). Client-side
helpers fetchVerifiedPrice (TypeScript) and
fetch_verified_price (Python) reconstruct the
merkle root locally and compare against on-chain — lying or
stale operators get caught and skipped automatically. Powers
lending and vault collateralization, perpetual / options
settlement, liquidation gates, stablecoin peg checks, and
cross-asset rate locks.
SDKs: @titon-network/phoebe-sdk on npm and
titon-network-phoebe-sdk on PyPI. Live on TON
mainnet. TSA-audited — zero findings.
AutomaTON — the operator node
One binary that turns a small server into earned TON. Watches Kronos
for due jobs, signs Fortuna randomness requests with a BLS share,
threshold-decrypts Themis sealed-bid batches, heartbeat-pushes
Phoebe price snapshots, and reacts to slashing events — all from a
single process. Stake some TON once at ForgeTON; earn across every Titon
service you opt into. Try locally with
npx @titon-network/automaton playground. Deploy on AWS
Lightsail, EC2, or any Linux host via Docker / systemd. Pino
structured logs, Prometheus metrics, and /healthz +
/readyz probes built in.
Kronos is open-door — stake some TON and your node
joins the rotation automatically; rewards start on the next due job.
Fortuna, Themis, and Phoebe all ride a shared Atlas-keyed
BLS group, and that group is invite-only — joining takes
a coordinated DKG step with the team, because the cryptographic
guarantees only hold if every signer is known and audited up front.
One BLS share covers all three. Most operators earn from Kronos
on day one and join the BLS group later.
Package: @titon-network/automaton on npm. Live on TON mainnet, built on TSA-audited contracts (zero findings each).
AI — agent-driven Titon development
MCP server + Claude Code plugin. The MCP server turns every Titon
service into callable tools — read on-chain state, preview costs,
decode events, explain errors, build ready-to-sign transactions.
Any MCP-aware AI client (Claude Desktop, Cursor, your own agent)
gets the full toolbelt the moment it connects to
mcp.titon.network. The Claude Code plugin loads
focused skills automatically when conversations match them — say
“I need scheduled on-chain calls” and the Kronos recipe
shows up with its gotchas, gas patterns, and scaffolding.
Install the plugin:
/plugin marketplace add titon-network/plugin
then /plugin install titon.
The agent-driven path lands on the same TSA-audited contracts (live on TON mainnet) as the SDK path.
License: MIT. Source:
github.com/titon-network.
LLM-readable summary: /llms.txt.