-
Notifications
You must be signed in to change notification settings - Fork 156
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
ZIP: Specify Payment API #56
Comments
Related is how to manage proving parameters: zcash/zcash#432 (comment) Tangential topics for SPV clients: #288 delegated JoinSplit detection and #1113 delegated proving. |
Unresolved issue: How do we represent values in the API? We want lossless representation, but we also are dealing with Bitcoin's API which may use "float-ish" numbers. Something to review and make an explicit decision on. |
Re "floatish", the problem is that if we send or accept decimals in the It's entirely possible to use a proper decimal datatype instead of Here's a simple example of the problems with using floats for decimals: 0.1
Not only is 0.1 times 0.1 not exactly 0.01, it isn't even the closest On Jul 20, 2016 10:52 AM, "Nathan Wilcox" notifications@github.com wrote:
|
Hm, is the payment API in scope for the specification? |
I'm deciding that it is not in scope for the specification, but should be maintained as a ZIP. Can someone convert https://github.com/zcash/zcash/blob/master/doc/payment-api.md to rST and submit it please? |
Placeholder. See https://zcash.slack.com/archives/paymentapi/p1468977244000002 for a discussion about how to represent amounts. (To do: that archive is not public, copy the relevant parts.)
The text was updated successfully, but these errors were encountered: