You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2019. It is now read-only.
875 author Weiwu here. We think alike - we wanted to beat ERC875 too.
Atomic offers and contingent payments are very similar to each other (both in use-cases and in format), and they should marry into one protocol; there is a school of thought (e.g. by R3 Corda) that the hash of the contingent payment terms (can be a smart-contract) is better than the terms itself so payment condition is known only when it is satisfied, for security and privacy. Furthermore, 875 atomic offers are non-binding, and a binding variant is needed. If a binding version exists, it should look very similar to a payment channel's protocol so we may step forward to marry that family as well. God how I wish to have 48 hours a day, but we won't be beating 875 for the sake of it, it has to be a meaningful marriage with plentiful of prospect.
Here is your competition https://medium.com/bitfwd/erc875-a-new-standard-for-non-fungible-tokens-and-cheap-atomic-swaps-93ab85b9e7f9
What's better than a standard? I an implementation that you can use today!
Let's beat them to market and obviate the need for a ERC-875 standard.
The text was updated successfully, but these errors were encountered: