02Sheet 02.03.118 · Entries

A transaction with the maximum 2 extra signers

Preconditions v2 extraSigners<2> full: two signed-payload keys, each needing its own signature; the transaction carries three.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0021 · CAP-0040 · H-B12 · H-C4
PreconditionsV2.extraSigners at its maximum of 2
two signed-payload extra signers

The shape

Preconditions v2 extraSigners<2> full: two signed-payload keys, each needing its own signature; the transaction carries three.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.0
change order varies: 20 orderings in 20 runs
21,176 B0ec4a1c8d0a2…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.0
change order varies: 2 orderings in 2 runs
21,176 B38004ed92e2d…

What a correct reader returns

A correct reader findsValueBacked by
There are two extra signers.length 2constructionsnapshot
The transaction carries three signatures.length 3constructionsnapshot
Operation 0 succeeds.
p30-mainnet-generated
successsnapshotcorewalker
Operation 0 succeeds.
p30-testnet-generated
successsnapshotcorewalker

Check it yourself

make verify   # schema, hashes, the byte-for-byte round trip and every fact above
make oracle   # the facts' values, re-read by stellar-core and the schema walker

Entry id max-length.extra-signers-2 · compiled from catalog/max-length.extra-signers-2.json · entry.json

On this page