Skip to main content

Clutch Node Overview

Clutch Node is the blockchain core of Clutch Protocol. It runs the consensus layer, stores blocks and state, validates transactions, and exposes WebSocket JSON-RPC and Prometheus metrics endpoints.

Features​

  • Aura consensus — Round-robin block production and finality across configured validators
  • Custom transaction format — Non-EVM, RLP-encoded function calls tailored for ride-sharing
  • Metrics — Prometheus-compatible /metrics on ports 3001–3003
  • Multi-node — Bootstrap and peer discovery via libp2p
  • Decentralized — Eliminates intermediaries, direct user-to-user
  • Secure — Blockchain-verified transactions with on-chain auditability

Components​

ComponentResponsibility
ConsensusAura round-robin scheduling; only addresses in authorities may author blocks
MempoolAccepts and gossips pending transactions; rejects invalid nonces/signatures
StateAccount balances, nonces, and the ride state machine (requests, offers, trips)
Transaction processorApplies function-call tags (Transfer, RideRequest, RidePay, …) to state
Block storeAppend-only block ledger; genesis allocates the testnet faucet supply
RPC serverWebSocket JSON-RPC for apps and the Hub API
P2P layerlibp2p gossip for tx and block propagation, plus bootstrap peer discovery
Metrics exporterExposes node state, block index, and runtime counters to Prometheus

Transaction lifecycle in the node​

Apps do not call the node RPC directly in most cases — they go through the Hub API, which builds unsigned transactions and forwards signed ones.

Ports (per node)​

PortPurpose
8081/8082/8083WebSocket JSON-RPC (node1/node2/node3)
4001/4002/4003libp2p
3001/3002/3003Prometheus metrics

Status and limitations​

  • Alpha testnet only — no mainnet, small validator set on the public testnet
  • Progressive RidePay releases after RideAcceptance; the chain does not attest physical arrival
  • DAO / governance is on the roadmap and not yet implemented

Source​

clutch-node on GitHub.