02Sheet 02.03.124 · Entries

CREATE_ACCOUNT: the new account appears as a CREATED entry and as a CAP-0067 transfer event

Two CREATE_ACCOUNT operations in one transaction, each funding a new account with 1000 XLM.

FIG. · Where it sits · inside LedgerCloseMetapre-cap · CAP-0067 · H-E1
CreateAccountOp emits a CAP-0067 transfer event of native XLM to the new account

The shape

Two CREATE_ACCOUNT operations in one transaction, each funding a new account with 1000 XLM. Each operation's meta holds the funder's state and update and the new account as a created entry, and, since CAP-0067, a transfer event of native XLM from the funder to the new account. Readers that count transfer events as payments double-count account funding; readers that only watch payment operations miss it.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.02,740 Bd386894f0344…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.02,740 B6479efb2b018…

What a correct reader returns

A correct reader findsValueBacked by
Operation 0 succeeds.successsnapshotcorewalker
The new account alice is created with 10000000000 stroops.some change where 2 fields matchconstructionsnapshotcorewalker
A transfer event moves the same 10000000000 stroops of native XLM from root to alice.
p30-mainnet-generated
some change where 4 fields matchconstructionsnapshotcorewalker
A transfer event moves the same 10000000000 stroops of native XLM from root to alice.
p30-testnet-generated
some change where 4 fields matchconstructionsnapshotcorewalker

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 event.classic.create-account-transfer · compiled from catalog/event.classic.create-account-transfer.json · entry.json

On this page