Query about project.

[GHexxerBrdv]

Hey, i have reached here from X. and i want to contribute. But i don't know the actual project scope. Like what should i have to develop and what the project is doing?
Can anyone help ma regarding this?

[mudgen]

HI @GHexxerBrdv , thanks for reaching out!

I suggest first reading the README, then the CONTRIBUTING document. Those provide the scope and what can be done to help. Happy to have more contributions. If you have further questions, please ask them.

[GHexxerBrdv]

Also the question regarding the library and the actual EIP. Like in your code base the EIP173 has been developed, in which the library has been developed and the contract has been developed. And i got an idea that library is used for user who wants their custom logic in facet. But for what the actual contract has been used? Like it is same as ownable contract in openzeppelin which we can just inherit in our logic to use?

[mudgen]

You are starting to get it. People create their own diamonds using the contracts (called facets) that Compose provides for them, plus their own custom facets.

OpenZepplelin requires using inheritance to use their contracts. People can certainly use inheritance with Compose, and sometimes they will have to in order to modify functionality, but we will have another way to do it without using inheritance. We will be introducing a new way to deploy contracts that do not require inheritance, but we have not developed that yet, but that will be a major part of Compose. We are doing some pretty new stuff (but the theory is old).

[GHexxerBrdv]

Thanks for clarification, Can you distinguish between the library contract and the actual contract used in every EIP's. I am bit confused in that.

[GHexxerBrdv]

@mudgen

[mudgen]

Hi @GHexxerBrdv, I'm not really sure I understand your question. Look in the Compose contracts, the files that start with "Lib" are Solidity libraries, and the files that end in "Facet" are contracts.