core-lightning/doc/schemas/pay.request.json
Rusty Russell 6c54e0e7e7 pay: add absolute "maxfee" parameter.
This is what LND does, and it's better for upper layers than trying to
twist our maxfeepercent / exemptfee heuristics to suit.

(I don't remember who complained about this, sorry!)

I'm doing this now because I want to add YA parameter next!

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Changelog-Added: JSON-RPC: `pay` has new parameter `maxfee` for setting absolute fee (instead of using `maxfeepercent` and/or `exemptfee`)
2022-04-04 20:26:04 +09:30

54 lines
861 B
JSON

{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"additionalProperties": false,
"required": [
"bolt11"
],
"properties": {
"bolt11": {
"type": "string"
},
"msatoshi": {
"type": "msat"
},
"label": {
"type": "string"
},
"riskfactor": {
"type": "number"
},
"maxfeepercent": {
"type": "number"
},
"retry_for": {
"type": "u16"
},
"maxdelay": {
"type": "u16"
},
"exemptfee": {
"type": "msat"
},
"localofferid": {
"type": "hex"
},
"exclude": {
"type": "array",
"items": {
"oneOf": [
{
"type": "short_channel_id_dir"
},
{
"type": "pubkey"
}
]
}
},
"maxfee": {
"type": "msat"
}
}
}