-
Notifications
You must be signed in to change notification settings - Fork 2.6k
seal: code_hash queries #2346
Comments
This is interesting for a contract to be able to trust another contract. For example a cookie-contract that is only writtable by a erc20 contract. The account will say to erc20 hello I want to use you and this is my cooke-contract, and erc20 will store the data he wants to store in this one and trusting by its code_hash. Although this mecanism is not entirely needed due to CREATE2 properties because the address of a contract contains the code_hash, user and input_data so user can just say hello use this contract, it has been created by him with that input. |
Good point on CREATE2. However, I believe that
|
Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. |
Closed by #10933 |
It might be useful to allow contracts to query their own
code_hash
. One thing that this would allow is to create contracts with identical codes.Another possibility is to allow contracts to query
code_hash
of another contract specified by some address.These two are not required for MVP and they are also not interdependent and can be delivered separately.
The text was updated successfully, but these errors were encountered: