-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Should we require suppliers to stake a deposit? #78
Comments
I think this is something we want to add. This would resolve #79 and also give us flexibility. |
The more I consider this, the more I think this is necessary. There are other abuses of the platform we can mitigate by having a stake. For example, if an address floods the Firebase or IPFS API, we can cite a ToS violation and punish the attacker by claiming the deposit. |
See #105 |
It would be helpful for someone to map out the minimum dollar amounts that every party would get paid in the case of reporting and dispute resolution. |
The biggest reason to require a stake for the supplier is that without it, there is no incentive for a supplier to award payment for the contract. They can simply let the contract expire and force the engineer to submit the timeout transaction themselves. If we require a supplier deposit, it incentivizes the supplier to accept in a timely fashion. If they do not, the engineer can receive the supplier stake as compensation for the supplier being non-responsive. |
IMO - we should not do this for MVP. We should just minimum amounts. Instead, I'd propose we ask our users after launch what they want. I think a huge thing will be supporting other ERC20 tokens. |
Not necessary for MVP, removing tag. |
Staked deposits by the suppliers would accomplish:
Amount could be a fixed amount ($50) or a percentage (6%) whichever is greater.
The text was updated successfully, but these errors were encountered: