Introduce deployment_id for smart contracts

[k06a]

Having deployment_id depending on deployer's deployment_id and some salt would allow to have non-interactive authorization checks between smart contracts family of the same service.

Deploying smart contract from the wallet:

deployment_id = hash(concat(hash(deployer_public_key), hash(salt)))

Deploying smart contract from the smart contract:

deployment_id = hash(concat(hash(deployer.deployment_id), hash(salt)))

I propose to discuss exact functions to be used.

[bowenwang1996]

Can you give an example of how deployment_id is used, where salt is stored, etc?

[k06a]

salt is an argument for a deployment process, which should affect deployed smart contract deployment_id. I am mostly talking about the case when smart contract deploy smart contracts, such deplyment_id would allow smart contract to perform non-interactive check is some calling smart contract is created by some factory smart contract with some salt or not.

[garikbesson]

Since there has been no activity for 5 years, I'm closing the issue. Feel free to open it if still relevant.