02Sheet 02.03.033 · Entries

A contract deployed from an address and salt

CREATE_CONTRACT_V2 from alice with salt sha256("xdrproof:kit:0"): the contract ID is derived from the network ID, the deployer and the salt.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0046 · H-D5 · H-G1
CreateContractV2 from address + salt
contract ID derived from the network ID: different in the mainnet and testnet variants of the same recipe

The shape

CREATE_CONTRACT_V2 from alice with salt sha256("xdrproof:kit:0"): the contract ID is derived from the network ID, the deployer and the salt.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.02,668 B751487df393d…
p28-mainnet-generatedP28mainnet passphrasegenerated by stellar-core v30.0.02,660 B0d2ca04b7715…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.02,668 B41c8cd4b609b…
p28-testnet-generatedP28testnet passphrasegenerated by stellar-core v30.0.02,660 B82b73a9e8baa…

What a correct reader returns

A correct reader findsValueBacked by
The instance is created for the derived contract ID.
p30-mainnet-generated
some change where 2 fields matchconstructionsnapshotcorewalker
The instance is created for the derived contract ID.
p28-mainnet-generated
some change where 2 fields matchconstructionsnapshotcorewalker
The instance is created for the derived contract ID.
p30-testnet-generated
some change where 2 fields matchconstructionsnapshotcorewalker
The instance is created for the derived contract ID.
p28-testnet-generated
some change where 2 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 contract.deploy-from-address-salt · compiled from catalog/contract.deploy-from-address-salt.json · entry.json

On this page