Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: change "DeFi implementation" with "DeFi services" #22

Closed
khemiriwalid opened this issue Jul 1, 2021 · 1 comment
Closed

Comments

@khemiriwalid
Copy link

DeFi protocols provide multiple services like decentralized exchange, lending & borrowing, stablecoin, etc.
We will use multiple DeFi services in order to build advanced use cases.

Example :

  • A DeFi application named "X" need to use a service from other DeFi application named "Y" ("Y" has a token named "Y token" used to consume their services ).
  • In the smart contract of "X" , there is a code that check if they have sufficient amount of 'Y token' before call "Y" services.
  • If the contract doesn't have the amount of tokens to consume "Y" service, they will use one of the decentralized exchanges like Uniswap, Balancer, Curve to swap some amount of their ETH to "Y token" in order to complete the execution of a such business logic.

So, I suggest to list the generic services provided by DeFi protocols like decentralized exchange, lending and borrowing and their famous and mass adapted protocols. Because, developers need to know those generic protocols and how to call them with smart contract code (API of each protocol).

DeFi services

@OffcierCia
Copy link
Owner

Will add new info to table today, thank you so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants