Skip to main content

CLT Economics

CLT (Clutch token) is the native unit on the Clutch blockchain. Ride payments and validator rewards follow the rules below — all enforced in clutch-node.

Overview

Two separate mechanisms:

LayerMechanismDefault
Ride paymentsReferrer fees on each RidePay, driver gets the remainder2% request + 2% offer
NetworkFixed block reward minted to the block author50 CLT per block

Ride fares do not fund validators directly. Validators earn block rewards only.

Ride payment flow

Step 1: RideAcceptance

When a passenger accepts an offer, the full offer fare is debited from the passenger (RideAcceptanceDebit). No funds are credited to the driver yet.

Step 2: RidePay

Each RidePay transaction distributes that payment installment:

  • Request referrerceil(ride_request_referrer_fee_percent × amount / 100) (default 2%)
  • Offer referrerceil(ride_offer_referrer_fee_percent × amount / 100) (default 2%)
  • Driver — installment amount minus total referrer fees

The passenger is not debited again on RidePay; payment comes from the fare already reserved at acceptance.

Referrer fees use ceiling rounding (e.g. 2% of 3 CLT = 1 CLT).

If the same address is referrer on both request and offer, both fees are credited to that address (up to 4% of the installment when defaults apply).

Step 3: RideCancel

If a trip is cancelled before the full fare is paid, the unpaid remainder is refunded to the passenger.

Example

Default config, 10 CLT fare, one full RidePay, both referrers set:

RecipientCLT
Request referrer1
Offer referrer1
Driver8

With no referrers, the driver receives the full installment.

Referrer addresses

Referrer addresses are attached to RideRequest and RideOffer at creation time. The Hub API injects defaults from config when the client does not supply a referrer:

  • default_ride_request_referrer
  • default_ride_offer_referrer

See Hub API configuration.

Validator block reward

Configured per node:

block_reward_amount = 50
  • Minted to the block author on every non-genesis block
  • Independent of ride volume and fare amounts

Configuration keys

SettingDescriptionDefault
ride_request_referrer_fee_percentRequest-side referrer fee on each RidePay2
ride_offer_referrer_fee_percentOffer-side referrer fee on each RidePay2
block_reward_amountCLT minted to block author per block50

Alpha / testnet notes

  • Genesis allocates test supply to the faucet account (u64::MAX CLT) for development
  • There is no on-chain supply cap or emission schedule beyond block_reward_amount
  • CLT has no fixed fiat peg; fares are denominated in CLT