exact fee and don't broadcast
This commit is contained in:
parent
d7dd6e55a2
commit
cd57c3ef45
|
@ -16,7 +16,7 @@ Revision 0.5
|
|||
10. (Server) Broadcasts payment to network and notifies client payment was accepted.
|
||||
11. (Client) If payment is accepted by server, wallet broadcasts payment
|
||||
|
||||
If at any time the payment is rejected by the server **your client should not broadcast the payment**.
|
||||
In general, the payment should not be broadcast by the client. If at any time the payment is rejected by the server **your client must not broadcast the payment**.
|
||||
Broadcasting a payment before getting a success notification back from the server will in most cases lead to a failed payment for the sender. The sender will bear the cost of paying transaction fees yet again to get their money back.
|
||||
|
||||
## Payment Request
|
||||
|
@ -35,7 +35,7 @@ On a successful request, the response will contain one header of note.
|
|||
#### Body
|
||||
* `network` - Which network is this request for (main / test / regtest)
|
||||
* `currency` - Three digit currency code representing which coin the request is based on
|
||||
* `requiredFeePerByte` - The minimum fee per byte required on this transaction, if lower than that we will reject it
|
||||
* `requiredFeePerByte` - The exact fee per byte required on this transaction. Payment will be rejected if fee rate included for the transaction is not equal to this value. _May be fractional value_ ie 0.123 sat/byte
|
||||
* `outputs` - What output(s) your transaction must include in order to be accepted
|
||||
* `time` - ISO Date format of when the invoice was generated
|
||||
* `expires` - ISO Date format of when the invoice will expire
|
||||
|
|
Loading…
Reference in New Issue