Need-to-KnowNeed-to-Know
rewardseconomicscantonomicsfeatured-apps

Rewards Overview: Infrastructure vs App Incentives

5 min read

Canton's economic design explicitly positions application builders as the primary beneficiaries of network rewards. Running a validator is the operational baseline—building a featured app is the growth lever.

The Big Picture

How do Canton rewards work for validators vs app builders? Is running a validator profitable on its own? The short answer: validators earn modest but reliable rewards for infrastructure, while the majority of the rewards pool flows to applications that drive network activity.

Monthly Rewards Pool Split (Jan 2026)
62%
38%
Featured Apps
~516M CC/month
Infrastructure
Validators, SVs
💡 Apps are the bigger lever — building generates more upside than operating alone

From January 2026, Canton's published tokenomics allocates 62% of rewards to featured applications (~516M CC monthly), with the remaining 38% going to infrastructure providers—validators, super validators, and network operations.


The Two Reward Tracks

1. Infrastructure Rewards (Validators)

Validator rewards depend on factors like liveness, uptime, and overall network conditions. The infrastructure pool is shared across the entire validator set.

Key dynamic: As more validators join the network, the same pool is divided across more operators. This tends to reduce per-validator rewards over time, unless total network activity (and thus the total pool) grows proportionally.
FactorImpact on Rewards
Uptime / LivenessHigher uptime = larger share of infra rewards
Validator Set SizeMore validators = smaller per-operator share
Network ActivityMore activity = larger total pool

Canton explicitly positions featured app rewards as the primary long-term economic driver for builders. This is by design: the network wants to incentivize applications that create real utility and drive transaction volume.

Featured app rewards are proportional to the activity your app drives relative to total network activity. A simplified mental model:

Your share ≈ (Your app transactions ÷ Total network transactions) × Monthly featured app pool
"Featured" status matters. Not all apps automatically qualify. Your application generally needs featured status and must emit the correct activity markers to participate in the app rewards mechanics.

Strategy Implications

How should you think about ROI when planning your Canton participation? Here's how the three main strategies compare:

Reward Strategy Comparison
🖥️
Validator Only
✓ Credibility & presence
✓ Reliable baseline rewards
⚠ Modest per-validator share
⚠ Pool dilutes as set grows
📱
Featured App
★ 62% of rewards pool
★ Scales with usage
✓ Highest upside potential
⚠ Requires featured status
🚀
Validator + App
★ Best of both worlds
✓ Infra control & uptime
✓ App-driven growth
✓ Credibility + scale
StrategyUpsideBest For
Validator OnlyModest, reliableInstitutional presence, credibility, ecosystem participation
Featured AppHigh, scales with usageBuilders who can drive sustained transaction volume
Validator + AppCombined + synergiesBest ROI: control your infra while building for scale

Practical Next Steps

1. Treat validator operations as platform capability. Focus on uptime, security, backups, upgrades, and monitoring. This is your operational foundation.

2. Design for featured status. If you're aiming for meaningful rewards, build an application that drives real usage and apply for featured status when production-ready.

3. Track the evolving economics. Tokenomics, splits, and mechanics can evolve. Stay current with official announcements and adjust your strategy.

The bottom line: Running a validator is necessary but not sufficient for maximum rewards. The 62/38 split tells the story—apps are where the real upside lives.