Hi all,
Local Traffic Management is now available to validator operators and wallet providers. It lets validators track synchronizer traffic spend per party and optionally enforce a traffic balance on submissions.
What this means if you’re a wallet provider: every submission your users make costs synchronizer traffic, and until now that cost was only visible at the node level, not per user. With this feature, your validator can attribute traffic spend to the individual party (i.e. your end user) that submitted the transaction. That gives you two things, independently:
- Accounting: see exactly how much traffic each of your users’ accounts is spending, via a TrafficService exposed on the Ledger API (gRPC and JSON API).
- Enforcement (optional): reject a user’s submission if their account balance doesn’t cover the cost, so spend stays capped per account instead of draining a shared node balance.
Full config, API reference, and a rollout runbook here: Local Traffic Management
Happy to answer questions here.