Proto commits in lightninglabs/faraday

These 39 commits are when the Protocol Buffers files have changed:

2026-08-26

multi: carry effective uptime as an unsigned second count Effective uptime is a duration, and the two second-valued fields already in the schema, ChannelInsight's monitored_seconds and uptime_seconds, are both unsigned. Aligning effective_uptime_s with them puts the non-negativity in the type, and it costs nothing at the boundary: the analyzer measures uptime as a time.Duration and the server derives whole seconds from it. The msat quantities beside it stay signed. They are the operands of arithmetic a consumer actually performs, deltas between windows and volume divided by forward count, where a signed result surfaces a mistake as a negative rather than as a number near 2^64. That reasoning does not reach a duration nobody subtracts, and it matches the seven signed msat fields the schema already carries. MinQualifyingUptime returns the same unsigned count, so the comparison it feeds needs no conversion. Its "admits nothing" sentinel becomes MaxUint64. Decoding an up-but-idle pair now clamps the window before adopting it as an uptime, since a response whose end precedes its start would otherwise reconstruct a near-infinite one instead of a negative one.

multi: report forwarding volume in millisatoshis The forwarding ability endpoint reported per-pair volume in satoshis while lnd hands us every forward amount in millisatoshis, so the analyzer floored each forward to a whole satoshi before summing it. A pair carrying only sub-satoshi forwards reported zero volume and had to be recognised by its forward count alone, and the CLI's fee rate needed a factor of 1000 to divide millisatoshi fees by satoshi volume. Summing at the granularity lnd reports means no forward is floored away and the fee rate falls out as a plain unitless fraction. The field is renamed forwarded_sat to forwarded_msat rather than kept, so a REST consumer that misses the change reads a missing field instead of a value that is silently 1000 times too small. int64 millisatoshis reaches 92.2 million BTC, over four times the supply, so the narrower unit costs nothing in range.

2026-08-25

frdrpc: report fees and forward counts per pair Report the fees alongside the volume so a single call describes the window completely. Fees are reported in millisatoshis because a single forward routinely earns less than one satoshi, and a satoshi granular sum would floor a low-fee pair's earnings to zero. Report the forward count as well. Both sums can be zero for a pair that really did forward: its volume floors to whole satoshis and a zero-fee policy earns nothing, so without a count neither zero can be told apart from a pair that carried nothing at all. The count is what makes the presence of traffic a fact the response states rather than one the consumer infers from a sum.

2026-06-09

frdrpc: add ForwardingAbility RPC schema Add the ForwardingAbility RPC that reports, for every (peerIn, peerOut) pair, the raw forwarding facts over a window: effective uptime in seconds and forwarded volume in satoshis. The response is a sparse, packed encoding (deduplicated peer keys plus packed pair indices) carrying only pairs with a non-zero signal; an absent pair means zero over the window. A single liquidity_floor_sat request parameter sets the directional liquidity a pair must hold to count as economically forwardable.

2026-05-08

frdrpc: add GetChannelEvents Adds the GetChannelEvents RPC to the proto and regenerates the gRPC, gateway, swagger, and JSON stubs. The request carries a chan_point, inclusive start_time and exclusive end_time bounds, a max_events cap, and a last_id keyset cursor; the response echoes last_id and a has_more flag so callers can drive pagination without server-side state.

2026-02-28

frdrpc: add Bitfinex fiat backend

2021-09-01

multi: surface coingecko on rpc

The documentation is generated from this commit.

2021-08-27

multi: add custom price options to RPC methods This commit adds the options required for the custom fiat price data to the RPC methods. These methods include the NodeAudit and ExchangeRate methods.

multi: update RPC to show the fiat currency Update the RPC methods (exchange rate and node report) so that they show the fiat currency that the bitcoin price is quoted in.

2021-05-14

multi: add fiat backend option to RPC endpoints This commit adds a fiat_backends option to the RPC relevant RPC endpoints. Namely, the NodeAudit and ExchangeRate endpoint.

2021-04-21

make+mod+frdrpc: use Docker for compiling protos To make the protobuf and grpc versions used in Faraday independent of those in lnd, we compile the protos inside a container. Therefore the local development environment doesn't have to match any other project in terms of those versions for successful compilation.

frdrpc: use rest-annotations.yaml for REST definitions To simplify the RPC generation and make it easier for people to compile the faraday.proto file, we extract the REST definitions into their own file.

frdrpc: rename rpc.proto to faraday.proto Because the file name "rpc.proto" is already taken by lnd, we get a weird warning everywhere we include both the lnd and faraday, as libraries for example: WARNING: proto: file "rpc.proto" is already registered We fix this problem by renaming faraday's proto file.

2020-10-27

mutli: add custom categories to node audit rpc

2020-09-09

multi: rename nodereport to nodeaudit Consensue on the team is that nodereport is more representative of a report about the node's operation than an accounting report. Renaming in anticipation of upcoming release.

2020-08-12

accounting: add channel close fee for channels we initiated

2020-07-22

multi: allow specifying of granularity level for report generation

frdrpc: surface bitcoin price and timestamp in report

multi: switchover fiat to use timestamped bitcoin prices and rename

frdrpc: rpcformat for existing formatting issues

2020-06-27

frdrpc: add close report endpoint

2020-06-26

multi: add option to disable fiat pricing for reports For testing, or users uninterested in fiat prices, we add an option to disable querying for fiat prices.

2020-06-23

multi: remove granularity from rpc endpoints The granularity with which we query our price backend is an implementation detail that we don't need to expose to users. Rather than making this configurable, we just calculate our best possible level of granularity server side, and leave this decision out of the user's hands.

2020-06-18

accounting: add sweep entry type

2020-06-05

accounting+frdrpc: add payments to off chain report Add payments to off chain report, failing if there are any duplicate payments in the period being queried. Legacy payments in lnd have duplicate payments which add significant overhead to dealing with payments. Rather than carry the tech debt, we do not support these payments.

2020-05-29

frdrpc: add forwards to node accounting endpoint

2020-05-25

frdrpc: add invoices to node report

2020-05-20

frdrpc: add node report endpoint, currently only populated with on chain

2020-05-13

frdrpc: update fiat endpoint to return strings for better precision

2020-04-30

frdrpc: add fiat estimate method

2020-04-07

frdrpc: add REST URLs

2020-03-30

multi: faraday rename

2020-03-05

multi: rename trmrpc to gvnrpc

2020-03-04

trmrpc+trmcli: add volume based recommendations

2020-02-25

trmrpc+trmcli: add revenue based recommendations

mutli: split uptime and threshold recommendations into separate calls This commit separates uptime based and threshold based recommendations into two separate calls. This decreases the matrix of possible values that users have to specify as we introduce more datasets that close decisions can be made based

2020-02-19

trmrpc: add channel insights endpoint

trmrpc: add revenue report endpoint

2020-01-31

trmrpc: add terminator service proto