02Sheet 02.03.112 · Entries

A 28-byte text memo that is not valid UTF-8, mapped into the transfer event

MEMO_TEXT holds 28 raw bytes that are not UTF-8 (the maximum length).

FIG. · Where it sits · inside LedgerCloseMetaCAP-0067 · H-B5 · H-A6
MEMO_TEXT bytes that are not UTF-8
MEMO_TEXT carried into the transfer event as to_muxed_id
string

The shape

MEMO_TEXT holds 28 raw bytes that are not UTF-8 (the maximum length). CAP-0067 copies it into the payment's transfer event as to_muxed_id (a string). Readers that decode either as UTF-8 lose or mangle it.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.03,708 Bbca68e8dd94e…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.03,708 B14208217f729…

What a correct reader returns

A correct reader findsValueBacked by
The memo text is 28 bytes, first ff fe 00.\xff\xfe\0\xc3(\xed\xa0\x80xdrproof-not-utf8-20constructionsnapshotcorewalker
The transfer event carries the same bytes as to_muxed_id.some change where 2 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 memo.text-not-utf8 · compiled from catalog/memo.text-not-utf8.json · entry.json

On this page