[FEATURE]: Add system call to read contract metadata

[joticajulian]

Is there an existing issue for this?

• I have searched the existing issues

New feature

As a smart contract developer I would like to have a system call to read contract metadata (authorizations flags, and bytecode).
Use case example: Fogata.
In Fogata we have a contract to submit and approve new mining pools. The new pools must upload a valid fogata contract. However, the approval needs to be done by a centralized party because there is no way to read the bytecode from the new pools in a decentralized way.

Anything else?

No response

[mvandeberg]

I don't have any problems with this living in Chain, but it could also live in Contract Meta Store.

[roaminro]

@joticajulian you could also get around that by implementing a function in Fogata that is called to register a contract, here's what you could do in this function:

• get all the operations included in the current transaction (System.getTransactionField('operations'))
• check that there are only 2 operations:
  • 1st operation is upload_contract:
    • check that it has the different authorizes overriden the way you want
    • check the bytecode's hash
  • 2nd operation is the operation that called your register contract in the first place

This should be enough to validate that the contract uploaded is what you expect it to be (although it doesn't solve the other issue you mentionned regarding the storage)

[koinos-ci]

This issue is stale because it has been open for 30 days with no activity.

[mvandeberg]

This is going to need governance approval.

A tentative proposition:

Handle this upgrade in two phases. Phase one implements it as a contract to provide the behavior in the near term. Phase two is providing an optimized thunk implementation to keep mana costs low and provide the thunk at genesis in the framework.