joshua/dips
1
0
Fork 0
mirror of https://github.com/seigler/dips synced 2025-07-26 17:26:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update DIPs regarding use of BLS12-381-reversed (#25)

Browse source 
* Update bls_signature_scheme.md with BLS12-381-reversed

* Update DIP3/DIP4 to use BLS operator keys

* Update DIP5 to use BLS keys for user keys

Also add the "Size" column to all serialization specs to align with other DIPs.

* Update BLS primitives serialization size in DIP6/7

* DIP3 - Correct PubKeyOperator type

* DIP4 - Correct PubKeyOperator type

* Remove trailing e from integere
This commit is contained in:
Alexander Block 2018-11-09 18:42:42 +01:00 • committed by thephez
parent b1b56aaefd
commit 52aee60048
6 changed files with 60 additions and 63 deletions
Download patch file Download diff file Expand all files Collapse all files

19
dip-0003.md
View file

@ -69,10 +69,11 @@ Only the valid subset is used in calculations to determine the recipient of the
To join the masternode list, masternode owners must submit a special transaction (DIP2) to the network. This transaction is called a Provider Registration Transaction and is abbreviated to ProRegTx. The ProRegTx must include an output with the 1000 DASH or refer to an already existing unspent output which holds 1000 DASH. To join the masternode list, masternode owners must submit a special transaction (DIP2) to the network. This transaction is called a Provider Registration Transaction and is abbreviated to ProRegTx. The ProRegTx must include an output with the 1000 DASH or refer to an already existing unspent output which holds 1000 DASH.
The ProRegTx contains 3 public key IDs, which represent 3 different roles in the masternode and define update and voting rights. A "public key ID" refers to the hash160 of an ECDSA public key. These are: The ProRegTx contains 2 public key IDs and one BLS public key, which represent 3 different roles in the masternode and define update and voting rights.
A "public key ID" refers to the hash160 of an ECDSA public key. The keys are:
1. KeyIdOwner: This is the public key ID of the masternode or collateral owner. It is different than the key used in the collateral output. Only the owner is allowed to issue ProUpRegTx transactions. 1. KeyIdOwner: This is the public key ID of the masternode or collateral owner. It is different than the key used in the collateral output. Only the owner is allowed to issue ProUpRegTx transactions.
2. KeyIdOperator: This is the public key ID of the masternode operator. Only the operator is allowed to issue ProUpServTx transactions. The operator key is also used while operating the masternode to sign masternode related P2P messages, quorum related messages and governance trigger votes. Messages signed with this key are only valid while the masternode is in the valid set. 2. PubKeyOperator: This is the BLS public key of the masternode operator. Only the operator is allowed to issue ProUpServTx transactions. The operator key is also used while operating the masternode to sign masternode related P2P messages, quorum related messages and governance trigger votes. Messages signed with this key are only valid while the masternode is in the valid set.
3. KeyIdVoting: This is the public key ID used for proposal voting. Votes signed with this key are valid while the masternode is in the registered set. 3. KeyIdVoting: This is the public key ID used for proposal voting. Votes signed with this key are valid while the masternode is in the registered set.
A single key can be used for multiple roles so the owner can also operate the masternode and/or issue proposal votes. Alternately, different keys can be used to delegate duties to other people. For example, owners might decide to use a masternode hosting service instead of self-hosting the masternode. To do so, they would use the operator key provided by the hosting service. The same applies to the voting key, which allows them to assign voting rights to someone else. A single key can be used for multiple roles so the owner can also operate the masternode and/or issue proposal votes. Alternately, different keys can be used to delegate duties to other people. For example, owners might decide to use a masternode hosting service instead of self-hosting the masternode. To do so, they would use the operator key provided by the hosting service. The same applies to the voting key, which allows them to assign voting rights to someone else.
@ -98,7 +99,7 @@ The transaction consists of the following data in the payload area:
| ipAddress | byte[] | 16 | IPv6 address in network byte order. Only IPv4 mapped addresses are allowed (to be extended in the future) | | ipAddress | byte[] | 16 | IPv6 address in network byte order. Only IPv4 mapped addresses are allowed (to be extended in the future) |
| port | uint_16 | 2 | Port (network byte order) | | port | uint_16 | 2 | Port (network byte order) |
| KeyIdOwner | CKeyID | 20 | The public key hash used for owner related signing (ProTx updates, governance voting) | | KeyIdOwner | CKeyID | 20 | The public key hash used for owner related signing (ProTx updates, governance voting) |
| KeyIdOperator | CKeyID | 20 | The public key hash used for operational related signing (network messages, ProTx updates) | | PubKeyOperator | BLSPubKey | 48 | The public key used for operational related signing (network messages, ProTx updates) |
| KeyIdVoting | CKeyID | 20 | The public key hash used for voting. | | KeyIdVoting | CKeyID | 20 | The public key hash used for voting. |
| operatorReward | uint_16 | 2 | A value from 0 to 10000. | | operatorReward | uint_16 | 2 | A value from 0 to 10000. |
| scriptPayoutSize | compactSize uint | 1-9 | Size of the Payee Script. | | scriptPayoutSize | compactSize uint | 1-9 | Size of the Payee Script. |
@ -138,8 +139,7 @@ The transaction consists of the following data in the payload area:
| scriptOperatorPayoutSize | compactSize uint | 1-9 | Size of the Payee Script. | | scriptOperatorPayoutSize | compactSize uint | 1-9 | Size of the Payee Script. |
| scriptOperatorPayout | Script | Variable | Payee script (p2pkh/p2sh) | | scriptOperatorPayout | Script | Variable | Payee script (p2pkh/p2sh) |
| inputsHash | uint256 | 32 | Hash of all the outpoints of the transaction inputs | | inputsHash | uint256 | 32 | Hash of all the outpoints of the transaction inputs |
| payloadSigSize | compactSize uint | 1-9 | Size of the Signature | | payloadSig | BLSSig | 96 | Signature of the hash of the ProUpServTx fields. Signed by the Operator. |
| payloadSig | vector<unsigned char> | Variable | Signature of the hash of the ProUpServTx fields. Signed by the Operator. |
### Updating Registrar of Masternode (ProUpRegTx) ### Updating Registrar of Masternode (ProUpRegTx)
@ -156,7 +156,7 @@ The transaction consists of the following data in the payload area:
| version | uint_16 | 2 | Upgrade Provider Transaction version number. Currently set to 1. | | version | uint_16 | 2 | Upgrade Provider Transaction version number. Currently set to 1. |
| proTXHash | uint256 | 32 | The hash of the provider transaction | | proTXHash | uint256 | 32 | The hash of the provider transaction |
| mode | uint_16 | 2 | Masternode mode | | mode | uint_16 | 2 | Masternode mode |
| KeyIdOperator | CKeyID | 20 | The public key hash used for operational related signing (network messages, ProTx updates) | | PubKeyOperator | BLSPubKey | 48 | The public key used for operational related signing (network messages, ProTx updates) |
| KeyIdVoting | CKeyID | 20 | The public key hash used for voting. | | KeyIdVoting | CKeyID | 20 | The public key hash used for voting. |
| scriptPayoutSize | compactSize uint | 1-9 | Size of the Payee Script. | | scriptPayoutSize | compactSize uint | 1-9 | Size of the Payee Script. |
| scriptPayout | Script | Variable | Payee script (p2pkh/p2sh) | | scriptPayout | Script | Variable | Payee script (p2pkh/p2sh) |
@ -182,8 +182,7 @@ The transaction consists of the following data in the payload area:
| proTXHash | uint256 | 32 | The hash of the provider transaction | | proTXHash | uint256 | 32 | The hash of the provider transaction |
| reason | uint_16 | 2 | The reason for revoking the key. | | reason | uint_16 | 2 | The reason for revoking the key. |
| inputsHash | uint256 | 32 | Hash of all the outpoints of the transaction inputs | | inputsHash | uint256 | 32 | Hash of all the outpoints of the transaction inputs |
| payloadSigSize | compactSize uint | 1-9 | Size of the Signature | | payloadSig | BLSSig | 96 | Signature of the hash of the ProTx fields. Signed by the Operator. |
| payloadSig | vector<unsigned char> | Variable | Signature of the hash of the ProTx fields. Signed by the Operator. |
## Rules for Updating the Masternode List ## Rules for Updating the Masternode List
@ -215,9 +214,9 @@ A ProRegTx is invalid if any of these conditions are true:
1. collateralOutpoint `hash` is null but an output with 1000 DASH is not present at position `n` of the ProRegTx outputs 1. collateralOutpoint `hash` is null but an output with 1000 DASH is not present at position `n` of the ProRegTx outputs
2. collateralOutpoint `hash` is not null but an output with 1000 DASH can't be found in the UTXO specified by the `hash` and `n` 2. collateralOutpoint `hash` is not null but an output with 1000 DASH can't be found in the UTXO specified by the `hash` and `n`
3. Any KeyId* field is null (KeyIdOwner, KeyIdOperator or KeyIdVoting) 3. Any KeyId* field is null (KeyIdOwner, KeyIdOperator or KeyIdVoting)
4. KeyIdOwner or KeyIdOperator was already used by any entry in the registered masternodes set 4. KeyIdOwner or PubKeyOperator was already used by any entry in the registered masternodes set
5. scriptPayout is not a P2PKH or P2SH script 5. scriptPayout is not a P2PKH or P2SH script
6. When scriptPayout is P2PKH script and the public key hash equals any of KeyIdOwner, KeyIdOperator or KeyIdVoting 6. When scriptPayout is P2PKH script and the public key hash equals any of KeyIdOwner or KeyIdVoting
7. ipAddress is set and port is not set to the default mainnet port 7. ipAddress is set and port is not set to the default mainnet port
8. ipAddress is set and not routable or not an IPv4 mapped address 8. ipAddress is set and not routable or not an IPv4 mapped address
9. ipAddress is set and already used in the registered masternodes set 9. ipAddress is set and already used in the registered masternodes set

