02Sheet 02.03.035 · Entries
A contract Wasm upload creates a contract-code entry
UPLOAD_CONTRACT_WASM: the result is the Wasm hash; a contract_code entry and its TTL are created.
FIG. · Where it sits · inside LedgerCloseMetaCAP-0046 · H-D5
UploadContractWasm creates a contract_code entry
The shape
UPLOAD_CONTRACT_WASM: the result is the Wasm hash; a contract_code entry and its TTL are created.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 5,448 B | 5e0fb433cd95… |
p28-mainnet-generated | P28 | mainnet passphrase | generated by stellar-core v30.0.0 | 5,440 B | 4957d77bbdad… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 5,448 B | 0a429dc273ef… |
p28-testnet-generated | P28 | testnet passphrase | generated by stellar-core v30.0.0 | 5,440 B | 1e3cd6bd4624… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| A contract_code entry with that hash is created. | some change where 1 fields match | constructionsnapshotcorewalker |
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 contract.upload-wasm · compiled from catalog/contract.upload-wasm.json · entry.json
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.
A mainnet contract upgrades its Wasm: an executable_update system event
A contract replaces its own code; the only trace is a system event executable_update with old and new executables.