Sign in
latestOpenAPI 3.0.32026-08-224982,0272.8 MB

e445c15e5bee

Transaction request

Create a signature share for a transaction on a transaction request

Allows users to supply their signature share for signing.

This route is only valid for transaction request full. Use only with MPC wallets.

post/api/v2/wallet/{walletId}/txrequests/{id}/transactions/{transactionIdx}/signatureshares

Path parameters

walletIdstring required
Example:59cd72485007a239fb00282ed480da1f

The wallet ID.

idstring required
Example:59cd72485007a239fb00282ed480da1f
transactionIdxstring required

Request body

signerSharestring

An openPGP ascii armored message (encrypted to the known HSM public key) containing the previous signer’s offset secret share as a 128 character hex string (64 bytes) consisting of the new offset “u” private component from the user [or backup] new offset Y-share as a 64 character hex string (32 bytes) concatenated with the new offset “chaincode” component of the new offset Y-share as a 64 character hex string (32 bytes). Must be provided when uploading an R share.

userPublicGpgKeystring

User’s public key of the gpg key.

Example request

{
  "signatureShare": {
    "from": "user",
    "to": "user"
  },
  "signatureShares": [
    {
      "from": "user",
      "to": "user"
    }
  ]
}

Response

Created

from'user' | 'backup' | 'bitgo' required
to'user' | 'backup' | 'bitgo' required
sharestring required

The signature share.

Example response

{
  "from": "user",
  "to": "user"
}