02Sheet 02.03.034 · Entries

A Stellar Asset Contract deployed from a classic asset

CREATE_CONTRACT (v1 host function) with a contract-ID preimage from the asset XPF: the instance's executable is stellar_asset, not a Wasm hash.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0046 · H-D5
HostFunction.CREATE_CONTRACT from ContractIdPreimage.FROM_ASSET; executable STELLAR_ASSET

The shape

CREATE_CONTRACT (v1 host function) with a contract-ID preimage from the asset XPF: the instance's executable is stellar_asset, not a Wasm hash. Readers that expect every contract to have Wasm code fail on SACs.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.02,652 B479c338154e5…
p28-mainnet-generatedP28mainnet passphrasegenerated by stellar-core v30.0.02,644 Bd820d4bd411d…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.02,652 Bb8777a679fe9…
p28-testnet-generatedP28testnet passphrasegenerated by stellar-core v30.0.02,644 B56428ae250db…

What a correct reader returns

A correct reader findsValueBacked by
The preimage is from the asset XPF.XPFconstructionsnapshotcorewalker
The created instance's executable is stellar_asset.some change where 1 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 contract.sac-deploy-from-asset · compiled from catalog/contract.sac-deploy-from-asset.json · entry.json

On this page