Skip to main content

PSKT (Portable Signing Sessions)

Welcome to the HardKAS PSKT documentation.

Unavailable in this build

No PSKT adapter implements an operation in this build: hardkas pskt export, import, sign, merge, finalize and extract refuse with a typed error, and hardkas pskt capabilities reports every operation as unavailable. hardkas pskt inspect shows a session file's metadata only: it does not decode the payload, so it shows no inputs, outputs, amounts or recipients and is no pre-signing check. These pages describe the upstream protocol, not something this build runs.

PSKT (Partially Signed Kaspa Transactions) is the upstream Kaspa protocol for coordinating distributed cryptographic authority.

  • What is PSKT?: Understand the difference between PSKT (a transport container) and Multisig (a spending condition).
  • The Lifecycle: Map the exact boundaries between Partial Signatures, Combination, Finalization, and Extraction.
  • Security & Privacy: Learn why PSKTs are not perfectly secret and why signers must trust their inspection tools.

Upstream vs HardKAS Evidence​

HardKAS would wrap the upstream implementation through an adapter; this build has none that works.

CapabilityUpstream Kaspa PrimitiveHardKAS CommandStatus in this build
InspectpsktInspecthardkas pskt inspectsession metadata only (the payload is not decoded)
SignpsktSignhardkas pskt signUNAVAILABLE (refuses)
CombinepsktCombinehardkas pskt mergeUNAVAILABLE (refuses)
FinalizepsktFinalizehardkas pskt finalizeUNAVAILABLE (refuses)
ExtractpsktExtracthardkas pskt extractUNAVAILABLE (refuses)

PSKT vs Normal Signing​

ConceptNormal Local SigningPSKT
AuthorityAvailable locally and synchronously.Deferred, offline, or distributed.
NetworkHardKAS requires node RPC to plan & submit.Signer requires zero network access.
OutputRaw SignedTxArtifact ready for broadcast.Intermediate binary envelope requiring extraction.

To see the workflows in action, review the Create & Inspect and Offline Signing guides.