trio/com.silencelaboratories.silentshard.trio/SilentShard/Taproot

Taproot

Three-party Taproot — BIP-340 Schnorr over secp256k1, the scheme behind Bitcoin Taproot (P2TR) key-path spends.

Construct a session with trioInitiator and drive it through TrioSession, which adds keyshare recovery on top of the shared operations (pre-signatures and hardened derivation are ECDSA-only). The stateless helpers inherited from SilentShard operate on secp256k1 keyshares; deriveChildPublicKey is address-side only, since a Taproot signing run takes no chain path.

Types

TestMessageSigner

object TestMessageSigner : MessageSigner

Internal test key provider for testing purposes ONLY. Never use in production. See MessageSigner for secure implementations.

Properties

tss

open override val tss: Taproot

The process-shared TSS instance backing the stateless helpers (getKeyshareKeyId, getKeysharePublicKey, deriveChildPublicKey, generateEncryptionDecryptionKeyPair). Sessions get their own instance via newSessionTss.

Functions

deriveChildPublicKey

open suspend fun deriveChildPublicKey(keyshare: ByteArray, derivationPath: String): Result<ByteArray>

Derives a child public key via BIP32 hierarchical-deterministic derivation, producing many addresses from one keyshare. Runs locally.

generateEncryptionDecryptionKeyPair

open suspend fun generateEncryptionDecryptionKeyPair(): Pair<ByteArray, ByteArray>

Generates a keypair used to encrypt keyshare-backup material.

getKeyshareKeyId

open suspend fun getKeyshareKeyId(keyshare: ByteArray): Result<ByteArray>

Computes the keyId of a keyshare — a deterministic identifier derived from its public key. This is the same value TrioSession.keygen and TrioSession.import return. Runs locally.

getKeysharePublicKey

open suspend fun getKeysharePublicKey(keyshare: ByteArray): Result<ByteArray>

Extracts the public key from a keyshare, for deriving addresses or verifying signatures. Runs locally.

newSessionTss

open override fun newSessionTss(): TSS

Construct a fresh per-session TSS instance — used by the trioInitiator(...) factories so each session owns its own native-handle tracking list. The process-singleton tss is kept for stateless utilities (getKeyshareKeyId etc.); sharing it for sessions would mean the library's allocation list grows monotonically and concurrent sessions race on it.

trioInitiator

open fun trioInitiator(messageSigner: MessageSigner, cloudVerifyingKey: String, networkClient: SilentShardWebsocketClient<TrioNetworkAction>, storageClient: StorageClient): TrioSession

Creates an initiating TrioSession over the default WebSocket transport, reusing a SilentShardWebsocketClient you construct and own — for example to share one client across sessions and com.silencelaboratories.silentshard.network.NetworkClient.close it yourself.

open fun trioInitiator(messageSigner: MessageSigner, cloudVerifyingKey: String, websocketConfig: WebsocketConfig, storageClient: StorageClient): TrioSession

Creates a TrioSession as the initiating party, over the default WebSocket transport. The recommended entry point for most integrations.

open fun trioInitiator(messageSigner: MessageSigner, cloudVerifyingKey: String, storageClient: StorageClient, networkClient: NetworkClient, actionProvider: TrioNetworkActionProvider): TrioSession

Creates an initiating TrioSession over a custom transport.