OneNess TOR node.
Real chain. Real AI.
A Rust ledger with an Ed25519 wallet core, a Python API that speaks every endpoint, and a local Ollama brain that calls those endpoints for you. Payments, Rust contracts, meme launches and AI-NFTs — all settled in TOR, on one node.
genesis mints 50,000,000 TOR into the founder wallet · public records expire after 30 days, the chain keeps them privately
Ollama command deck
Ask in English. The model reads the live schema, calls the real endpoints and shows the request + response it used.
fetch_oneness_dataExplorer
Blocks, records, accounts and supply verification straight from the Rust node.
30-day windowWallets
Phantom-compatible Ed25519 keys, live balances, signed transfers and offline signing.
ed25519Payments
Invoices for every LOCKED price — contract 5, mint 3, transfer 0.1 — paid on-chain.
0.1 TOR transfer fee
Rust contracts
Templates compile with rustc before they are stored; only authorized
nodes may deploy.
Model manager
Install Ollama, pull models with live progress, ollama run <model>
from the browser.
Live chain
- chain id
- 072316
- height
- 3,021
- head
- c43d392e597666…33468a
- genesis
- fc9a220ce910b0…f6e156
- fee receiver
- TOR12xd7zywc3iuwcls3fqzsozkgo5ahv3gnonion
- public window
- 30 days
- coin
- OneNess TOR · TOR
Settlement
Every price comes from /api/pricing; every charge is a signed transfer to the node's fee receiver, visible in the explorer.
How the node is put together
Rust torchain owns balances, tokens, pools and the permanent record.
Flask exposes every endpoint once and documents itself at /api/docs.
Ollama receives the schema + a live snapshot, then calls the API with one tool.
Payments, contracts and meme launches settle on-chain before they are served.