Get desktop application:
View/edit binary Protocol Buffers messages
* frcli: `outliers` Get close recommendations for currently open channels based on whether it is an outlier. Example request: http://localhost:8466/v1/faraday/outliers/REVENUE?rec_request.minimum_monitored=123
The parameters that are common to all close recommendations.
The number of inter-quartile ranges a value needs to be beneath the lower quartile/ above the upper quartile to be considered a lower/upper outlier. Lower values will be more aggressive in recommending channel closes, and upper values will be more conservative. Recommended values are 1.5 for aggressive recommendations and 3 for conservative recommendations.
* frcli: `threshold` Get close recommendations for currently open channels based whether they are below a set threshold. Example request: http://localhost:8466/v1/faraday/threshold/UPTIME?rec_request.minimum_monitored=123
The parameters that are common to all close recommendations.
The threshold that recommendations will be calculated based on. For uptime: ratio of uptime to observed lifetime beneath which channels will be recommended for closure. For revenue: revenue per block that capital has been committed to the channel beneath which channels will be recommended for closure. This value is provided per block so that channels that have been open for different periods of time can be compared. For incoming volume: The incoming volume per block that capital has been committed to the channel beneath which channels will be recommended for closure. This value is provided per block so that channels that have been open for different periods of time can be compared. For outgoing volume: The outgoing volume per block that capital has been committed to the channel beneath which channels will be recommended for closure. This value is provided per block so that channels that have been open for different periods of time can be compared. For total volume: The total volume per block that capital has been committed to the channel beneath which channels will be recommended for closure. This value is provided per block so that channels that have been open for different periods of time can be compared.
* frcli: `revenue` Get a pairwise revenue report for a channel. Example request: http://localhost:8466/v1/faraday/revenue
The funding transaction outpoints for the channels to generate a revenue report for. If this is empty, it will be generated for all open and closed channels. Channel funding points should be expressed with the format fundingTxID:outpoint.
Start time is beginning of the range over which the report will be generated, expressed as unix epoch offset in seconds.
End time is end of the range over which the report will be generated, expressed as unix epoch offset in seconds.
Reports is a set of pairwise revenue report generated for the channel(s) over the period specified.
* frcli: `insights` List currently open channel with routing and uptime information. Example request: http://localhost:8466/v1/faraday/insights
(message has no fields)
Insights for the set of currently open channels.
* frcli: Get fiat prices for btc. Example request: http://localhost:8466/v1/faraday/exchangerate
A set of timestamps for which we want the bitcoin price.
The level of granularity at which we want the bitcoin price to be quoted.
The api to be used for fiat related queries.
Custom price points to use if the CUSTOM FiatBackend option is set.
Rates contains a set of exchange rates for the set of timestamps
* Get a report of your node's activity over a period. Example request: http://localhost:8466/v1/faraday/nodeaudit
The unix time from which to produce the report, inclusive.
The unix time until which to produce the report, exclusive.
Set to generate a report without conversion to fiat. If set, fiat values will display as 0.
The level of granularity at which we wish to produce fiat prices.
An optional set of custom categories which can be used to identify bespoke categories in the report. Each category must have a unique name, and may not have common identifier regexes. Transactions that are matched to these categories report the category name in the CustomCategory field.
The api to be used for fiat related queries.
Custom price points to use if the CUSTOM FiatBackend option is set.
On chain reports for the period queried.
* Get a channel close report for a specific channel. Example request: http://localhost:8466/v1/faraday/closereport
The funding outpoint of the channel the report should be created for, formatted txid:outpoint.
The funding outpoint of the channel.
True if we opened the channel, false if the remote peer did.
The type of close that resolved this channel.
The transaction id of the close transaction that confirmed on chain.
The fee we paid on chain to open this channel in satoshis, note that this field will be zero if the remote party paid.
The fee we paid on chain for the close transaction in staoshis, note that this field will be zero if the remote party paid.
Used in:
, , ,The price of 1 BTC, expressed in USD.
The timestamp for this price price provided.
The currency that the price is denoted in.
Used in:
The outpoint of the channel's funding transaction.
The amount of time in seconds that we have monitored the channel peer's uptime for.
The amount of time in seconds that the channel peer has been online over the period it has been monitored for.
The volume, in millisatoshis, that has been forwarded with this channel as the incoming channel.
The volume, in millisatoshis, that has been forwarded with this channel as the outgoing channel.
The total fees earned by this channel for its participation in forwards, expressed in millisatoshis. Note that we attribute fees evenly across incoming and outgoing channels.
The number of confirmations the funding transaction has.
True if the channel is private.
Used in:
,The minimum amount of time in seconds that a channel should have been monitored by lnd to be eligible for close. This value is in place to protect against closing of newer channels.
The data point base close recommendations on. Available options are: Uptime: ratio of channel peer's uptime to the period they have been monitored to. Revenue: the revenue that the channel has produced per block that its funding transaction has been confirmed for.
Used in:
Used as response type in: FaradayServer.OutlierRecommendations, FaradayServer.ThresholdRecommendations
The total number of channels, before filtering out channels that are not eligible for close recommendations.
The number of channels that were considered for close recommendations.
A set of channel close recommendations. The absence of a channel in this set implies that it was not considered for close because it did not meet the criteria for close recommendations (it is private, or has not been monitored for long enough).
Used in:
The name for the custom category which will contain all transactions that are labelled with a string matching one of the regexes provided in label identifiers.
Set to true to apply this category to on chain transactions. Can be set in conjunction with off_chain to apply the category to all transactions.
Set to true to apply this category to off chain transactions. Can be set in conjunction with on_chain to apply the category to all transactions.
A set of regular expressions which identify transactions by their label as belonging in this custom category. If a label matches any single regex in the set, it is considered to be in the category. These expressions will be matched against various labels that are present in lnd: on chain transactions will be matched against their label field, off chain receipts will be matched against their memo. At present, there is no way to match forwards or off chain payments. These expressions must be unique across custom categories, otherwise faraday will not be able to identify which custom category a transaction belongs in.
Used in:
A channel opening transaction for a channel opened by our node.
A channel opening transaction for a channel opened by a remote node.
The on chain fee paid to open a channel.
A channel closing transaction.
Receipt of funds. On chain this reflects receives, off chain settlement of invoices.
Payment of funds. On chain this reflects sends, off chain settlement of our payments.
Payment of fees.
Receipt of a payment to ourselves.
A forward through our node.
Fees earned from forwarding.
Sending of a payment to ourselves.
The fees paid to send an off chain payment to ourselves.
A transaction that sweeps funds back into our wallet's control.
The amount of fees paid for a sweep transaction.
The fees paid to close a channel.
Used in:
timestamp is the timestamp of the original request made.
Price is the bitcoin price approximation for the timestamp queried. Note that this value has its own timestamp because we are not guaranteed to get price points for the exact timestamp that was queried.
FiatBackend is the API endpoint to be used for any fiat related queries.
Used in:
,Use the CoinCap API for fiat price information. This API is reached through the following URL: https://api.coincap.io/v2/assets/bitcoin/history
Use the CoinDesk API for fiat price information. This API is reached through the following URL: https://api.coindesk.com/v1/bpi/historical/close.json
Use custom price data provided in a CSV file for fiat price information.
Use the CoinGecko API for fiat price information. This API is reached through the following URL: https://api.coingecko.com/api/v3/coins/bitcoin/market_chart
Granularity describes the aggregation level at which the Bitcoin price should be queried. Note that setting lower levels of granularity may require more queries to the fiat backend.
Used in:
,Used in:
Amount outgoing msat is the amount in millisatoshis that arrived on the pair channel to be forwarded onwards by our channel.
Fees outgoing is the amount of fees in millisatoshis that we attribute to the channel for its role as the outgoing channel in forwards.
Amount incoming msat is the amount in millisatoshis that arrived on our channel to be forwarded onwards by the pair channel.
Fees incoming is the amount of fees in millisatoshis that we attribute to the channel for its role as the incoming channel in forwards.
Used in:
The channel point [funding txid: outpoint] of the channel being considered for close.
The value of the metric that close recommendations were based on.
A boolean indicating whether we recommend closing the channel.
Used in:
The unix timestamp of the event.
Whether the entry occurred on chain or off chain.
The amount of the entry, expressed in millisatoshis.
Whether the entry is a credit or a debit.
The asset affected by the entry.
The kind of activity that this entry represents.
This field will be populated for entry type custom, and represents the name of a custom category that the report was produced with.
The transaction id of the entry.
The fiat amount of the entry's amount in the currency specified in the btc_price field.
A unique identifier for the entry, if available.
An additional note for the entry, providing additional context.
The bitcoin price and timestamp used to calculate our fiat value.
Used in:
Target channel is the channel that the report is generated for; incoming fields in the report mean that this channel was the incoming channel, and the pair as the outgoing, outgoing fields mean that this channel was the outgoing channel and the peer was the incoming channel.
Pair reports maps the channel point of a peer that we generated revenue with to a report detailing the revenue.