BELL Protocol DEMO FEED

The market never
closes.

Millions of markets move every second. BELL tells the world when something matters.

Create a Bell
RingsToday
28,491 +412 (1.5%)

Compared to yesterday

Oracle quorum reached

$
Live Rings UTC

bell://registry --follow

01 — The problem

The problem was never a lack of data.

A modern market produces millions of datapoints every second. Prices move. Liquidity shifts. Volatility spikes. Prediction odds change. Tokenized assets trade around the clock. Autonomous agents watch all of it, continuously, at enormous cost.

None of that is scarce. What is scarce is knowing when something matters — and having that moment arrive in a form other systems can act on. BELL does not add another feed. It sits on top of every feed and decides which moments deserve a signal.

Wall Street had one Bell. The internet needs millions.

The modern bell rings when something happens

Old finance

One market. One bell. One schedule.

≈ 504 rings a year, across 252 sessions, on a single floor.

Onchain finance

Millions of markets. Millions of conditions. Millions of bells.

No opening. No close. 24 / 7 / 365.

02 — The language

A Bell. A Ring. A Ringer.

Five words the protocol runs on. Used consistently, they turn an abstract protocol into objects people can name, create and own.

03 — What can ring

Anything observable can Ring.

A Bell watching only price would be a price alert, and price alerts already exist. Every observable property of a market can carry a condition — and they compose.

IFBTC/USD > $150,000
ANDVolume > 2× average
ANDETF inflows positive
ANDVolatility < 5%
RING

One Bell. Four conditions. One event.

A breakout on thin volume during a volatility spike is not the same event as a breakout on heavy volume in a calm tape. A price alert cannot tell them apart. A composite Bell can, and it rings once — for the situation, not the number.

That is programmable market logic.

04 — How it works

Data becomes events.

Markets→ Oracles→ Bell engine→ Ring registry→ Ring→ Human · App · Agent

Market data arrives from venues, exchanges, issuers and pools. Independent oracle operators report what they observe, and nothing becomes fact until a quorum agrees — nothing Rings on a single source.

The Bell engine holds every armed Bell and evaluates it against verified data. When a condition is met, the registry records it and a Ring is emitted, once, in a single shape. BELL is the layer between market data and everything that acts on it.

05 — Agents

Agents don't watch markets. They listen for BELL.

An agent can analyze and it can act. What it cannot do cheaply is stay awake. Polling thousands of datapoints every second is expensive, noisy and always slightly late — and almost everything it reads is nothing happening.

A Ring tells an agent when to wake up. One event, one schema, one definition of "it happened", shared across every venue it touches. The agent spends its budget on judgment instead of surveillance.

Market→ Bell→ Ring→ Wake agent→ Analyze · decide · act

06 — The token

$BELL coordinates the network that decides what is worth ringing.

Most tokens launch first and look for utility afterwards. The order here runs the other way.

First

Product

Something people can open and use. A condition builder, a live registry, a working terminal.

Then

Network

Operators reporting data, a registry storing events, and decisions about which markets come next.

Only then

Token

Fees, stake behind attested events, governance, and incentives for the builders the network consumes.

Every function carries its real stage in public — live, in design, planned. Nothing here is live yet, and all figures on this page come from a demo feed, not live market data.

Est. 1903 · Ringer, retired

He rang twice a day for 100 years. Then he discovered crypto.

"You guys never close?"

— BELL, 03:41 on a Sunday

RING FOREVER