Solana’s September payments roundup, published on October 9, 2026, brings together several different measurements. A channel benchmark is not live base-layer transaction throughput, active addresses are not automatically identified people, and token supply is not monthly payment volume. One displayed growth claim also needs clarification: the stated address counts do not reproduce its stated percentage under the usual growth calculation.
First identify what was counted
The October 9 roundup summarizes payment-channel testing, stablecoin activity and other September developments. Those items can be useful evidence about different parts of an ecosystem. They cannot be added together or ranked as if they all measured completed consumer transfers. Before repeating a number, retain its unit and observation period.
| Metric in a payments story | Question that defines it | What cannot be inferred directly |
|---|---|---|
| Payments per second in a channel benchmark | What ran in the test, and where was settlement recorded? | The same number of separate mainnet transactions |
| Stablecoin transfer count | What is a transfer and which assets and period are included? | A count of unique people paying for goods |
| Active address count | Sending, receiving or both, over which window? | A verified customer count |
| Stablecoin supply | What stock of tokens existed at the observation time? | How much value was paid during a month |
| Percentage growth | What are the baseline, endpoint and exact formula? | A result derived from unrelated or inconsistent denominators |
A million channel payments is a scoped benchmark
The underlying payment-channel announcement describes testing a proxy with 100,000 wallets and more than a million payments per second. It also explains that usage is metered off-chain and the consumed amount is settled later on-chain. That distinction is central to what the benchmark means.
Do not relabel this as a live measurement of a million independent mainnet settlement transactions every second. Nor does a tested capacity establish that every request was generated by an independent human customer. This report did not reproduce the load test, measure current network throughput or verify the availability of every service named in the roundup.
Check a growth sentence with its own displayed numbers
The roundup presents 888,000 daily active addresses and a comparison with 333,000 a year earlier, alongside a stated 269% increase. If those two displayed figures are the inputs to ordinary percentage growth, the calculation is (888,000 / 333,000 − 1) × 100, or approximately 166.7%. The displayed pair therefore does not itself produce the stated increase.
This arithmetic check does not independently establish Solana’s true year-on-year growth. That would require checking the underlying series, matching the observation windows and resolving what the percentage was intended to describe. Until that is resolved, retain the discrepancy instead of copying the growth claim or silently substituting a newly calculated figure as verified network data.
The same discipline helps with rounded statistics. A percentage calculated from precise source observations need not equal a calculation from rounded display values. Here the reader’s job is to preserve which values and formula were checked, and identify what remains unverified. A plausible story about adoption is not a replacement for that evidence.
Keep stock, flow and identity separate
A simple fictional example shows why these boundaries matter: one customer can use several addresses, while a shared custody address can represent more than one customer. An address count alone does not resolve either case. Likewise, the same units can move repeatedly during a period, so transfer volume need not equal the supply outstanding at its end.
These are limits of the measurements, not an assertion that every transfer is artificial or that a particular project fabricated activity. A useful comparison discloses whether it uses gross transfers, filtered economic activity or a specifically identified payment category. Without that definition, comparing a blockchain chart with a card network’s transaction total can mix different things.
- Write down the unit, included assets, measurement window and source for each number.
- Separate benchmark capacity from observed production activity and individual settlement.
- Recalculate displayed growth only when baseline and endpoint describe the same measurement.
- Keep unresolved discrepancies visible rather than converting them into verified adoption claims.
- For an actual payment decision, check the relevant asset, route and recipient instead of relying on aggregate popularity.
What the report means for a transfer you make
The roundup identifies developments worth investigating; it does not set a personal transfer deadline or guarantee a receiving platform’s credit. Check the supported networks and assets before choosing a swap, and follow the actual exchange procedure. No ecosystem total establishes a KOT.CASH fee, delivery time or provider relationship. Those details must come from the relevant service and order.
FAQ
Does a Solana TPS record from a payment-channel test measure live mainnet TPS?
Identify what the benchmark counts and where settlement happens. The described channel meters usage off-chain before settling the consumed amount on-chain.
Can a Solana TPS chart tell me how many unique customers paid?
A transaction or address metric does not independently identify people. Check the dataset’s definitions instead of substituting a customer count.
Does Solana TPS speed establish my deposit’s delivery time?
An aggregate throughput measure is not an individual service’s delivery commitment. Inspect the actual route and the receiving service’s record.