Skip to main content

Clutch Protocol

Decentralized ride-sharing blockchain

Open-source stack for on-chain ride lifecycle, client-side signing, and instant CLT payouts to drivers.

Get startedOpen the mainnet appTry the testnet

Alpha software. The mainnet is live as a capped pilot, and a public testnet is open.

One ride, four transactions

  1. RideRequest The passenger posts the trip.
  2. RideOffer A driver offers a price.
  3. RideAcceptance The passenger accepts the offer.
  4. RidePay The passenger pays the driver in CLT.
Read the ride lifecycle

What is Clutch?

What it is
Clutch Protocol is an open-source ride-sharing blockchain. Passengers and drivers send ride requests, offers and payments as transactions on its own chain, clutch-node.
How apps use it
clutch-hub has the Hub API, a JavaScript SDK that signs on the user's device, and a reference app for passengers and drivers. clutch-explorer shows the blocks and transactions.
Money and servers
Rides are paid in CLT, a token fully backed by USDT, and clutch-treasury gives CLT for USDT and pays USDT back. clutch-deploy runs the public testnet and the mainnet. The mainnet is live as a capped pilot: top-ups and withdrawals are open.

Explore the stack

Clutch Node

Blockchain core with Aura consensus, custom RLP transactions, non-EVM design.

Hub API

GraphQL bridge between apps and the node, with wallet JWT auth.

JavaScript SDK

Client-side signing, RLP encoding, and live subscriptions over WebSocket.

Block Explorer

Read-only chain indexer, REST API, and web UI for blocks, transactions, and accounts.

Demo App

Reference React app showing the passenger and driver ride flow end to end.

CLT Economics

Fully-reserved CLT, referrer fees on ride payments, and a flat per-transaction fee to the block author.

Clutch Treasury

USDT deposits and redemptions split across three services, so no single one can both decide to mint and move the money behind it.

How it fits together

Demo App / Your dApp + SDK → Clutch Hub API (GraphQL / WS) → Clutch Node (blockchain, WebSocket RPC) → Clutch Explorer (indexer + UI)

  1. Build unsigned tx — the app asks the Hub API for an unsigned transaction payload
  2. Sign client-side — the user signs the hash locally (keys never sent to server)
  3. Submit signed tx — the app sends signed RLP hex to the Hub, which forwards to the node
  4. Validate & mine — the node verifies signature/nonce, applies state, includes in a block

See the full architecture overview and ride lifecycle.