Definition of Solidity practice to allow easy contract upgrades

[aaitor]

Related with: https://github.com/oceanprotocol/research/issues/13

It would be necessary to document the standard approach for creating Smart Contracts, allowing to make those easily upgradable.

List of relevant links:

• https://consensys.github.io/smart-contract-best-practices/
• https://blog.indorse.io/ethereum-upgradeable-smart-contract-strategies-456350d0557c
• https://medium.com/cardstack/upgradable-contracts-in-solidity-d5af87f0f913
• https://medium.com/rocket-pool/upgradable-solidity-contract-design-54789205276d

[H34D]

Like written above separating smart contract logic and data is a good practice. There is one concept of eternal storage that is pretty interesting in this case:

https://github.com/ethereum/EIPs/issues/930

[H34D]

Also usefull:

• https://embark.status.im/docs/
• https://truffleframework.com/docs/getting_started/project

[aaitor]

additional reading: https://blog.indorse.io/ethereum-upgradeable-smart-contract-strategies-456350d0557c

[aaitor]

@H34D , Is this in "Reviewing" state? Is there any PR associated?

[H34D]

its closed with this PR: https://github.com/oceanprotocol/dev-ocean/pull/27

[aaitor]

okay, I added some reviewers to the PR to move forward