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

Feedback on ATS, HTLC counterparty risk #27

Open
fulldecent opened this issue Jun 13, 2019 · 0 comments
Open

Feedback on ATS, HTLC counterparty risk #27

fulldecent opened this issue Jun 13, 2019 · 0 comments

Comments

@fulldecent
Copy link
Contributor

The cross-chain synchronization feature of ATS is not specified. If the approach is to use a hashed time-locked contract then counterparty exists.

Economic incentive helps to ensure that:

  • Sender locks up token on sending chain
  • Receiver accepts token on receiving chain

However other outcomes are possible, resulting in unstable total supply or unsynchronized total supply.

Even though ATS says that cross-chain transactions are out of scope of the specification, the requirements it places on cross-chain transactions make them impossible when working with existing cross-chain technology.

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