It looks like reserved_to_block field is missing from gRPC mapping:
|
message ListfundsOutputs { |
|
// ListFunds.outputs[].status |
|
enum ListfundsOutputsStatus { |
|
UNCONFIRMED = 0; |
|
CONFIRMED = 1; |
|
SPENT = 2; |
|
} |
|
bytes txid = 1; |
|
uint32 output = 2; |
|
Amount amount_msat = 3; |
|
bytes scriptpubkey = 4; |
|
optional string address = 5; |
|
optional bytes redeemscript = 6; |
|
ListfundsOutputsStatus status = 7; |
|
bool reserved = 9; |
|
optional uint32 blockheight = 8; |
|
} |
Is it intentional? It looks like CLI can return this field under certain conditions:
|
if (reserved) |
|
json_add_num(response, "reserved_to_block", |
|
utxo->reserved_til); |
It looks like
reserved_to_blockfield is missing from gRPC mapping:lightning/cln-grpc/proto/node.proto
Lines 261 to 277 in 5444a84
Is it intentional? It looks like CLI can return this field under certain conditions:
lightning/wallet/walletrpc.c
Lines 284 to 286 in 9a880a0