2
dip-0004.md
View file

@ -83,7 +83,7 @@ A SML entry consists of the following fields:
| proRegTxHash | uint256 | 32 | The hash of the ProRegTx that identifies the masternode | | proRegTxHash | uint256 | 32 | The hash of the ProRegTx that identifies the masternode |
| ipAddress | byte[] | 16 | IPv6 address in network byte order. Only IPv4 mapped addresses are allowed (to be extended in the future) | | ipAddress | byte[] | 16 | IPv6 address in network byte order. Only IPv4 mapped addresses are allowed (to be extended in the future) |
| port | uint_16 | 2 | Port (network byte order) | | port | uint_16 | 2 | Port (network byte order) |
| keyIDOperator | CKeyID | 20 | The operators public key hash | | pubKeyOperator | BLSPubKey | 48 | The operators public key |
| keyIDVoting | CKeyID | 20 | The public key hash used for voting. | | keyIDVoting | CKeyID | 20 | The public key hash used for voting. |
| isValid | bool | 1 | True if a masternode is not PoSe-banned | | isValid | bool | 1 | True if a masternode is not PoSe-banned |

55
dip-0005.md
View file

@ -68,15 +68,13 @@ The special transaction type used for Register Subscription Transactions is 8.
The transaction consists of the following data in the payload area: The transaction consists of the following data in the payload area:
| Name | Data Type | Description | | Name | Type | Size | Description |
| - | - | - | | - | - | - | - |
| version | uint16_t | Register transaction version number | | version | uint16_t | 2 | Register transaction version number |
| userNameSize | compactSize uint | Length of the username | | userNameSize | compactSize uint | 1-9 | Length of the username |
| userName | string | Username for the account<br> * Cannot be changed by subsequent SubTxs | | userName | string | Variable | Username for the account<br> * Cannot be changed by subsequent SubTxs |
| pubkeySize | compactSize uint | Length of the public key | | pubKey | BLSPubKey | 48 | Owner’s public key for the account<br> * For authentication only - should not be used to hold funds |
| pubkey | byte[] | Owner’s public key for the account<br> * For authentication only - should not be used to hold funds | | payloadSig | BLSSig | 96 | Signature of the hash of the preceding fields signed by the blockchain user with the private key for the specified PubKey |
| payloadSigSize| compactSize uint | Length of the signature |
| payloadSig | byte[] | Signature of the hash of the preceding fields signed by the blockchain user with the private key for the specified PubKey (65 bytes) |
### Topup Blockchain User Credit (SubTxTopup) ### Topup Blockchain User Credit (SubTxTopup)
@ -88,10 +86,10 @@ The special transaction type used for Topup Subscription Transactions is 9.
The transaction consists of the following data in the payload area: The transaction consists of the following data in the payload area:
| Name | Data Type | Description | | Name | Type | Size | Description |
| - | - | - | | - | - | - | - |
| version | uint16_t | Topup transaction version number | | version | uint16_t | 2 | Topup transaction version number |
| regTxHash | uint256 | Registration Transaction-ID of the first Register Subscription Transaction | | regTxHash | uint256 | 32 | Registration Transaction-ID of the first Register Subscription Transaction |
### Reset Blockchain User Key (SubTxResetKey) ### Reset Blockchain User Key (SubTxResetKey)
@ -107,16 +105,14 @@ The special transaction type used for ResetKey Subscription Transactions is 10.
The transaction consists of the following data in the payload area: The transaction consists of the following data in the payload area:
| Name | Data Type | Description | | Name | Type | Size | Description |
| - | - | - | | - | - | - | - |
| version | uint16_t | Reset key transaction version number | | version | uint16_t | 2 | Reset key transaction version number |
| regTxHash | uint256 | Registration Transaction-ID of the first Register Subscription Transaction | | regTxHash | uint256 | 32 | Registration Transaction-ID of the first Register Subscription Transaction |
| hashPrevSubTx | uint256 | Hash of the user’s previous subscription transaction | | hashPrevSubTx | uint256 | 32 | Hash of the user’s previous subscription transaction |
| creditFee | int64_t | Fee (denominated in duffs) to pay for transaction | | creditFee | int64_t | 8 | Fee (denominated in duffs) to pay for transaction |
| newPubKeySize | compactSize uint | Length of the new public key | | newPubKey | BLSPubKey | 48 | New public key for a change/reset action |
| newPubKey | byte[] | New public key for a change/reset action | | payloadSig | BLSSig | 96 | Signature of most recent pubkey prior to this transaction, signing a change/reset action |
| payloadSigSize| compactSize uint | Length of the signature |
| payloadSig | byte[] | Signature of most recent pubkey prior to this transaction, signing a change/reset action |
### Close Blockchain User Account (SubTxCloseAccount) ### Close Blockchain User Account (SubTxCloseAccount)
@ -126,14 +122,13 @@ The special transaction type used for CloseAccount Subscription Transactions is
The transaction consists of the following data in the payload area: The transaction consists of the following data in the payload area:
| Name | Data Type | Description | | Name | Type | Size | Description |
| - | - | - | | - | - | - |
| version | uint16_t | Close account transaction version number | | version | uint16_t | 2 | Close account transaction version number |
| regTxHash | uint256 | Registration Transaction-ID of the first Register Subscription Transaction | | regTxHash | uint256 | 32 | Registration Transaction-ID of the first Register Subscription Transaction |
| hashPrevSubTx | uint256 | Hash of the user’s previous subscription transaction. This is necessary to ensure proper order of operations is followed (e.g. make sure the proper key has signed the Close message if a ResetKey message is also present) | | hashPrevSubTx | uint256 | 32 | Hash of the user’s previous subscription transaction. This is necessary to ensure proper order of operations is followed (e.g. make sure the proper key has signed the Close message if a ResetKey message is also present) |
| creditFee | int64_t | Fee (denominated in duffs) to pay for transaction | | creditFee | int64_t | 8 | Fee (denominated in duffs) to pay for transaction |
| payloadSigSize| compactSize uint | Length of the signature | | payloadSig | BLSSig | 96 | Signature from either the current key or a previous key<br>Version 1 - Previous keys are constrained to ones <= ~90 days old (51840 blocks)
| payloadSig | byte[] | Signature from either the current key or a previous key<br>Version 1 - Previous keys are constrained to ones <= ~90 days old (51840 blocks)
#### Important notes regarding closed accounts #### Important notes regarding closed accounts

