02Sheet 02.03.044 · Entries

Address credentials V2: the signature payload is bound to the address

SOROBAN_CREDENTIALS_ADDRESS_V2 (CAP-0071-02): same fields as ADDRESS, but the signed payload includes the address.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0071 · H-B15
SorobanCredentials.SOROBAN_CREDENTIALS_ADDRESS_V2

The shape

SOROBAN_CREDENTIALS_ADDRESS_V2 (CAP-0071-02): same fields as ADDRESS, but the signed payload includes the address. Readers that only know source-account and ADDRESS credentials fail to parse it or verify it.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.02,912 B33bc74baabea…
p28-mainnet-generatedP28mainnet passphrasegenerated by stellar-core v30.0.02,904 Bbcc66f2d823d…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.02,912 B0093bfe46273…
p28-testnet-generatedP28testnet passphrasegenerated by stellar-core v30.0.02,904 Bd4914813181c…

What a correct reader returns

A correct reader findsValueBacked by
The credentials are address_v2 for bob with nonce 7102001.7102001constructionsnapshotcorewalker
bob's nonce entry is created.some change where 1 fields matchsnapshotcorewalker

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 auth.address-v2-credentials · compiled from catalog/auth.address-v2-credentials.json · entry.json

On this page