Describe the kroner transfer rules in the API
This commit is contained in:
1 parent
1cb4de6f4b
commit
9886ea285b
1 file changed
+6
-1
+6
-1
@@ -694,7 +694,12 @@ rejected. A kroner amount may carry two decimals, as the storage is øre. A fee
|
||||
`fee_sats` only: `fee_ore` is never sent by a client and stays 0 in the database.
|
||||
|
||||
For `admin_cost`, the amount is sent as `leg_out_ore`, `market_id` must be absent or null,
|
||||
`lot_picks` are rejected, and a fee is rejected; the account is not required and not looked up.
|
||||
`lot_picks` are rejected, and a fee is rejected; the server stores the bank of §3.11 and the
|
||||
matching `leg_in_ore` itself.
|
||||
|
||||
For a `transfer_out`, exactly one of `leg_out_sats` and `leg_out_ore` is sent. `to_market_id` is
|
||||
required when the amount is in sats; it may be absent when the amount is in kroner, which is a
|
||||
withdrawal, and then no `transfer_in` is generated.
|
||||
|
||||
Every transaction object carries `btc_price_ore`: the price of §7.3 in øre per whole BTC, or
|
||||
null when the type has no price. For a `transfer_out` it is worked out from the consumed lots
|
||||
|
||||
Reference in new issue
Block a user