22
dip-0006.md
View file

@ -187,11 +187,11 @@ The internal Dash message name is `qcontrib` and the format of the message is:
| quorumHash | uint256 | 32 | The quorum identifier | quorumHash | uint256 | 32 | The quorum identifier
| proTxHash | uint256 | 32 | The proTxHash of the contributing member | proTxHash | uint256 | 32 | The proTxHash of the contributing member
| vvecSize | compactSize uint | 1-9 | The size of the verification vector | vvecSize | compactSize uint | 1-9 | The size of the verification vector
| vvec | BLSPubKey[] | 64 * vvecSize | The verification vector | vvec | BLSPubKey[] | 48 * vvecSize | The verification vector
| ephemeralPubKey | BLSPubKey | 64 | Ephemeral BLS public key used to encrypt secret key contributions | ephemeralPubKey | BLSPubKey | 48 | Ephemeral BLS public key used to encrypt secret key contributions
| skCount | compactSize uint | 1-9 | Number of encrypted secret key contributions | skCount | compactSize uint | 1-9 | Number of encrypted secret key contributions
| skContributions | byte[] | 32 * skCount | Secret key contributions encrypted to recipient masternodes’ BLS public operator key | skContributions | byte[] | 32 * skCount | Secret key contributions encrypted to recipient masternodes’ BLS public operator key
| sig | BLSSig | 32 | BLS signature, signed with the operator key of the contributing masternode | sig | BLSSig | 96 | BLS signature, signed with the operator key of the contributing masternode
### 3. Complaining phase ### 3. Complaining phase
@ -231,7 +231,7 @@ The internal Dash message name is `qcomplaint` and the format of the message is:
| badMembers | byte[] | (bitSize + 7) / 8 | The bad members bitvector | badMembers | byte[] | (bitSize + 7) / 8 | The bad members bitvector
| complaintsBitSize | compactSize uint | 1-9 | Number of bits in the complaints bitvector | complaintsBitSize | compactSize uint | 1-9 | Number of bits in the complaints bitvector
| complaints | byte[] | (bitSize + 7) / 8 | The complaints bitvector | complaints | byte[] | (bitSize + 7) / 8 | The complaints bitvector
| sig | BLSSig | 32 | BLS signature, signed with the operator key of the contributing masternode | sig | BLSSig | 96 | BLS signature, signed with the operator key of the contributing masternode
### 4. Justification phase ### 4. Justification phase
@ -265,7 +265,7 @@ The internal Dash message name is `qjustify` and the format of the message is:
| skContributionsCount | compactSize uint | 1-9 | Number of unencrypted secret key contributions | skContributionsCount | compactSize uint | 1-9 | Number of unencrypted secret key contributions
| skContributionMembers | uint32[] | 4 * count | Indexes of the members for which justifications are provided | skContributionMembers | uint32[] | 4 * count | Indexes of the members for which justifications are provided
| skContributions | BLSSecKey[] | 32 * count | Unencrypted secret key contributions for the members contained in skContributionMembers | skContributions | BLSSecKey[] | 32 * count | Unencrypted secret key contributions for the members contained in skContributionMembers
| sig | BLSSig | 32 | BLS signature, signed with the operator key of the contributing masternode | sig | BLSSig | 96 | BLS signature, signed with the operator key of the contributing masternode
### 5. Commitment phase ### 5. Commitment phase
@ -309,10 +309,10 @@ The internal Dash message name is `qpcommit` and the format of the message is:
| proTxHash | uint256 | 32 | The proTxHash of the committing member | proTxHash | uint256 | 32 | The proTxHash of the committing member
| validMembersSize | compactSize uint | 1-9 | Bit size of the validMembers bitvector | validMembersSize | compactSize uint | 1-9 | Bit size of the validMembers bitvector
| validMembers | byte[] | (bitSize + 7) / 8 | Bitset of valid members in this commitment | validMembers | byte[] | (bitSize + 7) / 8 | Bitset of valid members in this commitment
| quorumPublicKey | BLSPubKey | 64 | The quorum public key | quorumPublicKey | BLSPubKey | 48 | The quorum public key
| quorumVvecHash | uint256 | 32 | The hash of the quorum verification vector | quorumVvecHash | uint256 | 32 | The hash of the quorum verification vector
| quorumSig | BLSSig | 32 | Threshold signature, signed with the threshold signature share of the committing member | quorumSig | BLSSig | 96 | Threshold signature, signed with the threshold signature share of the committing member
| sig | BLSSig | 32 | BLS signature, signed with the operator key of the contributing masternode | sig | BLSSig | 96 | BLS signature, signed with the operator key of the contributing masternode
### 6. Finalization phase ### 6. Finalization phase
@ -356,10 +356,10 @@ The internal Dash message name is `qfcommit` and the format of the message is:
| signers | byte[] | (bitSize + 7) / 8 | Bitset representing the aggregated signers of this final commitment | signers | byte[] | (bitSize + 7) / 8 | Bitset representing the aggregated signers of this final commitment
| validMembersSize | compactSize uint | 1-9 | Bit size of the validMembers bitvector | validMembersSize | compactSize uint | 1-9 | Bit size of the validMembers bitvector
| validMembers | byte[] | (bitSize + 7) / 8 | Bitset of valid members in this commitment | validMembers | byte[] | (bitSize + 7) / 8 | Bitset of valid members in this commitment
| quorumPublicKey | BLSPubKey | 64 | The quorum public key | quorumPublicKey | BLSPubKey | 48 | The quorum public key
| quorumVvecHash | uint256 | 32 | The hash of the quorum verification vector | quorumVvecHash | uint256 | 32 | The hash of the quorum verification vector
| quorumSig | BLSSig | 32 | Recovered threshold signature | quorumSig | BLSSig | 96 | Recovered threshold signature
| sig | BLSSig | 32 | Aggregated BLS signatures from all included commitments | sig | BLSSig | 96 | Aggregated BLS signatures from all included commitments
### 7. Mining phase ### 7. Mining phase

21
dip-0006/bls_signature_scheme.md
View file

@ -110,23 +110,26 @@ We chose to enforce distinct messages when signing with a secret key. Dash’s i
## BLS Curves used ## BLS Curves used
The BLS signature scheme requires pairing-friendly curves to be used. Multiple curves with different security, performance and space characteristics have been proposed by different parties. At the time this document was written, no decision had been made as to which curve would be used. The BLS signature scheme requires pairing-friendly curves to be used, of which only a few suitable exist. Dash is
using the BLS12-381 with reversed G1 and G2 groups. A specification can be found in the Chia [bls-signatures](https://github.com/Chia-Network/bls-signatures/blob/master/SPEC.md)
However, the choice of the specific curve should have no influence on the scheme itself, how BLS is used or what is possible. repository.
This document will be updated when a decision has been made on which curve to use.
## Serialization format of BLS primitives ## Serialization format of BLS primitives
It is necessary to serialize BLS primitives into a byte representation so that they can be used inside other serialized data structures. How this is performed depends on the curves and libraries used. This has not been defined yet and this document will be updated later. It is necessary to serialize BLS primitives into a byte representation so that they can be used inside other serialized data structures.
The serialization format is described in the Chia [bls-signatures](https://github.com/Chia-Network/bls-signatures/blob/master/SPEC.md)
repository.
Until then, all DIPs will use placeholders types for the BLS primitives and assume a fixed size. These placeholder type are: The size of individual BLS primitives is fixed:
| Type | Size | Description | | Type | Size | Description |
| -- | -- | -- | | -- | -- | -- |
| BLSSecKey | 32 | BLS secret key | BLSSecKey | 32 | BLS secret key
| BLSPubKey |64 | BLS public key | BLSPubKey | 48 | BLS public key
| BLSSig |32 | BLS signature | BLSSig | 96 | BLS signature
Please note that there is no length field before the primitives serialized data. This is different from ECDSA signatures
where a compact size integer is prepended.
## Copyright ## Copyright

4
dip-0007.md
View file

@ -110,7 +110,7 @@ The internal Dash message name is `qbsigshares` and the format of the message is
| messageHash | uint256 | 32 | The message hash | | messageHash | uint256 | 32 | The message hash |
| shareCount | compactSize uint | 1-9 | The number of signature shares in this batch | | shareCount | compactSize uint | 1-9 | The number of signature shares in this batch |
| shareMembers | uint32[] | 4 * shareCount | Member indexes of the shares in this batch | | shareMembers | uint32[] | 4 * shareCount | Member indexes of the shares in this batch |
| shareSigs | BLSSig[] | 32 * shareCount | The signature shares | | shareSigs | BLSSig[] | 96 * shareCount | The signature shares |
### Recovered threshold signatures ### Recovered threshold signatures
@ -132,7 +132,7 @@ The internal Dash message name is `qsigrec` and the format of the message is:
| quorumHash | uint256 | 32 | The quorum identifier | | quorumHash | uint256 | 32 | The quorum identifier |
| id | uint256 | 32 | The signing request id | | id | uint256 | 32 | The signing request id |
| messageHash | uint256 | 32 | The message hash | | messageHash | uint256 | 32 | The message hash |
| thresholdSig | BLSSig | 32 | The final recovered threshold signature | | thresholdSig | BLSSig | 96 | The final recovered threshold signature |
## Internal high-level API ## Internal high-level API