Checking Pending Transactions

KMS in Daemon Mode

When running in Daemon mode, KMS periodically checks for transactions to sign.
By default, this check occurs every 5 seconds, which consumes credits from your monthly allowance.

Baseline consumption: ~4 credits per minute per chain
Signature attempts: 1 credit is charged for every 500 transaction signature IDs processed.

Adjusting the Frequency

You can reduce baseline credit usage by changing the frequency of pending transaction checks. Use the --period option to set the interval (in seconds).

Request command:

tatum-kms daemon --period=15

This increases the check interval to 15 seconds, lowering the daily credit cost per chain.

Credit Consumption Estimate by Interval (Per Chain)

Interval (`--period`)	Checks per Minute	Credits per Day (Per Chain)
5 seconds (default)	12	5.760
15 seconds	4	1.920
30 seconds	2	960
60 seconds	1	480

Multiple Chains Example

If you run KMS against 3 blockchains at the default 5-second interval:

~5,760 credits × 3 chains = ~17,280 credits/day

Important Information

Credit usage scales linearly with the number of chains being monitored.
There is currently no upper limit on the --period value. However, some blockchains, such as Tron, may have a transaction expiration limit.
Checking for pending transactions consumes credits for every API call
Full reference: Run KMS in Daemon Mode and Change the Frequency.