An XLM SAC transfer creates a G account
Since CAP-0073 the native SAC can transfer to an account that does not exist: the transfer creates it with 25 XLM.
The shape
Since CAP-0073 the native SAC can transfer to an account that does not exist: the transfer creates it with 25 XLM. There is no CREATE_ACCOUNT operation. Readers that only create accounts from CREATE_ACCOUNT miss dave.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 change order varies: 2 orderings in 20 runs | 3,292 B | 2192362c16a9… |
p28-mainnet-generated | P28 | mainnet passphrase | generated by stellar-core v30.0.0 | 3,284 B | d8348cf5c6f1… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 3,292 B | 1bfa62521a16… |
p28-testnet-generated | P28 | testnet passphrase | generated by stellar-core v30.0.0 | 3,284 B | 8a32e3393265… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| dave's account is created. | some change where 1 fields match | snapshotcorewalker |
| The transfer event names dave. | some change where 1 fields match | snapshotcorewalker |
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 walkerEntry id sac.xlm-transfer-creates-account · compiled from catalog/sac.xlm-transfer-creates-account.json · entry.json
SAC trust() on an existing trustline succeeds and changes nothing
Calling trust() again for bob, whose trustline exists, succeeds with no ledger change and no event: a reader must not create, duplicate or touch anything.
An XLM SAC transfer to a muxed contract address (W…)
CAP-0084 muxed contract address: the argument is SC_ADDRESS_TYPE_MUXED_CONTRACT (a W… strkey); the event names the contract (C…) and carries to_muxed_id 84; the balance is the contract's.