Ledger validators
Cities and companies with standing can be ledger validators — the record is kept by the networks, not over them.
In build · roadmap
Enterprise · Network governance
Rules, not discretion.
Who enters, how they operate, how they're sanctioned, and how they exit is defined by public, defined rules — not by anyone's judgment in the moment. Enforcement is one thing and transparent: renewing, or not, the dispatch authorization. And every decision is recorded in the ledger.
Single enforcement lever
Authorize, or don't
Enforcement is one thing, and it's transparent: renewing — or not — the dispatch authorization. There is no hidden second mechanism.
Why it binds both sides
Governance is bilateral — it binds us too. Every decision, entry, sanction, and exit is recorded in the ledger as immutable, auditable evidence. The rules are public, so the same standard applies to the network and to the operators on it.
Onboarding without arbitrariness
Four verifiable requirements — then activation is automatic.
There is no discretionary "permission" in between. Meet four verifiable requirements and the node activates on its own — nobody gets to decide otherwise on a whim.
- requirement
Legal identity
A verifiable legal entity behind the operator — who you are, established before anything else.
- requirement
Network contract
The signed terms that bind the operator to the network's public rules — and bind the network back.
- requirement
Technical node conformance
Your node meets the protocol's technical conformance bar, so it speaks the network's language correctly.
- requirement
Minimum capacity
A baseline operating capacity, so an activated node can actually serve the riders routed to it.
Once all four are met, activation is automatic — no discretionary gate, no queue of favors, no one to lobby. The requirement list is the gate, and it's public.
Due process
No suspension without cause, notice, and a window to fix it.
A node isn't cut off on a whim. There's a defined cause, a notification, and a remediation window first — and for the most serious causes, a committee decides, with the networks themselves at the table. The full record is auditable.
- cause
A defined cause
No suspension without a cause defined in the rules in advance. Discretion isn't a cause.
- notice
Notification
The operator is notified — they learn the cause before anything happens to their authorization.
- remedy
A remediation window
A defined window to remedy the cause. The first move is a chance to fix it, not a sanction.
- committee
Serious causes go to committee
Fraud or manipulation is decided by a committee with representation from the networks themselves — and the full record stays auditable.
Build status. The network layer — registry, ledger, roaming and protocol — is on the roadmap and shown here as a target architecture, not a live service. The governance model, validator roles, and the immutable ledger described on this page are part of that network plane. The operation plane — the node, apps, dispatch, payments and tracking — is what ships today.
Networks govern the network
Cities and companies with standing share the decisions.
The operators aren't governed from above — they participate. Those with standing can validate the ledger, vote on major changes, and resolve disputes against an immutable record.
Votes on major changes
Major protocol changes are voted — and paired with long migration windows, so no one is forced to move overnight.
In build · roadmap
Disputes on immutable evidence
A dispute process uses the ledger as immutable evidence — the record is the arbiter, not anyone's say-so.
In build · roadmap
What we guarantee on our side
Governance is bilateral — it binds us too.
The rules don't only constrain the operators. Here is what TechnoRides commits to on its own side of the contract — read against the concerns those commitments answer.
Five commitments we hold
- Availability — the registry stays reachable, treated as critical infrastructure.
- Routing neutrality — we don't tilt the network toward one operator over another.
- Due process — the cause-notice-remediation path applies to every sanction.
- Auditability — every decision is recorded in the ledger and can be checked.
- Continuity — the network endures, even through an operator's exit.
| The concern | What we guarantee |
|---|---|
| Being cut off arbitrarily | Due process — no suspension without a defined cause, notification, and a remediation window. |
| The network favoring a rival | Routing neutrality — the registry doesn't tilt traffic toward any one operator. |
| Trusting a decision after the fact | Auditability — every decision is recorded in the ledger as immutable evidence. |
| The registry going dark | Availability — registry uptime is treated and contracted as critical infrastructure. |
| An operator leaving the network | Continuity — a plan agreed in advance so the network survives the exit. |
Read the governance model
Rules you can read. A record you can audit.
Public rules for who enters, operates, is sanctioned, and exits — enforced through one transparent lever and recorded in the ledger. Governance binds us too. Read the full model, or see how the SLA frames our side of it.