[FEATURE]: Store number of updates of a specific contract

[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 know how many upgrades a specific contract has had.
Use case example: Fogata.
Before adding a new pool to the list of approved pools we have to check that the storage of the pool has not been manipulated in the past by a previous contract. Then we have to check that the submitted contract has not been upgraded in the past.
Right now, we check this by reading the history of transactions. But I would like to perform this check in a decentralized way.

Anything else?

No response

[mvandeberg]

Unlike koinos/koinos-chain#806, this issue is a bit more involved.

the storage of the pool has not been manipulated in the past by a previous contract.

I don't think this is the responsibility of the chain. Rather, the pool contract should be checking its own state and emitting a "success" event if everything looks good. Since your pool contract is not intended to be upgraded, I would focus on your second point.

Then we have to check that the submitted contract has not been upgraded in the past.

This is do-able, but it is not the responsibility of the chain. I would rely on Contract Meta Store to give current and history information on smart contracts.

But I would like to perform this check in a decentralized way.

Reading transaction history is still decentralized. You can cryptographically prove inclusion of the transaction.

[joticajulian]

Thanks Michael. Could you give an example of how can I make this cryptographic proof?

[koinos-ci]

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

[mvandeberg]

Thanks Michael. Could you give an example of how can I make this cryptographic proof?

If the contract meta store recorded which transaction included the update, you can look up which block included the transaction and the blockchain itself is the proof.

I am moving this issue to contract meta store as the correct place to add this information.

[koinos-ci]

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

[koinos-ci]

This issue was closed because it has been inactive for 14 days since being marked as stale.