Specify Payment API

[daira]

Issue by daira
Wednesday Jul 20, 2016 at 15:31 UTC
Originally opened as zcash/zips#56

---

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.)

[daira]

Comment by nathan-at-least
Wednesday Jul 20, 2016 at 16:45 UTC

---

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

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

[daira]

Comment by nathan-at-least
Wednesday Jul 20, 2016 at 16:52 UTC

---

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.

[daira]

Comment by zookozcash
Wednesday Jul 20, 2016 at 18:54 UTC

---

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" notifications@github.com 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
zcash/zips#56 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/APp9QFNXyBUCPrv5CeOBs5zjQsm7WECIks5qXlIxgaJpZM4JQ52P
.

[daira]

Comment by ebfull
Friday Jul 22, 2016 at 02:02 UTC

---

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

[daira]

Comment by daira
Monday Sep 26, 2016 at 10:07 UTC

---

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?

[daira]

ZIPs can (as of now) be in Markdown, as well as reStructuredText or LaTeX, so the conversion isn't necessary.

[daira]

Duplicate of #2317.