Add DeWeb Smart-Contract Wrapper

[pivilartisant]

Proposition: Add a Deweb smart contract wrapper (and other things) to Massa Web3

Objective:

• create a central access point to DeWeb (and DeWeb related smart contracts) to make it easier for devs to access and use DeWeb smart contract.
• have less and cleaner deweb related imports in project

Technical blockers:

• should be none, all the functions have been implemented at least once... we might need to do some thinking around meta data but that is to be determined.

Deweb:

• Export key utils
• Create a wrapper that can be used as such : DEWEB.UploadFilesInit(...) wrapper functions should include the ones listed here
• Export of the commun deweb models

Index:

• Export of indexer address + add function that returns address depending on a networkparam

[SlnPons]

@damip could you check this issue? I'm confused about terminology here: DeWeb SC already exist. Maybe I don't get the point sorry :/

[pivilartisant]

@damip could you check this issue? I'm confused about terminology here: DeWeb SC already exist. Maybe I don't get the point sorry :/

sorry @SlnPons i meant smart-contract wrapper... just some code to make it easier for devs to use and call sc functions

[Ben-Rey]

Can we clarify this need ? I propose to start with what's needed right now and why. Then we will add functionalities incrementally as needed.

[pivilartisant]

Can we clarify this need ? I propose to start with what's needed right now and why. Then we will add functionalities incrementally as needed.

As suggested, we'll start by adding the meta-data (read and write) then determine how we proceed

[SlnPons]

@pivilartisant @thomas-senechal for this issue to be prioritised correctly, it would be good to order the list of needs listed above.
It would be too much time consuming to do everything at once. Let's try to break it down for now. Could you have a try to priorise it (and/or discuss it with Pierre for instance)?

[pivilartisant]

@pivilartisant @thomas-senechal for this issue to be prioritised correctly, it would be good to order the list of needs listed above. It would be too much time consuming to do everything at once. Let's try to break it down for now. Could you have a try to priorise it (and/or discuss it with Pierre for instance)?

hey @SlnPons https://github.com/massalabs/deweb-uploader/pull/31 this pull request (refactor) should pave the way and provide some clarity for other developers. IMO, once it is merged, this can be re-evaluated and discussed.