From ec27832184abc8713178b52d71d78642e9f384f5 Mon Sep 17 00:00:00 2001 From: Wo Jake Date: Mon, 17 Jul 2023 18:57:43 +0800 Subject: [PATCH] Update max no. of signers per signer list --- .../transactions/transaction-common-fields.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/references/protocol-reference/transactions/transaction-common-fields.md b/content/references/protocol-reference/transactions/transaction-common-fields.md index 7878c8e2ff..b4603a6161 100644 --- a/content/references/protocol-reference/transactions/transaction-common-fields.md +++ b/content/references/protocol-reference/transactions/transaction-common-fields.md @@ -154,7 +154,7 @@ Transaction replay attacks are theoretically possible, but require specific cond ## Signers Field -The `Signers` field contains a [multi-signature](multi-signing.html), which has signatures from up to 8 key pairs, that together should authorize the transaction. The `Signers` list is an array of objects, each with one field, `Signer`. The `Signer` field has the following nested fields: +The `Signers` field contains a [multi-signature](multi-signing.html), which has signatures from up to 32 key pairs, that together should authorize the transaction. The `Signers` list is an array of objects, each with one field, `Signer`. The `Signer` field has the following nested fields: | Field | Type | [Internal Type][] | Description | |:----------------|:-------|:------------------|:--------------------------------|