ZIP: Specify Payment API about zips HOT 5 CLOSED

Re "floatish", the problem is that if we send or accept decimals in the
API, then a lot of programmers will use floats/doubles to produce or
consume those numbers, which will lead to bugs.

It's entirely possible to use a proper decimal datatype instead of
floats/doubles in all modern languages, so a potential mitigation is just
to add documentation saying "do NOT ever use floats/doubles to store or
process this. There is a library in your language that handles decimals. Go
find out and use it and nothing but it to handle these numbers."

Here's a simple example of the problems with using floats for decimals: 0.1

• 0.1 != 0.01

Not only is 0.1 times 0.1 not exactly 0.01, it isn't even the closest
possible number to 0.01.

https://web.archive.org/web/20140723054136/https://zooko.com/uri/URI:DIR2-MDMF-RO:dwvqalbdt4ax4vgupcewxljg3u:bej7hhojmpuugy77oyydmazf6uu7huiipkctih7adky7e6txavnq/klog.html#pyutil.jsonutil

On Jul 20, 2016 10:52 AM, "Nathan Wilcox" [email protected] wrote:

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.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#56 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/APp9QFNXyBUCPrv5CeOBs5zjQsm7WECIks5qXlIxgaJpZM4JQ52P
.

from zips.

Related is how to manage proving parameters: zcash/zcash#432 (comment)

Tangential topics for SPV clients: #288 delegated JoinSplit detection and #1113 delegated proving.

from zips.

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.

from zips.

Hm, is the payment API in scope for the specification?

from zips.

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?

from zips.