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.
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
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 change order varies: 14 orderings in 20 runs | 4,588 B | 9ad012318d86… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 change order varies: 2 orderings in 2 runs | 4,588 B | cd15eeecf183… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| asset_a is the ARST whose issuer comes first by bytes (GCUXRL…), not first by text (GC7VO2…). | some change where 1 fields match | constructionsnapshotcorewalker |
| The pool is created with the ID from the byte-ordered parameters. | some change where 1 fields match | constructionsnapshotcorewalker |
Sightings
js-stellar-sdk#1766Check 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 walkerEntry id asset-order.pool-issuers-text-vs-bytes · compiled from catalog/asset-order.pool-issuers-text-vs-bytes.json · entry.json
An issued asset with code "xlm" is not XLM
A credit_alphanum4 asset whose code is "xlm": readers that match on the code instead of the asset type treat it as native.
Every ScVal number and time type at its extreme
i64 min, u128 max, i128 min, u256 max, i256 min, timepoint and duration max, 64 bytes, a non-UTF-8 string, bool and void in one vector: storage, event and return value.