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

Implement escrow/dispute management #21

Open
bitgamma opened this issue Mar 19, 2020 · 0 comments
Open

Implement escrow/dispute management #21

bitgamma opened this issue Mar 19, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@bitgamma
Copy link
Contributor

At the moment all payment transactions are final and the funds are directly transfer from buyer to merchant. We need a mechanism to revert malicious transactions. What we already mitigate is

  1. Caching of transactions. When a transaction is created it expires after x (currently 10) blocks are elapsed, so it must be sent immediately on creation.
  2. Multiple transactions. The contract only accepts payment requests at least x (currently 5) blocks apart, so in a single tap you can only create 1 valid transaction.
  3. Maximum tx amount. This sets the limit on how much can be transferred in one payment.

What we want to mitigate is the merchant showing a different amount on the POS screen from what is actually being requested and also unauthorized taps. An escrow and a reputation system could help identify and punish malicious actors.

@bitgamma bitgamma added the enhancement New feature or request label Mar 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant