2018-07-10 18:44:30 +00:00
|
|
|
GetPublicKey.address_n max_count:8
|
|
|
|
|
GetPublicKey.ecdsa_curve_name max_size:32
|
|
|
|
|
GetPublicKey.coin_name max_size:21
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-07-10 18:44:30 +00:00
|
|
|
PublicKey.xpub max_size:113
|
2024-02-23 00:03:54 +00:00
|
|
|
PublicKey.descriptor type:FT_IGNORE
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-07-10 18:44:30 +00:00
|
|
|
GetAddress.address_n max_count:8
|
|
|
|
|
GetAddress.coin_name max_size:21
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-07-10 18:44:30 +00:00
|
|
|
Address.address max_size:130
|
2021-02-03 14:58:00 +00:00
|
|
|
Address.mac type:FT_IGNORE
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-07-10 18:44:30 +00:00
|
|
|
SignTx.coin_name max_size:21
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-07-10 18:44:30 +00:00
|
|
|
SignMessage.address_n max_count:8
|
|
|
|
|
SignMessage.message max_size:1024
|
|
|
|
|
SignMessage.coin_name max_size:21
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-07-10 18:44:30 +00:00
|
|
|
VerifyMessage.address max_size:130
|
|
|
|
|
VerifyMessage.signature max_size:65
|
|
|
|
|
VerifyMessage.message max_size:1024
|
|
|
|
|
VerifyMessage.coin_name max_size:21
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-07-10 18:44:30 +00:00
|
|
|
MessageSignature.address max_size:130
|
|
|
|
|
MessageSignature.signature max_size:65
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-08-27 17:06:11 +00:00
|
|
|
TransactionType.inputs max_count:1
|
|
|
|
|
TransactionType.bin_outputs max_count:1
|
|
|
|
|
TransactionType.outputs max_count:1
|
|
|
|
|
TransactionType.extra_data max_size:1024
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-08-27 17:06:11 +00:00
|
|
|
TxInputType.address_n max_count:8
|
|
|
|
|
TxInputType.prev_hash max_size:32
|
|
|
|
|
TxInputType.script_sig max_size:1650
|
2020-05-25 15:04:57 +00:00
|
|
|
TxInputType.witness max_size:109
|
2022-12-16 09:38:08 +00:00
|
|
|
TxInputType.ownership_proof max_size:147
|
|
|
|
|
TxInputType.commitment_data max_size:70
|
2020-09-23 17:34:36 +00:00
|
|
|
TxInputType.orig_hash max_size:32
|
2021-10-18 13:21:21 +00:00
|
|
|
TxInputType.script_pubkey max_size:520
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-08-27 17:06:11 +00:00
|
|
|
TxOutputType.address max_size:130
|
|
|
|
|
TxOutputType.address_n max_count:8
|
legacy: Update op_return max size to 150 bytes
The goal is to allow Trezor 1 to create TPoS contracts for Stakenet.
Last year, Stakenet introduced a hard-fork [1] to change the way TPoS contracts
are created, instead of a custom signature method, now it works with the
output from the signMessage method, while this works for Trezor T, it doesn't
work for Trezor 1 due to the 80 bytes limit on the OP_RETURN output while
Stakenet allows up to 150 bytes [2], in a gitter discussion [3] we concluded that
the change should be fine.
The hard-fork was introduced because we couldn't got our TPoS contracts PR accepted [4],
the OP_RETURN still contains the same data, its just stored in a different way:
- The TPoS address, where the coins to stake are stored, and where rewards are received.
- The merchant address, where the merchant receives its commission.
- The contract commission.
- The TPoS collateral signature (this is what uses the signMessage now).
At last, there is an example transaction creating a TPoS contract [5].
[1]: https://github.com/X9Developers/XSN/pull/154
[2]: https://github.com/X9Developers/XSN/blob/master/src/script/standard.h#L34
[3]: https://gitter.im/trezor/community?at=6064c41e940f1d555e2ea670
[4]: https://github.com/trezor/trezor-firmware/pull/140
[5]: https://xsnexplorer.io/transactions/858feb31097501cf68d698cde104cf778ec51ff3668e943404b549a5dd2f5792
2021-04-02 14:28:40 +00:00
|
|
|
TxOutputType.op_return_data max_size:150
|
2020-09-23 17:34:36 +00:00
|
|
|
TxOutputType.orig_hash max_size:32
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-08-27 17:06:11 +00:00
|
|
|
TxOutputBinType.script_pubkey max_size:520
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-08-27 17:06:11 +00:00
|
|
|
TxRequestDetailsType.tx_hash max_size:32
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-08-27 17:06:11 +00:00
|
|
|
TxRequestSerializedType.signature max_size:73
|
|
|
|
|
TxRequestSerializedType.serialized_tx max_size:2048
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2018-07-10 18:44:30 +00:00
|
|
|
MultisigRedeemScriptType.pubkeys max_count:15
|
|
|
|
|
MultisigRedeemScriptType.signatures max_count:15 max_size:73
|
2019-02-04 12:53:05 +00:00
|
|
|
MultisigRedeemScriptType.nodes max_count:15
|
|
|
|
|
MultisigRedeemScriptType.address_n max_count:8
|
2018-07-10 14:58:00 +00:00
|
|
|
|
2020-06-29 11:11:43 +00:00
|
|
|
HDNodePathType.address_n max_count:8
|
2020-06-09 15:46:52 +00:00
|
|
|
|
2020-09-23 11:08:26 +00:00
|
|
|
TxInput.address_n max_count:8
|
|
|
|
|
TxInput.prev_hash max_size:32
|
|
|
|
|
TxInput.script_sig max_size:1650
|
|
|
|
|
TxInput.witness max_size:109
|
2022-12-16 09:38:08 +00:00
|
|
|
TxInput.ownership_proof max_size:147
|
|
|
|
|
TxInput.commitment_data max_size:70
|
2020-09-23 17:34:36 +00:00
|
|
|
TxInput.orig_hash max_size:32
|
2021-10-18 13:21:21 +00:00
|
|
|
TxInput.script_pubkey max_size:520
|
2020-09-18 09:32:38 +00:00
|
|
|
|
2020-09-23 11:08:26 +00:00
|
|
|
TxOutput.address max_size:130
|
|
|
|
|
TxOutput.address_n max_count:8
|
legacy: Update op_return max size to 150 bytes
The goal is to allow Trezor 1 to create TPoS contracts for Stakenet.
Last year, Stakenet introduced a hard-fork [1] to change the way TPoS contracts
are created, instead of a custom signature method, now it works with the
output from the signMessage method, while this works for Trezor T, it doesn't
work for Trezor 1 due to the 80 bytes limit on the OP_RETURN output while
Stakenet allows up to 150 bytes [2], in a gitter discussion [3] we concluded that
the change should be fine.
The hard-fork was introduced because we couldn't got our TPoS contracts PR accepted [4],
the OP_RETURN still contains the same data, its just stored in a different way:
- The TPoS address, where the coins to stake are stored, and where rewards are received.
- The merchant address, where the merchant receives its commission.
- The contract commission.
- The TPoS collateral signature (this is what uses the signMessage now).
At last, there is an example transaction creating a TPoS contract [5].
[1]: https://github.com/X9Developers/XSN/pull/154
[2]: https://github.com/X9Developers/XSN/blob/master/src/script/standard.h#L34
[3]: https://gitter.im/trezor/community?at=6064c41e940f1d555e2ea670
[4]: https://github.com/trezor/trezor-firmware/pull/140
[5]: https://xsnexplorer.io/transactions/858feb31097501cf68d698cde104cf778ec51ff3668e943404b549a5dd2f5792
2021-04-02 14:28:40 +00:00
|
|
|
TxOutput.op_return_data max_size:150
|
2020-09-23 17:34:36 +00:00
|
|
|
TxOutput.orig_hash max_size:32
|
2020-09-18 09:32:38 +00:00
|
|
|
|
2020-09-23 11:08:26 +00:00
|
|
|
PrevInput.prev_hash max_size:32
|
|
|
|
|
PrevInput.script_sig max_size:1650
|
2020-09-18 09:32:38 +00:00
|
|
|
|
2020-09-23 11:08:26 +00:00
|
|
|
PrevOutput.script_pubkey max_size:520
|
2020-09-18 09:32:38 +00:00
|
|
|
|
2021-03-17 20:33:15 +00:00
|
|
|
TxAckPrevExtraDataWrapper.extra_data_chunk type:FT_IGNORE
|
|
|
|
|
|
2022-12-16 09:38:08 +00:00
|
|
|
GetOwnershipId.address_n max_count:8
|
|
|
|
|
GetOwnershipId.coin_name max_size:21
|
|
|
|
|
|
|
|
|
|
OwnershipId.ownership_id max_size:32
|
|
|
|
|
|
|
|
|
|
GetOwnershipProof.address_n max_count:8
|
|
|
|
|
GetOwnershipProof.coin_name max_size:21
|
|
|
|
|
GetOwnershipProof.ownership_ids max_count:15 max_size:32
|
|
|
|
|
GetOwnershipProof.commitment_data max_size:70
|
|
|
|
|
|
|
|
|
|
OwnershipProof.ownership_proof max_size:147
|
|
|
|
|
OwnershipProof.signature max_size:71
|
|
|
|
|
|
2022-12-22 12:27:21 +00:00
|
|
|
AuthorizeCoinJoin.coordinator max_size:37
|
|
|
|
|
AuthorizeCoinJoin.address_n max_count:8
|
|
|
|
|
AuthorizeCoinJoin.coin_name max_size:21
|
|
|
|
|
|
2023-01-02 19:10:34 +00:00
|
|
|
CoinJoinRequest.mask_public_key max_size:33
|
|
|
|
|
CoinJoinRequest.signature max_size:64
|
2022-12-22 12:27:21 +00:00
|
|
|
|
2021-03-17 20:33:15 +00:00
|
|
|
# Unused messages.
|
2021-01-12 17:56:10 +00:00
|
|
|
TxAckPaymentRequest skip_message:true
|
|
|
|
|
PaymentRequestMemo skip_message:true
|