> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/user-guide-canton/validators/balances-and-traffic.md). # Traffic A read-only tab showing the validator's synchronizer traffic counters.
{% hint style="info" %} The Traffic tab is **read-only**. There is no top-up or purchase action in the UI. Traffic purchases and Canton Coin transfers are performed through the Wallet UI or the Canton console. {% endhint %} {% hint style="info" %} **Version note.** 2.0.0 also had a **Balances** tab showing Canton Coin holdings from the network's Scan service. It was removed in 2.0.1, together with the `GET /api/v1/validators/{name}/balances` endpoint. To read a validator's balance, query the Scan API directly. {% endhint %} ## Traffic Synchronizer traffic counters, read from the participant. Canton meters the data a participant sends through the synchronizer. Each participant gets a base allowance that refills over time, and can purchase extra traffic beyond it. This tab shows where the validator stands against both. ### Metric cards All three are byte-formatted (`B`, `KB`, `MB`, `GB`). | Card | Meaning | | ------------------ | --------------------------------- | | **Extra consumed** | Purchased traffic consumed so far | | **Extra limit** | Total purchased traffic allowance | | **Base remaining** | Remaining base allowance | {% hint style="warning" %} When **Base remaining** is near zero and **Extra consumed** is approaching **Extra limit**, the participant is close to being throttled by the synchronizer, and command submission will start failing. Purchase additional traffic through the Wallet UI before that happens. {% endhint %} ### Routing **Domain ID**, **Participant ID**, and **Endpoint**, each with a copy button. Shown when the synchronizer reports them. ### Counters **Last consumed cost**, plus any additional counters the synchronizer returns, with humanised labels. The set of counters depends on the Canton protocol version, so this section is deliberately open-ended. ### States | Situation | What you see | | ------------------ | ----------------------------------------------------------------------- | | Loading | *Loading traffic status…* | | No counters yet | **No traffic data** — *The synchronizer has not reported counters yet.* | | The request failed | **Failed to load traffic**, with the error | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/user-guide-canton/validators/balances-and-traffic.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.