NETWORK ORACLES — WORKSHOP 1 / 3
All changes saved
Network Oracles · workshop

Join your
group.

Type your group name. If it already exists, you'll pick up exactly where your group left off — otherwise you start a fresh canvas. Everything you type saves automatically.

01

What is a network oracle?

Make a network function available through a protocol, as a decision rather than a data dump. The reference example, plus a few more — and where it could go.

A borrowed word. Strictly, "oracle" is Web3: it becomes one only when the answer is consumed on-chain. We use it for the wider pattern, because the property that matters — a verifiable answer instead of raw data — is the same in every layer.
PATH A · DIRECT

Consume the API as-is. Same spec at every operator, cheap to integrate, increasingly commoditised — that is the point of CAMARA.

Example: DT × Fireblocks — one Number Verify call replaced a ~50-click onboarding.
PATH B · COMPOSED

Buy the operator's composite. The operator owns the logic, weights and policy — the decision is the product, and the margin.

Example: Mobile Trust Score — six fraud signals composed into one score with tiers.

Both are valid in Part 2 — a strong use case can need one API, or six.

The reference example, and others

Where this could develop

02

The network API landscape

CAMARA — open source in the Linux Foundation, in collaboration with GSMA — defines one common spec per network capability: questions (SIM swapped? number verified?) and actions (quality on demand), the same at every operator, taken to market through GSMA Open Gateway. TMForum Open APIs are the standard for the whole telecom IT stack (BSS/OSS) — dozens of Open APIs, the interface contracts of the Open Digital Architecture; in this workshop we use only the small commerce subset that stands up a service end-to-end. Tap + use to add an API to your scenario. Statuses indicative — verify on camaraproject.org.

03

Your scenario

Five steps. Everything autosaves to your group as you type — anyone on your group's link sees the same canvas, and it shows up live on the room screen.

💳

Low-friction mobile payments

4 APIs · REST + On-chain

⚡

Decentralised service activation

4 APIs · Attestation + On-chain

📱

Mobile Trust Score

6 APIs · REST + On-chain

or build your own
Give your scenario a short, memorable name
Who are the actors? (end user, app/platform, relying party)
What problem does this solve? Why would someone pay for it?
What signals must the network provide? What decision does it enable?
Pick from popular APIs above, browse the dropdown, or use the explorer in section 02. One API can be enough — or compose several.
REST — adds a live answer over one HTTPS call; solves fraud checks inside live flows
Attestation — adds a signed credential the user re-presents; solves verify-later/elsewhere without calling the operator every time
On-chain — adds an oracle writing the answer where contracts can read it; solves contracts can't call REST
ZK — adds predicate proofs (tier ≥ TRUSTED, age ≥ 18); solves verification without exposing the score, the number, or the person
ADMIN LOGIN 🔒

Enter the admin password to access the control panel.

⚠ RESET ALL GROUPS

This will permanently delete all groups and their work. This cannot be undone.

Type RESET to confirm:

Who?  ·  Why?  ·  Which APIs — one or many?  ·  Produces what, on-chain or off?
★

All groups 0

Live view of every group's canvas — refreshes on its own as groups type. Hit present for the room.

Untitled scenario 0 APIs ▲