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

Claim code for AbcPay using AWS #12

Open
kensauruss opened this issue Apr 17, 2022 · 0 comments
Open

Claim code for AbcPay using AWS #12

kensauruss opened this issue Apr 17, 2022 · 0 comments

Comments

@kensauruss
Copy link

Currently sending payment in crypto is quite risky. There can be a typo in address or the wrong address is selected, then the fund is lost forever as transactions are irreversible.
There are attempts to address this issue, such as Cash Account, which addresses are shared publicly as registries. Or the barcode scanner also useful to avoid the mistake. However there are still usability issues and risks associated.
Hereby, a new proposal aim to address the risk of lost fund.

When the sender sends the fund to the recipient, there would be an option for the sender to set a claim code, together with an expiry time period (say 15m, 1h, 2h, 4h, 8h, 24h, etc...)
The claim code is autogenerated for now. Consists of 4 or 6 digits.
Once the fund is sent, the claim code must be passed to the recipient in order to claim the fund
If after the expiry period, the fund is not claim, it will be returned back to the recipient
The sender must ensure the fund is not spent before it is claimed. Otherwise the fund will be unredeemable to the users
This should be proposed at protocol level, so that the fund is locked to avoid double spending. Alternatively this could be also done at BWS layer, given that the sender has the responsibility to keep the fund intact before the recipient can claim it. This will need to be further discussed with ABC team.

@kensauruss kensauruss changed the title Claim code for AbcPay using BWS Claim code for AbcPay using AWS Apr 17, 2022
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

1 participant