02Sheet 02.03.017 · Entries

A pool whose two issuers sort one way as strkeys and the other as bytes

Two ARST assets whose issuers order oppositely as strkey text and as raw key bytes.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0038 · H-B1
LiquidityPoolParameters asset order by XDR bytes, not strkey text

The shape

Two ARST assets whose issuers order oppositely as strkey text and as raw key bytes. The pool ID and the asset order in the pool use XDR byte order. js-stellar-sdk#1766 compared strkey text and computed the wrong pool ID.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.0
change order varies: 14 orderings in 20 runs
4,588 B9ad012318d86…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.0
change order varies: 2 orderings in 2 runs
4,588 Bcd15eeecf183…

What a correct reader returns

A correct reader findsValueBacked by
asset_a is the ARST whose issuer comes first by bytes (GCUXRL…), not first by text (GC7VO2…).some change where 1 fields matchconstructionsnapshotcorewalker
The pool is created with the ID from the byte-ordered parameters.some change where 1 fields matchconstructionsnapshotcorewalker

Sightings

js-stellar-sdk#1766

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 asset-order.pool-issuers-text-vs-bytes · compiled from catalog/asset-order.pool-issuers-text-vs-bytes.json · entry.json

On this page