-
Notifications
You must be signed in to change notification settings - Fork 103
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
Review UTXO based Credit Notes RFC #115
Comments
So my high-level thought on all of this is that at some point we're going to need to interface with IBC transfer which uses balances and denoms. I'm not sure I see the concrete advantages of this UTXO approach over the existing account/balance approach Cosmos uses and if we do something different we will need to write the interoperability layer (i.e. IBC transfer). Also, how exactly would the UTXO model provide more privacy? It seems like everything is still traceable without something like ZKP or Monero. Couldn't a method like that provide privacy for an account/balance model too? I will summarize the current design in a separate issue so that it's easy to find and up to date, and we can compare. |
See #117. |
Re privacy: Using x/bank would probably require TEE (what Enigma is doing) or MPC like Nucypeher (which will be very slow). I'm not aware about other efficient trustless methods without escaping accounting system like x/bank. |
The benefit of the Credit Note is:
For
I don't know how extending x/banking impacts the IBC compatibility nor how difficult it is to add it to a new module. |
It seems like the key question to enable a clear assessment of the Credit Note as an option is an assessment of how much effort would be needed for IBC compatibility. How long would that assessment take? @robert-zaremba? |
Shall we summarize the review and close the task? |
Review Credit Notes RFC from @robert-zaremba
https://docs.google.com/document/d/14___kg4DWpd5QMWNKdCqFbMzUMac4qQo3GaSwMjZyi8/edit
The text was updated successfully, but these errors were encountered: