BIP340 - Sign multiple messages using key shares
POST/bip340/batch-sign
Perform a batch of sign operations at once. This is useful for batching multiple sign operations into a single request. every sign request in the batch is the exact same as the normal sign request
Request
Header Parameters
The AUTHORIZATION
header must be set to the API Key of the user. The API Key is returned when a new user is created using the /admin/create-user
endpoint.
- application/json
Body
required
Array [
]
sign_requests
object[]
required
Hex encoded extra data to be passed to the Rule Server. This data should be used to pass any additional information / external state to the Rule Server that is required to properly validate the signing request.
The message to be signed. Has to be hex encoded.
Responses
- 200
- 400
- 401
- 404
- 500
- application/json
- Schema
- Example (from schema)
Schema
Array [
- MOD1
- MOD2
]
oneOf
Signature
object
required
Error
object
required
[
{},
{}
]
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [already_performed_keygen
, bad_n_and_t_params
, bad_request_params
, batch_too_large
, executor_result
, key_id_not_exists
, key_operation_before_keygen
, policy_in_use_by_keys
, policy_in_use_by_users
, policy_not_found
, policy_validation_failed
, room_creation_problem
, rule_in_use
, rule_not_found
, rule_not_in_policy
, user_id_not_exists
, you_have_to_be_admin
]
{
"err_msg": "string",
"err_type": "already_performed_keygen"
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [access_denied
]
{
"err_msg": "string",
"err_type": "access_denied"
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [not_found
]
{
"err_msg": "string",
"err_type": "not_found"
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [internal_problem
]
{
"err_msg": "string",
"err_type": "internal_problem"
}