-
Notifications
You must be signed in to change notification settings - Fork 2
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
Integration of Aave to support loans with NFTs as collateral #156
Conversation
…ontracts into feature/aave_integration
…ontracts into feature/aave_integration
repayment condition
interest rate mode
remove treasury & dynamic fee
require( | ||
_nftAmount == 0 || (_nftAmount == 1 && token.ownerOf(uint256(_did)) == msg.sender), | ||
_nftAmount == 0 || | ||
(_nftAmount == 1 && (nftOwner == msg.sender || nftOwner == _lockConditionAddress)), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If lockConditionAddress
has an NFT and this contract is able to transfer them, then somebody could create another condition, and use it to transfer the NFT away.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will be resolved as an independent issue
contracts/conditions/defi/aave/AaveCollateralDepositCondition.sol
Outdated
Show resolved
Hide resolved
…eters to hash and fulfill functions
… the previous one
…Address as part of the conditions
…a hash and fulfill parameter
…ect against hash collisions between condition ids
Description
Implementation of the Aave integration:
Pending tasks
Is this PR related with an open issue?
Related to Issue #
Types of changes
Checklist: