<p>I am switching from electrum to bitcoind. On <code>electrum</code> is function <code>paytomany</code> which accept usual bitcoin amounts like <code>0.0001</code>. But why method sendtomany accept only double-precision floating point numbers? Maybe there is another option for that purpose and I just missed it?</p>

CC BY-SA 4.0
2021-04-27T18:46:21.007Z
What is the difference between `0.0001` and "floating point numbers"? The Bitcoin Core RPC accepts amounts either as strings or as numbers (JSON has no concept of floating-point or double precision; everything is just a "number").
Pieter Wuille
CC BY-SA 4.0
2021-04-27T20:53:32.660Z
it only allow number like 0.02, 0.01 etc, only two digits
Oleksandr IY
CC BY-SA 4.0
2021-04-27T21:20:16.047Z
That's just wrong. Any valid amount can be provided in the JSON-RPC interface or the GUI (meaning up to 8 digits after the dot, because BTC can be subsidivided into 10^8 units).
Pieter Wuille
<bitcoind>
bitcoind: why sendmany allows only double-precision floating point numbers?
Oleksandr IY
# bitcoind: why sendmany allows only double-precision floating point numbers?

(Asked by: username_0 on 2021-04-27)

I am switching from electrum to bitcoind. On `electrum` is function `paytomany` which accept usual bitcoin amounts like `0.0001`. But why method sendtomany accept only double-precision floating point numbers? Maybe there is another option for that purpose and I just missed it?

**Tags:** bitcoind

> **Comments:**
> **username_1**: What is the difference between `0.0001` and "floating point numbers"? The Bitcoin Core RPC accepts amounts either as strings or as numbers (JSON has no concept of floating-point or double precision; everything is just a "number").  
> **username_0**: it only allow number like 0.02, 0.01 etc, only two digits  
> **username_1**: That's just wrong. Any valid amount can be provided in the JSON-RPC interface or the GUI (meaning up to 8 digits after the dot, because BTC can be subsidivided into 10^8 units).  

---

## 0 answers

