02Sheet 02.03.040 · Entries

Calling a contract whose code comes from a reference

The external-ref contract runs the v1 kit's put: its footprint must include the owner's tag entry and the referenced Wasm.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0085 · H-D11
InvokeHostFunction on an external-ref contract

The shape

The external-ref contract runs the v1 kit's put: its footprint must include the owner's tag entry and the referenced Wasm.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.02,644 Bb9b3dea25e3b…
p28-mainnet-generatedP28mainnet passphrasegenerated by stellar-core v30.0.02,636 Bb4308d3f237c…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.02,644 B8b5da2dc9074…
p28-testnet-generatedP28testnet passphrasegenerated by stellar-core v30.0.02,636 Bc880988df1be…

What a correct reader returns

A correct reader findsValueBacked by
It stores via_ref = 85 under its own address.
p30-mainnet-generated
some change where 2 fields matchconstructionsnapshotcorewalker
It stores via_ref = 85 under its own address.
p28-mainnet-generated
some change where 2 fields matchconstructionsnapshotcorewalker
It stores via_ref = 85 under its own address.
p30-testnet-generated
some change where 2 fields matchconstructionsnapshotcorewalker
It stores via_ref = 85 under its own address.
p28-testnet-generated
some change where 2 fields matchconstructionsnapshotcorewalker
The footprint reads the owner's executable_tag entry.some change where 1 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 executable-ref.invoke · compiled from catalog/executable-ref.invoke.json · entry.json

On this page