-
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
Potential issue: Overfunded Loan #52
Comments
True. Is it common practice to have people be responsible for their own mistakes, in EthDev? |
In the case of the ERC20 token, the user is responsible for their activities, |
@tspoff do you have any thoughts on this? |
There is a scenario where an overfunded loan would cause an issue:
A few possible solutions:
|
I've added an implementation of approach (1) in this commit. Borrower can use |
Freezing the tokens in the smart Contract is not my first choice, |
I like the idea on discord by @onggunhao , |
Further thinking: |
@adibas03 Do you mean allowing the I think this shouldn't be an issue if the To note: in that scenario ( For example: They basically will be getting interest on 50,000 Dai lent out at 6% interest, split up among 48,000 shareholders. Good deal! |
Yes, the So, in the case of: The 5000 Dai is taken as |
With the implementation of the ERC20 stable coin,
more than the principal can be sent to the smart contracts as described in #32 ,
This becomes a problem if a user natively sends tokens to the contract address during the fund process, which means the user can send any amount, and will not be recorded as a contributor to the crowdloan, and will get not repayment.
The issue to the borrower can be removed, by removing limitation of the amount of
principalDisbursed
been worked on by @onggunhao , so any amount can be disbured, and that would be used in calculating the repayment.The problem to the sender of the said funds, is that they can not get the funds back, and it would be sent to the contributors as part of the repayment, which the sender will not partake of.
The text was updated successfully, but these errors were encountered: