original data source signature
- Sign the specified data directly, and the signature result can be queried through /v1/waas/mpc/web3/sign_result, or distributed via callback from the MPC node.
- Only supports "WaaS" services.
application/json
Request Body
vaultId string required
Vault id
requestId string required
Unique id
User-generated request unique id, used for retry
walletId string required
Wallet id
hdPath string required
The path corresponding to the address
rawData string required
Signature data
algorithmType integer
Signature algorithm, when not provided or with a value of 0 (the current default), the default signature is executed using the algorithm and curve type (ecdsa-secp256k1/eddsa-ed25519) specified when the address was created. When the value is 1 (valid for ecdsa-secp256k1 keys only), execute BIP340-compliant Schnorr signatures (Bitcoin glyph reveal transactions are supported). Perform Taproot signing at a value of 2 (valid only for ecdsa-secp256k1 keys)
tapScriptRoot string
taproot script root, Only taproot-sign can use it.
Responses
- 200
successful operation
application/json
Schema
Example (from schema)
Schema
code integer
msg string
data object
sinoId string
sinohope id
unique id generated by sinohope for each business
success boolean
{
"code": 200,
"msg": "",
"data": {
"sinoId": "12312321"
},
"success": true
}
Loading...