Kaspa payments: speed, fees and payroll limits

What a Kaspa payment actually involves

A direct payment moves KAS from a sender’s wallet to a recipient’s Kaspa address. A merchant processor adds another layer: a checkout, invoice, conversion or payout service. These are different arrangements, so start with what the recipient needs to receive: KAS, another asset or money in a bank account.

Kaspa’s proof-of-work network orders parallel blocks in a blockDAG. The project’s network overview describes the underlying system. It does not tell you whether a particular employer uses KAS, how a merchant handles refunds or when an exchange credits a deposit.

What does 10 blocks per second tell you?

The Crescendo release notes document the transition from 1 to 10 blocks per second. The current project overview reports that 10-block rate on mainnet. Dividing one second by ten gives a mean interval of 0.1 seconds; individual intervals vary.

Block production, transaction confirmation and spendable receipt are different milestones. A receiving service sets its own acceptance policy and may add processing or conversion. Ask when it credits the funds. This article cannot support the old promise of a universally completed payroll payment within ten seconds.

What do Kaspa payments cost?

The Kaspa integration documentation ties network fees to transaction mass, with compute, storage, change outputs and fee priority among the relevant components. A wallet estimate for the actual transaction is more useful than a universal cents-per-payment figure.

For example, NOWPayments’ general pricing page displays a 1% service fee. Its mass-payout page advertises 0% payout service fees while also showing a separate “Starting from: 1%” statement. These labels do not establish a single all-in KAS payroll price. Obtain a quote for the actual funding, conversion and withdrawal path.

A useful comparison records the sender’s total debit, the recipient’s final amount and the units of each. If either side converts KAS, record the quote time too. A small network fee alone does not show whether the complete payment is cheaper.

What is actually established about payroll?

There is a concrete integration lead: NOWPayments’ KAS page lists payment tools and a mass-payout API. Its payout documentation describes funding a custodial balance and submitting recipient details. That establishes an advertised service, not a first-hand test by BitByteDaily.

Our assessment: the sources reviewed here do not establish widespread KAS salary adoption. We found no independently verified employer count or KAS payroll-volume series in them. This is a limit of this review, not evidence that nobody pays in KAS. A stronger adoption claim would need identifiable deployments and evidence of actual use.

The provider’s KAS page still refers to one block per second. We use the newer project and release documentation for the network rate. A provider can be a primary source for its advertised product while carrying outdated technical copy.

Does the KAS rally show payment demand?

A rising KAS price does not establish that more businesses are paying in KAS. Gerhard’s Kaspa Is Back analysis, published on 8 September 2026, examines spot trading, derivatives and possible selling pressure. His 15 September follow-up, Kaspa Is Waking Up, weighs shrinking issuance against demand and development. Those are useful research questions; his trading conclusions are his interpretation.

Source: the price, statistics and performance panels on CoinGecko’s KAS page, read on 18 September. Panels refresh separately; these rounded observations are not a synchronized execution quote. The circulating share is our calculation from the displayed supply figures.

Gerhard also compares KAS with Bitcoin. A dollar gain can still underperform BTC over the same dates. For someone choosing between assets, that measures opportunity cost; for a business paying a dollar invoice, the relevant exposure is the exchange-rate change between funding and conversion. Neither comparison measures payroll adoption.

What does declining issuance change?

Kaspa’s subsidy implementation uses declining monthly rewards and adjusts them for the block rate. The monthly multiplier is approximately 2^−1/12: a reduction of about 5.61% per emission month, halving the rate over twelve such periods. These periods are 30.4375 days in the implementation, not calendar months. Increasing blocks per second does not multiply coin issuance by the same factor.

This distinction changes an inflation calculation. With twelve full periods and that multiplier, projected issuance is about 74.2% of twelve times the starting monthly issuance. An exact forecast from today must include the remaining part of the current period. Gerhard revisits this annualization issue in his follow-up; we do not treat its historical estimate as a fresh network measurement.

Less new supply can reduce one source of dilution. It does not establish demand or remove coins already available for sale. Comparing a year of issuance, valued at one assumed price, with one day’s trading turnover also cannot prove that buyers would absorb it without moving the price.

There is a security-budget question too. If subsidy income alone falls by 5.61%, the KAS price would need to rise by about 5.95% to preserve its dollar value, all else equal. That is an illustrative calculation, not a required price path: fees, network hashrate, miner share, equipment and electricity costs also matter.

What do Kasplex and Igra tell us about usage?

Application activity adds evidence beyond exchange trading. On 18 September, DefiLlama’s live pages showed approximately $351,000 of Kasplex TVL and $1.20 million of Igra TVL. Their displayed 24-hour chain fees were about $14 and $237 respectively. These are separate, changing observations of the tracked application ecosystems.

TVL means value locked in tracked DeFi applications; it is not sales, salaries or total value transferred. Rising dollar TVL can partly reflect rising asset prices. These figures do not measure all native Kaspa use, and the application-layer fees are not a measurement of base-layer miner revenue. A small DeFi footprint neither disproves the payment technology nor substantiates widespread payroll use.

Our assessment is that a payment-adoption claim needs its own evidence: identifiable integrations in use, repeat payments and disclosed payment volumes. Traders, application users and employers can generate very different kinds of demand.

Which improvements are live, and which are still ahead?

The project’s current technical overview reports that Toccata activated on mainnet on 30 June 2026. The v2.0.0 release introduced native covenant programming and infrastructure for based zero-knowledge applications. Covenants place conditions on how outputs can be spent; that creates building blocks for applications, not a ready-made payroll service.

As reviewed on 18 September, the latest tagged v2.0.1 release was dated 15 June. However, the repository’s pull-request list showed DAGKnight-related proposals opened on 14 September. A release gap therefore does not establish that development has stopped. Open proposals also do not establish shipped, audited functionality.

The overview places DAGKnight after Toccata and describes 100 blocks per second as a 2027 target. Treat those as future milestones. The payment assumptions above use the reported live rate of 10 blocks per second.

What would strengthen the case? Compare sustained spot activity and KAS/BTC performance over matching periods; track application usage and fees alongside TVL; and verify announced upgrades against releases and mainnet activation. For the payroll claim specifically, seek documented recurring salary payments. Until that evidence appears, the supply case and the adoption case remain separate.

What should a business check first?

Define the amount owed and its denomination, who can approve a payment, who controls the wallet and how the recipient will use the funds. Request the receiving service’s minimum amount and confirmation policy. Plan how to investigate an incorrect address, a delayed credit or a failed conversion before depending on the workflow.

Payroll also needs records beyond a transaction ID. As a US-specific example, the IRS digital-assets guidance calls for records of transactions and the US-dollar fair market value of assets received as income or business payments. That tax example does not resolve local wage-payment rules; those need a jurisdiction-specific check.

If a payment obligation is denominated in dollars while the recipient receives KAS, the conversion quote determines how many coins discharge that amount. Agree on that conversion point and who bears subsequent exchange-rate changes. Fast block production does not answer this commercial question.

For background reading, the BitByteDaily archive retains older coverage. Our guide to this edition explains how to distinguish those historical articles from a dated source review.