Add host functions that calculate contract IDs from inputs

[leighmcculloch]

We need a set of host functions that will return contract ID (as Bytes) given a set of inputs.

We have the following functions that can create contracts:

rs-soroban-env/soroban-env-common/src/env.rs

Lines 307 to 321 in 4f2f3a2

	{"3", fn create_contract_from_ed25519(v: Object, salt: Object, key: Object, sig: Object) -> Object}
	{"4", fn create_contract_from_contract(v: Object, salt: Object) -> Object}
	{"5", fn create_token_from_ed25519(salt: Object, key: Object, sig: Object) -> Object}
	{"6", fn create_token_from_contract(salt: Object) -> Object}
	{"7", fn create_token_from_asset(asset: Object) -> Object}
	/// Create a contract using the source account and salt as input
	/// to the contract ID that gets created. Pass as arguments a
	/// Bytes for the wasm code and a Bytes for the salt. Returned
	/// will be a Bytes of length 32 bytes.
	{"8", fn create_contract_from_source_account(v: Object, salt: Object) -> Object}
	/// Create a token contract using the source account and salt
	/// as input to the contract ID that gets created. Pass as
	/// arguments a Bytes for the salt. Returned
	/// will be a Bytes of length 32 bytes.
	{"9", fn create_token_from_source_account(salt: Object) -> Object}

In total we need to add 12 new host functions:

• 7 new host functions that are counter-parts to the host functions above, that will return the contract ID that will be used if the deployment was to occur by calling the respective function.

  • get_contract_id_contract_from_ed25519(salt: Object, key: Object) -> Object
  • get_contract_id_contract_from_contract(salt: Object) -> Object
  • get_contract_id_contract_from_source_account(salt: Object) -> Object
  • get_contract_id_token_from_ed25519(salt: Object, key: Object) -> Object
  • get_contract_id_token_from_contract(salt: Object) -> Object
  • get_contract_id_token_from_source_account(salt: Object) -> Object
  • get_contract_id_token_from_asset(asset: Object) -> Object

• 2 new host functions for getting the contract ID for a deployment from contract that isn't the currently executing contract.

  • get_contract_id_contract_from_other_contract(contract_id: RawVal, salt: Object) -> Object
  • get_contract_id_token_from_other_contract(contract_id: RawVal, salt: Object) -> Object

We can omit any of these host functions that would always return the same value given the same inputs. For example, I expect we can omit all the token functions except the one that accepts an asset,

Dependent on #537
Blocking stellar/rs-soroban-sdk#730

[jayz22]

@leighmcculloch Is this issue still relevant? Most of the mentioned host functions have been removed and the mentioned issue has been closed.

[leighmcculloch]

Yeah it should be possible for us to write an SDK function that helps a developer predetermine a contract ID that would be the contract ID of a contract when deployed.

[leighmcculloch]

The infrastructure around deployments has changed a lot, so the examples in the original issue are out of date, but the problem remains.

[jayz22]

We currently have two host functions for creating a contract:

                    "name": "create_contract",
                    "args": [
                        {
                            "name": "deployer",
                            "type": "AddressObject"
                        },
                        {
                            "name": "wasm_hash",
                            "type": "BytesObject"
                        },
                        {
                            "name": "salt",
                            "type": "BytesObject"
                        }
                    ],

                    "name": "create_asset_contract",
                    "args": [
                        {
                            "name": "serialized_asset",
                            "type": "BytesObject"
                        }                        
                    ],

So we just need two additional host functions given the same arguments and returns the contract_id without creating?

2 new host functions for getting the contract ID for a deployment from contract that isn't the currently executing contract.

@leighmcculloch Can you confirm if this statement is outdated?

[leighmcculloch]

I think we could probably defer this. I suspect someone will need it, but it can be added at any point.

[jayz22]

@leighmcculloch I've created the PR above which adds two new host functions corresponding to contract and asset contract. I think this should cover all the scenarios originally requested to unblock the sdk? Let me know if that's not the case.

[leighmcculloch]

@jayz22 It looks great 👏🏻. That was fast!