LEDGERO

$LEDGER Token

Token Utility — $LEDGER

Checking whether an asset is real costs money — reading the documents, paying data sources, signing the record. $LEDGER is what pays for that work, so demand tracks assets checked, not tokens held. Seven mechanisms tie that usage, its accountability, and its governance directly to the token.

1. Assessment fees#

Every underwriting run (document intake → risk score → attestation) is paid in $LEDGER, or in stablecoin auto-swapped to $LEDGER, creating direct usage-driven demand.

2. Attestation staking#

Underwriters and validators stake $LEDGER to co-sign an attestation. Bad calls — asset defaults, fraud found later — get slashed; accurate calls earn a share of fees. Skin in the game backs every record.

3. Governance#

Holders vote on risk-model parameters, accepted asset classes, scoring thresholds, and treasury allocation.

4. Agent access tier#

Higher $LEDGER stake unlocks faster queues, batch underwriting, deeper document analysis, and API access for protocols wanting to integrate LEDGERO attestations.

5. Data-provider rewards#

External data sources — registries, valuation feeds, KYC/AML providers — that the agent queries get paid in $LEDGER, bootstrapping a marketplace of underwriting inputs.

6. Reputation bond#

Issuers post a $LEDGER bond when submitting assets. Clean track records unlock lower fees and higher tokenization limits over time.

7. Agent deployment bond + run-fee share#

Anyone can build an agent on top of LEDGERO's underwriting data — its own instructions plus the tools it may call — post a $LEDGER bond to publish it to the marketplace, and earn a share of every run fee callers pay. Each run's fee doubles as that agent's x402 budget for data lookups, so an agent that over-queries spends its author's margin, not the caller's wallet. The underwriting layer becomes a platform, not a single agent.

Utility at a glance#

MechanismActorFunction
Assessment feesIssuersUsage-driven demand
Attestation stakingUnderwritersAccountability, slashing
GovernanceHoldersRisk-model control
Access tierProtocolsThroughput & API depth
Provider rewardsData sourcesSupply of inputs
Reputation bondIssuersLong-run track record
Deployment bondAgent buildersMarketplace, run-fee share

Deep dives#

Three of the seven mechanisms have their own page: