titon.network is live on TON mainnet.
Four production primitives for TON dapps. All TSA-audited (zero findings each). SDKs in TypeScript and Python. MIT-licensed throughout.
Kronos — decentralized cron for TON contracts. Register a recurring on-chain job (interval / cron / round-robin / consensus); operators compete to execute on schedule. First valid execution wins a reward; missed windows are slashed. Auto-compounders, scheduled liquidations, oracle refreshes, vesting unlocks.
Fortuna — on-chain verifiable randomness via threshold-BLS. Call
AutomaTON — the operator node binary. One process. Stake once on ForgeTON (the shared-security pool that backs every Titon service), opt into Kronos and Fortuna, earn TON across both.
AI surface — MCP server at [mcp.titon.network](https://mcp.titon.network) plus a Claude Code plugin marketplace. Every Titon service exposed as callable tools (read state, preview costs, build wallet-ready transactions). Tell an AI agent what you want to build; the MCP gives it the tools to actually build it.
Operator permission model
Kronos rewards are open to anyone who stakes — your node joins the rotation automatically, no waiting list. Fortuna VRF group is invite-only because the randomness only stays unbiased if every signer is known and audited up front. Most operators earn from Kronos on day one and add Fortuna later.
Try it locally — no faucet, no wallet, no real TON, ~30 seconds
Boots an in-process sandbox blockchain, deploys the full Titon stack, runs a demo operator that earns from both Kronos automation and Fortuna VRF fulfillments.
Production paths from the same binary
AWS Lightsail (testnet hobbyist), AWS EC2 with SSM-backed secrets (mainnet production), Docker via the public ECR image, systemd unit, or from source.
Links
- Site: https://titon.network
- Source: https://github.com/titon-network
- MCP endpoint: https://mcp.titon.network
- Claude plugin:
- npm SDKs: https://www.npmjs.com/org/titon-network
- PyPI: titon-network-kronos-sdk + titon-network-fortuna-sdk
Built for dapp authors. Ship the app, not the plumbing.
Four production primitives for TON dapps. All TSA-audited (zero findings each). SDKs in TypeScript and Python. MIT-licensed throughout.
Kronos — decentralized cron for TON contracts. Register a recurring on-chain job (interval / cron / round-robin / consensus); operators compete to execute on schedule. First valid execution wins a reward; missed windows are slashed. Auto-compounders, scheduled liquidations, oracle refreshes, vesting unlocks.
Fortuna — on-chain verifiable randomness via threshold-BLS. Call
RequestRandomness from your contract; get a verified random number back at op 0x50 via callback. Operators threshold-BLS-sign together; the contract verifies the aggregate on-chain. No oracles, no commit-reveal, no off-chain trust. NFT raffles, on-chain card games, lotteries, randomized airdrops.AutomaTON — the operator node binary. One process. Stake once on ForgeTON (the shared-security pool that backs every Titon service), opt into Kronos and Fortuna, earn TON across both.
AI surface — MCP server at [mcp.titon.network](https://mcp.titon.network) plus a Claude Code plugin marketplace. Every Titon service exposed as callable tools (read state, preview costs, build wallet-ready transactions). Tell an AI agent what you want to build; the MCP gives it the tools to actually build it.
Operator permission model
Kronos rewards are open to anyone who stakes — your node joins the rotation automatically, no waiting list. Fortuna VRF group is invite-only because the randomness only stays unbiased if every signer is known and audited up front. Most operators earn from Kronos on day one and add Fortuna later.
Try it locally — no faucet, no wallet, no real TON, ~30 seconds
npx @titon-network/automaton playground
Boots an in-process sandbox blockchain, deploys the full Titon stack, runs a demo operator that earns from both Kronos automation and Fortuna VRF fulfillments.
Production paths from the same binary
AWS Lightsail (testnet hobbyist), AWS EC2 with SSM-backed secrets (mainnet production), Docker via the public ECR image, systemd unit, or from source.
Links
- Site: https://titon.network
- Source: https://github.com/titon-network
- MCP endpoint: https://mcp.titon.network
- Claude plugin:
/plugin marketplace add titon-network/plugin- npm SDKs: https://www.npmjs.com/org/titon-network
- PyPI: titon-network-kronos-sdk + titon-network-fortuna-sdk
Built for dapp authors. Ship the app, not the plumbing.
🚀 Big news for TON builders!
titon.network launched exactly what we’ve been missing.
Dropped two super useful primitives:
Kronos → decentralized cron (real scheduled on-chain jobs)
Fortuna → verifiable on-chain randomness (threshold-BLS, no oracles)
No more sketchy off-chain solutions. Everything is audited, open-source, and actually production-ready.
What you can build right now:
✨ Auto-compounding vaults that pay rewards on schedule
✨ Fair NFT raffles and randomized airdrops
✨ On-chain games with true randomness
✨ Weekly distributions, subscriptions, or timed unlocks
✨ Scheduled liquidations and oracle refreshes
Basically, all the features users actually love.
titon.network launched exactly what we’ve been missing.
Dropped two super useful primitives:
Kronos → decentralized cron (real scheduled on-chain jobs)
Fortuna → verifiable on-chain randomness (threshold-BLS, no oracles)
No more sketchy off-chain solutions. Everything is audited, open-source, and actually production-ready.
What you can build right now:
✨ Auto-compounding vaults that pay rewards on schedule
✨ Fair NFT raffles and randomized airdrops
✨ On-chain games with true randomness
✨ Weekly distributions, subscriptions, or timed unlocks
✨ Scheduled liquidations and oracle refreshes
Basically, all the features users actually love.
TON Devs & AI Builders!
Tired of sketchy randomness breaking your on-chain AI agents?
Fortuna VRF is LIVE on mainnet — true verifiable on-chain randomness with zero trust.
One contract call → cryptographically proven random number delivered via callback. No oracles. No commit-reveal. Fully audited.
This is rocket fuel for AI agents:
• Unpredictable yet provably fair decisions & exploration
• Stochastic behaviors in autonomous agents
• Fair AI-generated NFTs, loot & reward systems
• Randomized simulations & multi-agent coordination
Build 10× faster: skip the infra, let our Claude plugin + MCP literally code the integration for you.
Try it instantly
titon.network
Tired of sketchy randomness breaking your on-chain AI agents?
Fortuna VRF is LIVE on mainnet — true verifiable on-chain randomness with zero trust.
One contract call → cryptographically proven random number delivered via callback. No oracles. No commit-reveal. Fully audited.
This is rocket fuel for AI agents:
• Unpredictable yet provably fair decisions & exploration
• Stochastic behaviors in autonomous agents
• Fair AI-generated NFTs, loot & reward systems
• Randomized simulations & multi-agent coordination
Build 10× faster: skip the infra, let our Claude plugin + MCP literally code the integration for you.
Try it instantly
titon.network
Themis and Phoebe are live on TON mainnet
Big update — two new production primitives just shipped, and they unlock a whole class of dApps that were hard to build on TON until now.
Themis — sealed-bid auctions & MEV-resistant intents
Anywhere the order of bids shouldn't 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. Your consumer contract receives the verified bid table and runs your domain logic: clearing, matching, settlement.
Every dApp deploys its own chamber via the singleton factory — permissionless, fee-gated.
Use cases: Vickrey / English / Dutch auctions, sealed AMM with single-price batch clearing, MEV-resistant batch DEX swaps, encrypted limit orders, blind DAO votes, NFT mints with hidden allowlists, intent-based DEX aggregators.
Phoebe — verifiable on-chain prices
A live, BLS-attested price feed 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: — Mode A (cached, ~16k gas) — walks against the on-chain root, great for routine reads — Mode B (Pyth-style, ~73k gas) — attaches a fresh signed update inline for sub-heartbeat freshness
Client-side helpers reconstruct the Merkle root locally and compare against on-chain, so lying or stale operators get caught and skipped automatically.
Use cases: lending and vault collateralization, perpetuals and options settlement, liquidation gates, stablecoin peg checks, cross-asset rate locks.
The details
Both services are TSA-audited — zero findings. SDKs are live on npm (
Together with Kronos (decentralized cron) and Fortuna (verifiable randomness), TON developers now have the full primitive set to ship serious DeFi, gaming, and intent-based apps — without rebuilding the plumbing.
Docs, examples, and the MCP server for AI-driven development: titon.network
Building something? Open an issue on GitHub and we'll feature it.
Big update — two new production primitives just shipped, and they unlock a whole class of dApps that were hard to build on TON until now.
Themis — sealed-bid auctions & MEV-resistant intents
Anywhere the order of bids shouldn't 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. Your consumer contract receives the verified bid table and runs your domain logic: clearing, matching, settlement.
Every dApp deploys its own chamber via the singleton factory — permissionless, fee-gated.
Use cases: Vickrey / English / Dutch auctions, sealed AMM with single-price batch clearing, MEV-resistant batch DEX swaps, encrypted limit orders, blind DAO votes, NFT mints with hidden allowlists, intent-based DEX aggregators.
Phoebe — verifiable on-chain prices
A live, BLS-attested price feed 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: — Mode A (cached, ~16k gas) — walks against the on-chain root, great for routine reads — Mode B (Pyth-style, ~73k gas) — attaches a fresh signed update inline for sub-heartbeat freshness
Client-side helpers reconstruct the Merkle root locally and compare against on-chain, so lying or stale operators get caught and skipped automatically.
Use cases: lending and vault collateralization, perpetuals and options settlement, liquidation gates, stablecoin peg checks, cross-asset rate locks.
The details
Both services are TSA-audited — zero findings. SDKs are live on npm (
@titon-network/themis-sdk, @titon-network/phoebe-sdk) and PyPI (titon-network-themis-sdk, titon-network-phoebe-sdk).Together with Kronos (decentralized cron) and Fortuna (verifiable randomness), TON developers now have the full primitive set to ship serious DeFi, gaming, and intent-based apps — without rebuilding the plumbing.
Docs, examples, and the MCP server for AI-driven development: titon.network
Building something? Open an issue on GitHub and we'll feature it.