02Sheet 02.03.041 · Entries
An executable-reference entry keyed by SCV_EXECUTABLE_TAG
CA1 stores the v1 kit Wasm hash under an SCV_EXECUTABLE_TAG key "kit" (CAP-0085): other contracts may run that Wasm by reference.
FIG. · Where it sits · inside LedgerCloseMetaCAP-0085 · H-D11
ContractData keyed by SCV_EXECUTABLE_TAG
The shape
CA1 stores the v1 kit Wasm hash under an SCV_EXECUTABLE_TAG key "kit" (CAP-0085): other contracts may run that Wasm by reference.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 2,588 B | 17349a8fefb5… |
p28-mainnet-generated | P28 | mainnet passphrase | generated by stellar-core v30.0.0 | 2,580 B | 58f12b2b5add… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 2,588 B | df1ced051397… |
p28-testnet-generated | P28 | testnet passphrase | generated by stellar-core v30.0.0 | 2,580 B | 780b128c2138… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The key is executable_tag "kit". | some change where 2 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 executable-ref.tag-entry · compiled from catalog/executable-ref.tag-entry.json · entry.json
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.
One contract, one key, persistent and temporary: two different entries
put_all("dup") writes the same key in persistent and temporary storage and in instance storage.