02Sheet 02.03.006 · Entries

Signed-payload signer

A signer whose P… strkey carries a payload. wallet-backend halted on it, then stored it as 33 bytes; this entry keeps it whole.

FIG. · SignerKey · signed payload · 44 bytesCAP-0040 · testnet ledger 4437357
TYPEED25519 KEY · 32 BYTESLENGTHPAYLOAD00000000034404ad47185a0830e91c24125e8b058216b191e27d2099fb40f924ff48ca0d287e1264ec32879b200036000003de40adbe00payload = de ad bethe bytes a 33-byte column loses (#716)
The SignerKey exactly as it sits in the ledger: type 3 (ed25519 signed payload), the account key, a payload length of 3, the payload, and one byte of XDR padding. Decoded from the P… strkey in the mined variant.

The shape

CAP-0040 added a signer type that carries a payload: the strkey starts with P and is longer than a G address (up to 165 characters for a 64-byte payload). Readers that assume every signer is a 32-byte ed25519 key truncate it or fail. wallet-backend halted ingestion on testnet ledger 4437357 (#729) and stored the signer as 33 bytes, losing the payload (#716).

FIG. · Where it sits · inside LedgerCloseMetaCAP-0040 · H-A3
SetOptionsOp.signer.key
SIGNER_KEY_TYPE_ED25519_SIGNED_PAYLOAD

Variants

One variant is mined: the real testnet ledger where wallet-backend halted. Two are generated by a standalone stellar-core v30.0.0, on the mainnet and testnet passphrases. The generated ones push the edges: a 64-byte payload (the longest allowed, a 165-character strkey), and a 29-byte payload that needs XDR padding.

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.02,904 Bc3bc44b52a51…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.02,904 B9a22f13104ed…
p28-testnet-minedP28testnet passphrasemined from history58,256 B582e694b96bf…

What a correct reader returns

A correct reader findsValueBacked by
The transaction succeeded: core applied the signed-payload signer.successsnapshotcorewalker
The mined testnet signer is the P… strkey from the wallet-backend#729 ledger, kept whole.
p28-testnet-mined
PBCK2RYYLIYOSHBEL2FQLAVRSHRH3GP3ID476SGKBV7BEZHMQ6NSAAAAAAB55LN6AANMSsnapshotcorewalker
After apply, the mined account's only signer is that full P… key (an indexer storing 33 bytes has lost the payload).
p28-testnet-mined
some change where 2 fields matchsnapshotcorewalker
Generated: the first signer carries a 64-byte payload (sha256('xdrproof:payload:a') || sha256('xdrproof:payload:b')) for bob's key; its strkey is 165 characters.
p30-mainnet-generated
PCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAABAPLCG4TV4JZWAODQ2OPNXPBFSF7DB774MDE3MVLMKFQ7PHE5HQIOGTBILGV7NGJBMP3A7I5NBRXG5PJFEDEZBYWZW72BQXUSY4R5RC7YFXCconstructionsnapshotcorewalker
Generated: the first signer carries a 64-byte payload (sha256('xdrproof:payload:a') || sha256('xdrproof:payload:b')) for bob's key; its strkey is 165 characters.
p30-testnet-generated
PCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAABAPLCG4TV4JZWAODQ2OPNXPBFSF7DB774MDE3MVLMKFQ7PHE5HQIOGTBILGV7NGJBMP3A7I5NBRXG5PJFEDEZBYWZW72BQXUSY4R5RC7YFXCconstructionsnapshotcorewalker
Generated: the second signer carries a 29-byte payload, a length that needs XDR padding (first 29 bytes of sha256('xdrproof:payload:c')).
p30-mainnet-generated
PCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAAAOS2UR5JPZSJKJ7MTYM2KD5A35N4M6CQAT7BRSYUBOTHZFDOMAAAABQCMconstructionsnapshotcorewalker
Generated: the second signer carries a 29-byte payload, a length that needs XDR padding (first 29 bytes of sha256('xdrproof:payload:c')).
p30-testnet-generated
PCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAAAOS2UR5JPZSJKJ7MTYM2KD5A35N4M6CQAT7BRSYUBOTHZFDOMAAAABQCMconstructionsnapshotcorewalker
Generated: after both operations, alice's account holds both signed-payload signers.
p30-mainnet-generated
some change where 2 fields matchconstructionsnapshotcorewalker
Generated: after both operations, alice's account holds both signed-payload signers.
p30-testnet-generated
some change where 2 fields matchconstructionsnapshotcorewalker

What it reproduces

wallet-backend#729wallet-backend#716

make replay feeds testnet ledgers 4437356–4437359 to three real wallet-backend builds through a mock stellar-rpc:

wallet-backend buildExpected verdict
79ea2acd, "upgrade to protocol 28" (#715)stores the signer as 33 bytes, losing the payload (#716)
6e5a5910, "reduce muxed addresses to their base account" (#693)halts at ledger 4437357
2c873353, "handle CAP-40 signed-payload signers" (#729)stores the full 41-byte key

The verdict is read from state: the ingest cursor and the stored signer's length. See Replay.

Check it yourself

make verify   # schema, hashes, byte-for-byte round trip, every fact above
make replay   # the wallet-backend runs (Docker, about 10 minutes cold)

On this page