Documentation
Docs24. `ktn_` Methods (18 Methods)

24. ktn_ Methods (18 Methods)

The ktn_ namespace provides 18 dedicated remote procedure calls for querying Kortana-specific protocol features, including dPOH sequence metrics, validator sets, staking economics, slashing evidence, and on-chain governance.

24.1 Node Info

  • ktn_nodeInfo: Returns detailed diagnostic metadata about the running daemon, including the kortanad version string, Git commit hash, C++23 compiler flags, uptime seconds, active execution subsystem configurations, and connected column family metrics.
  • ktn_syncStatus: Returns comprehensive synchronization metrics, including current sync mode (block, snapshot, fast), pivot block height, downloaded state trie node counts, verification bandwidth, and peer connection stages.

24.2 dPOH

  • ktn_getPoHInfo: Returns real-time metrics from the local Delegated Proof of History subsystem, including current slot tick count (0..64), instantaneous SHA-256 hash rate (hashes/sec), cumulative slot hash count, and generator health status.

24.3 Validators

  • ktn_getValidators: Returns the full list of active validators in the current epoch, detailing each validator's 20-byte address, registered BLS12-381 consensus public key, total bonded stake weight, commission percentage, and active status.
  • ktn_getValidatorInfo: Returns in-depth operational performance statistics for a specific validator address, including historical uptime percentage, proposal success rate, missed slots in the current epoch, and accrued reward balances.
  • ktn_validatorSetChange: A WebSocket streaming subscription method that pushes notification payloads whenever the active validator set is modified at an epoch boundary.

24.4 Staking

  • ktn_getStakingInfo: Returns network-wide staking economic metrics, including total bonded DNR across all validators, total DNR in the unbonding queue, circulating stake ratio, current annual staking reward yield (APY), and minimum self-stake thresholds.

24.5 Slashing

  • ktn_getEquivocationEvidence: Retrieves the cryptographic double-sign evidence payload for a specified validator address and consensus view, containing conflicting BLS12-381 vote signatures ready for inclusion in a ReportEquivocation (0x40) transaction.

24.6 Epochs

  • ktn_getEpochInfo: Returns the current epoch index, the slot progress within the epoch (0..2399), the target duration remaining until the next epoch transition, and the deterministic seed for the upcoming leader schedule.
  • ktn_newEpoch: Returns historical epoch boundary records, detailing validator weight snapshots, reward distributions, and matured unbonding stake releases.

24.7 Governance

  • ktn_getGovernanceProposals: Returns the full dictionary of active and historical on-chain governance proposals, including proposal ID, proposer address, target parameter key, proposed value, voting deadlines, and current stake-weighted vote tallies.
  • ktn_getParamStore: Dumps the authoritative key-value dictionary of all active configuration constants stored in the on-chain ParamStore system contract (0x...0102).

24.8 Mempool

  • ktn_getMempoolInfo: Returns real-time telemetry from the transaction mempool, including total pending transaction count, queued transaction count, memory footprint (bytes), and fee distribution histogram.

24.9 Addresses

  • ktn_addressInfo: Translates and resolves both 0x... (secp256k1) and ktn: (Ed25519) address formats, returning account type (EOA, KEVM contract, KVM contract), current nonce, liquid balance, and code hash from the unified world state trie.

24.10 Transactions

  • ktn_sendTransaction: Formats and broadcasts native protocol transactions (such as Stake, Unstake, DelegatePoH, and GovernanceVote), managing payload serialization and signature verification natively.

24.11 Subscriptions

  • ktn_subscribe, ktn_unsubscribe: Manages persistent WebSocket event streams for native protocol events, including epoch boundary transitions, parameter updates, and equivocation alerts.

24.12 Admin

  • ktn_shutdown: Initiates a graceful, deterministic node shutdown procedure: flushes pending RocksDB write batches, checkpoints the state trie, disconnects P2P peers, and terminates background worker threads safely (requires authenticated Bearer token).