Skip to main content

Documentation Index

Fetch the complete documentation index at: https://cantonfoundation-api-reference-details-history.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Back to Signing API

Details and history

Signing API details and history

Generated-source metadata, version coverage, method inventory, and per-version changes for this source stream.

JSON-RPC0.25.0Since 0.24.0

Generated from

Generated reference pages

Operation pages are generated from the publish-version OpenRPC document, with history calculated across selected snapshots.

Version summary

Active since / addedChangedRemovedDeprecated
VERSIONSTATUSSUMMARY
0.24.0
0 surface changes
No surface changes detected in the selected inputs.
0.25.0
0 surface changes
No surface changes detected in the selected inputs.

Current reference inventory

Published methods

These methods are present in the publish version and link to the generated operation pages.
TYPESTATUSSUMMARY
createKey
Since 0.24.0
Create a new key at the Wallet Provider.
getConfiguration
Since 0.24.0
-
getKeys
Since 0.24.0
Get a list of public keys availabile for signing.
getTransaction
Since 0.24.0
Get the status of a single transaction by its ID.
getTransactions
Since 0.24.0
Get the status of multiple transactions, filtering by txIds or publicKeys. Either publicKeys or txIds must be provided.
setConfiguration
Since 0.24.0
Set configuration parameters for the Wallet Provider. The paramaters will change depending on the Wallet Provider implementation
signTransaction
Since 0.24.0
Uses the Wallet Provider to sign a transaction. This will likely be an asynchronous operation.
subscribeTransactions
Since 0.24.0
Subscribe to updates for specific transactions. The server will emit updates when the status of the specified transactions have changed. On initial…

Change details

0.24.0Initial selected snapshot 8 methods were present when this source stream first appears in the selected inputs.

Known limits

  • Change detection is structural and compares selected generated inputs; it does not infer behavioral compatibility.
  • Method-level additions, removals, and changed request or result shapes are tracked when they are present in the selected snapshots.
  • Lifecycle labels and replacement links are included only when the source document carries that metadata.