You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the option to include the route that a HTLC has taken in our simulation output (probably with an option to turn on/off so that it's not too noisy).
This isn't straightforward because right now we report per-payment (which may have multiple HTLCs), and just note a HTLC count. We'd need to re-examine the way we report payments to have per-HTLC granularity.
This may also have some implementation implications (I'm not sure how much information each surfaces). Researching what is available to us is part of the scope of this issue.
The text was updated successfully, but these errors were encountered:
Add the option to include the route that a HTLC has taken in our simulation output (probably with an option to turn on/off so that it's not too noisy).
This isn't straightforward because right now we report per-payment (which may have multiple HTLCs), and just note a HTLC count. We'd need to re-examine the way we report payments to have per-HTLC granularity.
This may also have some implementation implications (I'm not sure how much information each surfaces). Researching what is available to us is part of the scope of this issue.
The text was updated successfully, but these errors were encountered: