Open geofmureithi opened 1 year ago
All our contracts are ripe for interfaces. They need to be consistent in the following
Here is an example of the Token specification. Building interfaces for the current contracts will allow the reusing of different but similar contracts. This would make it easier for dApp devs to build on top of our products.
Here are some examples that can shape this process:
The interface approach would also solve the issue we have at #103. Here are the steps to think about:
This specification might prove to be helpful too.
This covers the main concepts about soroban interfaces. Let me know your thoughts @eloylp @mariopil
Switch from classic stellar asset.
Is this something the broader community is doing or is just another way of doing it ?
Switch from classic stellar asset.
Is this something the broader community is doing or is just another way of doing it ?
If we wanna work with soroban, this is the way to go. Check out timelock by soroban examples and timelock with classic assets. With smart contracts we should be using the former.
Summary
Soroban contracts provide interfaces that can be implemented in other contracts. Eg the token and stellar admin interfaces
Motivations
Currently the best use case for this is the marketplace where an interface can be used to manage listings. In this research part I am gonna be looking at how to approach it this way.
References: https://github.com/altugbakan/sorodogs/blob/main/contracts/src/interface.rs
Final conclusions We need to implement interfaces for our contracts.