[#2189] Score Fee Params as a passed in parameter by henghonglee · Pull Request #2237 · lightningdevkit/rust-lightning

henghonglee · 2023-04-26T21:35:02Z

[#2189] Score Fee Params as a passed in parameter
Description:
Aims to fix https://github.com/lightningdevkit/rust-lightning/issues/2189
1. Introduce ScoreParams to Score Trait, allowing channel penalty calculations to have custom parameters
2. Split up ProbablisticScoreParamters into FeeParameters and DecayParameters
3. Couple tightly decay_params but decouple fee params so that modifying and customizing fee parameters can be more flexible.
4. Propagate changes to affect get_route and find_route in the router
5. Fix tests, put placeholder values on the various test scorers

TheBlueMatt

Thanks for working on this!

TheBlueMatt · 2023-04-28T21:22:55Z

Needs rebase, though it looks like you just have some commits that made their way upstream on this branch?

henghonglee

Hi @TheBlueMatt, Ive tried to list down the issues im facing here. tried a few different variations of this solution but ive rolled back to this one since its the simplest and imo closest to what i want to achieve

henghonglee

@TheBlueMatt could you also take a quick look at the other comments that i made? in router.rs

henghonglee

Hi @TheBlueMatt, it's finally ready for review :)

TheBlueMatt · 2023-05-09T01:31:48Z

You can tell github thinks your line is too long because it cut off the last word and replace it with ... :). I think its cutoff is ~~around 75, but I'm not 100% sure. 70 is always safe.~~ It was 70.

arik-so · 2023-05-09T17:15:45Z

+	pub manual_node_penalties: HashMap<NodeId, u64>,
+
+
+	/// This penalty is applied when `htlc_maximum_msat` is equal to or larger than half of the


I think writing out htlc_maximum_msat ≥ 0.5 * channel_capacity might make this a bit easier to read

I just moved this. but happy to make this change if thats necessary

Do it in a separate commit to preserve the move-only-ness, but nothing wrong with cleaning things up when they're getting touched anyway.

sure i can tease that out it into a seperate commit.

arik-so · 2023-05-09T17:20:06Z

+/// these decay parameters affect the score of the channel penalty but are usually not changed on a per-route
+/// penalty cost call.


Nit: These
Also, "per-route" could probably go on the next line.

okay will do

TheBlueMatt · 2023-05-10T16:59:08Z

Its not critical, but if you do have to push again for some reason, your commit message still has lines (in the body, post-title) that are longer than 70 chars long. This LGTM, however, I'll let @arik-so take another look.

henghonglee · 2023-05-10T18:45:59Z

@arik-so

arik-so · 2023-05-10T18:54:07Z

Looks good, but there are failing tests, so I imagine you're probably gonna need to push again.

This PR aims to create a "stateless" scorer. Instead of passing in fee params at construction-time, we want to parametrize the scorer with an associated "parameter" type, which is then passed to the router function itself, and allows passing different parameters per route-finding call.

henghonglee · 2023-05-11T00:51:50Z

@arik-so checks seems to be passing now

arik-so

Thanks!

TheBlueMatt · 2023-05-11T05:16:11Z

+
+#[cfg(test)]
+impl ProbabilisticScoringDecayParameters {
+	fn zero_penalty() -> Self {


Heh, we don't really need a duplicate of default that does the same thing :)

henghonglee · 2023-04-26T21:35:02Z

[#2189] Score Fee Params as a passed in parameter
Description:
Aims to fix https://github.com/lightningdevkit/rust-lightning/issues/2189
1. Introduce ScoreParams to Score Trait, allowing channel penalty calculations to have custom parameters
2. Split up ProbablisticScoreParamters into FeeParameters and DecayParameters
3. Couple tightly decay_params but decouple fee params so that modifying and customizing fee parameters can be more flexible.
4. Propagate changes to affect get_route and find_route in the router
5. Fix tests, put placeholder values on the various test scorers

TheBlueMatt

Thanks for working on this!

TheBlueMatt · 2023-04-28T21:22:55Z

Needs rebase, though it looks like you just have some commits that made their way upstream on this branch?

henghonglee

Hi @TheBlueMatt, Ive tried to list down the issues im facing here. tried a few different variations of this solution but ive rolled back to this one since its the simplest and imo closest to what i want to achieve

henghonglee

@TheBlueMatt could you also take a quick look at the other comments that i made? in router.rs

henghonglee

Hi @TheBlueMatt, it's finally ready for review :)

TheBlueMatt · 2023-05-09T01:31:48Z

You can tell github thinks your line is too long because it cut off the last word and replace it with ... :). I think its cutoff is ~~around 75, but I'm not 100% sure. 70 is always safe.~~ It was 70.

arik-so · 2023-05-09T17:15:45Z

+	pub manual_node_penalties: HashMap<NodeId, u64>,
+
+
+	/// This penalty is applied when `htlc_maximum_msat` is equal to or larger than half of the


I think writing out htlc_maximum_msat ≥ 0.5 * channel_capacity might make this a bit easier to read

I just moved this. but happy to make this change if thats necessary

Do it in a separate commit to preserve the move-only-ness, but nothing wrong with cleaning things up when they're getting touched anyway.

sure i can tease that out it into a seperate commit.

arik-so · 2023-05-09T17:20:06Z

+/// these decay parameters affect the score of the channel penalty but are usually not changed on a per-route
+/// penalty cost call.


Nit: These
Also, "per-route" could probably go on the next line.

okay will do

TheBlueMatt · 2023-05-10T16:59:08Z

Its not critical, but if you do have to push again for some reason, your commit message still has lines (in the body, post-title) that are longer than 70 chars long. This LGTM, however, I'll let @arik-so take another look.

henghonglee · 2023-05-10T18:45:59Z

@arik-so

arik-so · 2023-05-10T18:54:07Z

Looks good, but there are failing tests, so I imagine you're probably gonna need to push again.

This PR aims to create a "stateless" scorer. Instead of passing in fee params at construction-time, we want to parametrize the scorer with an associated "parameter" type, which is then passed to the router function itself, and allows passing different parameters per route-finding call.

henghonglee · 2023-05-11T00:51:50Z

@arik-so checks seems to be passing now

arik-so

Thanks!

TheBlueMatt · 2023-05-11T05:16:11Z

+
+#[cfg(test)]
+impl ProbabilisticScoringDecayParameters {
+	fn zero_penalty() -> Self {


Heh, we don't really need a duplicate of default that does the same thing :)

henghonglee · 2023-04-26T21:35:02Z

[#2189] Score Fee Params as a passed in parameter
Description:
Aims to fix https://github.com/lightningdevkit/rust-lightning/issues/2189
1. Introduce ScoreParams to Score Trait, allowing channel penalty calculations to have custom parameters
2. Split up ProbablisticScoreParamters into FeeParameters and DecayParameters
3. Couple tightly decay_params but decouple fee params so that modifying and customizing fee parameters can be more flexible.
4. Propagate changes to affect get_route and find_route in the router
5. Fix tests, put placeholder values on the various test scorers

TheBlueMatt

Thanks for working on this!

TheBlueMatt · 2023-04-28T21:22:55Z

Needs rebase, though it looks like you just have some commits that made their way upstream on this branch?

henghonglee

Hi @TheBlueMatt, Ive tried to list down the issues im facing here. tried a few different variations of this solution but ive rolled back to this one since its the simplest and imo closest to what i want to achieve

henghonglee

@TheBlueMatt could you also take a quick look at the other comments that i made? in router.rs

henghonglee

Hi @TheBlueMatt, it's finally ready for review :)

TheBlueMatt · 2023-05-09T01:31:48Z

You can tell github thinks your line is too long because it cut off the last word and replace it with ... :). I think its cutoff is ~~around 75, but I'm not 100% sure. 70 is always safe.~~ It was 70.

arik-so · 2023-05-09T17:15:45Z

+	pub manual_node_penalties: HashMap<NodeId, u64>,
+
+
+	/// This penalty is applied when `htlc_maximum_msat` is equal to or larger than half of the


I think writing out htlc_maximum_msat ≥ 0.5 * channel_capacity might make this a bit easier to read

I just moved this. but happy to make this change if thats necessary

Do it in a separate commit to preserve the move-only-ness, but nothing wrong with cleaning things up when they're getting touched anyway.

sure i can tease that out it into a seperate commit.

arik-so · 2023-05-09T17:20:06Z

+/// these decay parameters affect the score of the channel penalty but are usually not changed on a per-route
+/// penalty cost call.


Nit: These
Also, "per-route" could probably go on the next line.

okay will do

TheBlueMatt · 2023-05-10T16:59:08Z

Its not critical, but if you do have to push again for some reason, your commit message still has lines (in the body, post-title) that are longer than 70 chars long. This LGTM, however, I'll let @arik-so take another look.

henghonglee · 2023-05-10T18:45:59Z

@arik-so

arik-so · 2023-05-10T18:54:07Z

Looks good, but there are failing tests, so I imagine you're probably gonna need to push again.

This PR aims to create a "stateless" scorer. Instead of passing in fee params at construction-time, we want to parametrize the scorer with an associated "parameter" type, which is then passed to the router function itself, and allows passing different parameters per route-finding call.

henghonglee · 2023-05-11T00:51:50Z

@arik-so checks seems to be passing now

arik-so

Thanks!

TheBlueMatt · 2023-05-11T05:16:11Z

+
+#[cfg(test)]
+impl ProbabilisticScoringDecayParameters {
+	fn zero_penalty() -> Self {


Heh, we don't really need a duplicate of default that does the same thing :)

henghonglee · 2023-04-26T21:35:02Z

[#2189] Score Fee Params as a passed in parameter
Description:
Aims to fix https://github.com/lightningdevkit/rust-lightning/issues/2189
1. Introduce ScoreParams to Score Trait, allowing channel penalty calculations to have custom parameters
2. Split up ProbablisticScoreParamters into FeeParameters and DecayParameters
3. Couple tightly decay_params but decouple fee params so that modifying and customizing fee parameters can be more flexible.
4. Propagate changes to affect get_route and find_route in the router
5. Fix tests, put placeholder values on the various test scorers

TheBlueMatt

Thanks for working on this!

TheBlueMatt · 2023-04-28T21:22:55Z

Needs rebase, though it looks like you just have some commits that made their way upstream on this branch?

henghonglee

Hi @TheBlueMatt, Ive tried to list down the issues im facing here. tried a few different variations of this solution but ive rolled back to this one since its the simplest and imo closest to what i want to achieve

henghonglee

@TheBlueMatt could you also take a quick look at the other comments that i made? in router.rs

henghonglee

Hi @TheBlueMatt, it's finally ready for review :)

TheBlueMatt · 2023-05-09T01:31:48Z

You can tell github thinks your line is too long because it cut off the last word and replace it with ... :). I think its cutoff is ~~around 75, but I'm not 100% sure. 70 is always safe.~~ It was 70.

arik-so · 2023-05-09T17:15:45Z

+	pub manual_node_penalties: HashMap<NodeId, u64>,
+
+
+	/// This penalty is applied when `htlc_maximum_msat` is equal to or larger than half of the


I think writing out htlc_maximum_msat ≥ 0.5 * channel_capacity might make this a bit easier to read

I just moved this. but happy to make this change if thats necessary

Do it in a separate commit to preserve the move-only-ness, but nothing wrong with cleaning things up when they're getting touched anyway.

sure i can tease that out it into a seperate commit.

arik-so · 2023-05-09T17:20:06Z

+/// these decay parameters affect the score of the channel penalty but are usually not changed on a per-route
+/// penalty cost call.


Nit: These
Also, "per-route" could probably go on the next line.

okay will do

TheBlueMatt · 2023-05-10T16:59:08Z

Its not critical, but if you do have to push again for some reason, your commit message still has lines (in the body, post-title) that are longer than 70 chars long. This LGTM, however, I'll let @arik-so take another look.

henghonglee · 2023-05-10T18:45:59Z

@arik-so

arik-so · 2023-05-10T18:54:07Z

Looks good, but there are failing tests, so I imagine you're probably gonna need to push again.

This PR aims to create a "stateless" scorer. Instead of passing in fee params at construction-time, we want to parametrize the scorer with an associated "parameter" type, which is then passed to the router function itself, and allows passing different parameters per route-finding call.

henghonglee · 2023-05-11T00:51:50Z

@arik-so checks seems to be passing now

arik-so

Thanks!

TheBlueMatt · 2023-05-11T05:16:11Z

+
+#[cfg(test)]
+impl ProbabilisticScoringDecayParameters {
+	fn zero_penalty() -> Self {


Heh, we don't really need a duplicate of default that does the same thing :)

henghonglee · 2023-04-26T21:35:02Z

[#2189] Score Fee Params as a passed in parameter
Description:
Aims to fix https://github.com/lightningdevkit/rust-lightning/issues/2189
1. Introduce ScoreParams to Score Trait, allowing channel penalty calculations to have custom parameters
2. Split up ProbablisticScoreParamters into FeeParameters and DecayParameters
3. Couple tightly decay_params but decouple fee params so that modifying and customizing fee parameters can be more flexible.
4. Propagate changes to affect get_route and find_route in the router
5. Fix tests, put placeholder values on the various test scorers

TheBlueMatt

Thanks for working on this!

TheBlueMatt · 2023-04-28T21:22:55Z

Needs rebase, though it looks like you just have some commits that made their way upstream on this branch?

henghonglee

Hi @TheBlueMatt, Ive tried to list down the issues im facing here. tried a few different variations of this solution but ive rolled back to this one since its the simplest and imo closest to what i want to achieve

henghonglee

@TheBlueMatt could you also take a quick look at the other comments that i made? in router.rs

henghonglee

Hi @TheBlueMatt, it's finally ready for review :)

TheBlueMatt · 2023-05-09T01:31:48Z

You can tell github thinks your line is too long because it cut off the last word and replace it with ... :). I think its cutoff is ~~around 75, but I'm not 100% sure. 70 is always safe.~~ It was 70.

arik-so · 2023-05-09T17:15:45Z

+	pub manual_node_penalties: HashMap<NodeId, u64>,
+
+
+	/// This penalty is applied when `htlc_maximum_msat` is equal to or larger than half of the


I think writing out htlc_maximum_msat ≥ 0.5 * channel_capacity might make this a bit easier to read

I just moved this. but happy to make this change if thats necessary

Do it in a separate commit to preserve the move-only-ness, but nothing wrong with cleaning things up when they're getting touched anyway.

sure i can tease that out it into a seperate commit.

arik-so · 2023-05-09T17:20:06Z

+/// these decay parameters affect the score of the channel penalty but are usually not changed on a per-route
+/// penalty cost call.


Nit: These
Also, "per-route" could probably go on the next line.

okay will do

TheBlueMatt · 2023-05-10T16:59:08Z

Its not critical, but if you do have to push again for some reason, your commit message still has lines (in the body, post-title) that are longer than 70 chars long. This LGTM, however, I'll let @arik-so take another look.

henghonglee · 2023-05-10T18:45:59Z

@arik-so

arik-so · 2023-05-10T18:54:07Z

Looks good, but there are failing tests, so I imagine you're probably gonna need to push again.

This PR aims to create a "stateless" scorer. Instead of passing in fee params at construction-time, we want to parametrize the scorer with an associated "parameter" type, which is then passed to the router function itself, and allows passing different parameters per route-finding call.

henghonglee · 2023-05-11T00:51:50Z

@arik-so checks seems to be passing now

arik-so

Thanks!

TheBlueMatt · 2023-05-11T05:16:11Z

+
+#[cfg(test)]
+impl ProbabilisticScoringDecayParameters {
+	fn zero_penalty() -> Self {


Heh, we don't really need a duplicate of default that does the same thing :)

henghonglee · 2023-04-26T21:35:02Z

[#2189] Score Fee Params as a passed in parameter
Description:
Aims to fix https://github.com/lightningdevkit/rust-lightning/issues/2189
1. Introduce ScoreParams to Score Trait, allowing channel penalty calculations to have custom parameters
2. Split up ProbablisticScoreParamters into FeeParameters and DecayParameters
3. Couple tightly decay_params but decouple fee params so that modifying and customizing fee parameters can be more flexible.
4. Propagate changes to affect get_route and find_route in the router
5. Fix tests, put placeholder values on the various test scorers

TheBlueMatt

Thanks for working on this!

TheBlueMatt · 2023-04-28T21:22:55Z

Needs rebase, though it looks like you just have some commits that made their way upstream on this branch?

henghonglee

Hi @TheBlueMatt, Ive tried to list down the issues im facing here. tried a few different variations of this solution but ive rolled back to this one since its the simplest and imo closest to what i want to achieve

henghonglee

@TheBlueMatt could you also take a quick look at the other comments that i made? in router.rs

henghonglee

Hi @TheBlueMatt, it's finally ready for review :)

TheBlueMatt · 2023-05-09T01:31:48Z

You can tell github thinks your line is too long because it cut off the last word and replace it with ... :). I think its cutoff is ~~around 75, but I'm not 100% sure. 70 is always safe.~~ It was 70.

arik-so · 2023-05-09T17:15:45Z

+	pub manual_node_penalties: HashMap<NodeId, u64>,
+
+
+	/// This penalty is applied when `htlc_maximum_msat` is equal to or larger than half of the


I think writing out htlc_maximum_msat ≥ 0.5 * channel_capacity might make this a bit easier to read

I just moved this. but happy to make this change if thats necessary

Do it in a separate commit to preserve the move-only-ness, but nothing wrong with cleaning things up when they're getting touched anyway.

sure i can tease that out it into a seperate commit.

arik-so · 2023-05-09T17:20:06Z

+/// these decay parameters affect the score of the channel penalty but are usually not changed on a per-route
+/// penalty cost call.


Nit: These
Also, "per-route" could probably go on the next line.

okay will do

TheBlueMatt · 2023-05-10T16:59:08Z

Its not critical, but if you do have to push again for some reason, your commit message still has lines (in the body, post-title) that are longer than 70 chars long. This LGTM, however, I'll let @arik-so take another look.

henghonglee · 2023-05-10T18:45:59Z

@arik-so

arik-so · 2023-05-10T18:54:07Z

Looks good, but there are failing tests, so I imagine you're probably gonna need to push again.

This PR aims to create a "stateless" scorer. Instead of passing in fee params at construction-time, we want to parametrize the scorer with an associated "parameter" type, which is then passed to the router function itself, and allows passing different parameters per route-finding call.

henghonglee · 2023-05-11T00:51:50Z

@arik-so checks seems to be passing now

arik-so

Thanks!

TheBlueMatt · 2023-05-11T05:16:11Z

+
+#[cfg(test)]
+impl ProbabilisticScoringDecayParameters {
+	fn zero_penalty() -> Self {


Heh, we don't really need a duplicate of default that does the same thing :)

henghonglee · 2023-04-26T21:35:02Z

[#2189] Score Fee Params as a passed in parameter
Description:
Aims to fix https://github.com/lightningdevkit/rust-lightning/issues/2189
1. Introduce ScoreParams to Score Trait, allowing channel penalty calculations to have custom parameters
2. Split up ProbablisticScoreParamters into FeeParameters and DecayParameters
3. Couple tightly decay_params but decouple fee params so that modifying and customizing fee parameters can be more flexible.
4. Propagate changes to affect get_route and find_route in the router
5. Fix tests, put placeholder values on the various test scorers

TheBlueMatt

Thanks for working on this!

TheBlueMatt · 2023-04-28T21:22:55Z

Needs rebase, though it looks like you just have some commits that made their way upstream on this branch?

henghonglee

Hi @TheBlueMatt, Ive tried to list down the issues im facing here. tried a few different variations of this solution but ive rolled back to this one since its the simplest and imo closest to what i want to achieve

henghonglee

@TheBlueMatt could you also take a quick look at the other comments that i made? in router.rs

henghonglee

Hi @TheBlueMatt, it's finally ready for review :)

TheBlueMatt · 2023-05-09T01:31:48Z

You can tell github thinks your line is too long because it cut off the last word and replace it with ... :). I think its cutoff is ~~around 75, but I'm not 100% sure. 70 is always safe.~~ It was 70.

arik-so · 2023-05-09T17:15:45Z

+	pub manual_node_penalties: HashMap<NodeId, u64>,
+
+
+	/// This penalty is applied when `htlc_maximum_msat` is equal to or larger than half of the


I think writing out htlc_maximum_msat ≥ 0.5 * channel_capacity might make this a bit easier to read

I just moved this. but happy to make this change if thats necessary

Do it in a separate commit to preserve the move-only-ness, but nothing wrong with cleaning things up when they're getting touched anyway.

sure i can tease that out it into a seperate commit.

arik-so · 2023-05-09T17:20:06Z

+/// these decay parameters affect the score of the channel penalty but are usually not changed on a per-route
+/// penalty cost call.


Nit: These
Also, "per-route" could probably go on the next line.

okay will do

TheBlueMatt · 2023-05-10T16:59:08Z

Its not critical, but if you do have to push again for some reason, your commit message still has lines (in the body, post-title) that are longer than 70 chars long. This LGTM, however, I'll let @arik-so take another look.

henghonglee · 2023-05-10T18:45:59Z

@arik-so

arik-so · 2023-05-10T18:54:07Z

Looks good, but there are failing tests, so I imagine you're probably gonna need to push again.

This PR aims to create a "stateless" scorer. Instead of passing in fee params at construction-time, we want to parametrize the scorer with an associated "parameter" type, which is then passed to the router function itself, and allows passing different parameters per route-finding call.

henghonglee · 2023-05-11T00:51:50Z

@arik-so checks seems to be passing now

arik-so

Thanks!

TheBlueMatt · 2023-05-11T05:16:11Z

+
+#[cfg(test)]
+impl ProbabilisticScoringDecayParameters {
+	fn zero_penalty() -> Self {


Heh, we don't really need a duplicate of default that does the same thing :)

henghonglee changed the title ~~Issue 2189: Changes to score params~~https://github.com/lightningdevkit/rust-lightning/issues/2189 Issue 2189: Changes to score paramsApr 27, 2023

henghonglee changed the title ~~https://github.com/lightningdevkit/rust-lightning/issues/2189 Issue 2189: Changes to score params~~[Issue 2189] Changes to score paramsApr 27, 2023

henghonglee force-pushed the issue-2189-score-params branch from 9ec4e0f to d3273d3Compare April 27, 2023 07:34

TheBlueMatt reviewed Apr 28, 2023
View reviewed changes

Comment threadlightning/src/routing/router.rs Outdated

henghonglee force-pushed the issue-2189-score-params branch 9 times, most recently from 65a65ea to b00c185Compare April 28, 2023 21:21

henghonglee force-pushed the issue-2189-score-params branch 2 times, most recently from 7605325 to 25924b3Compare May 3, 2023 15:21

henghonglee commented May 3, 2023
View reviewed changes

Comment threadlightning/src/routing/router.rs
Comment threadlightning/src/routing/router.rs Outdated
Comment threadlightning/src/routing/router.rs Outdated

henghonglee force-pushed the issue-2189-score-params branch 3 times, most recently from db1db6e to 9362cbdCompare May 3, 2023 16:03

TheBlueMatt reviewed May 3, 2023
View reviewed changes

Comment threadlightning-background-processor/src/lib.rs Outdated

henghonglee commented May 3, 2023
View reviewed changes

Comment threadlightning-background-processor/src/lib.rs Outdated

henghonglee force-pushed the issue-2189-score-params branch 3 times, most recently from 530cb5d to 422d73dCompare May 5, 2023 01:15

henghonglee commented May 5, 2023
View reviewed changes

Comment threadlightning-background-processor/src/lib.rs Outdated
Comment threadlightning/src/routing/scoring.rs Outdated
Comment threadlightning/src/routing/scoring.rs Outdated
Comment threadlightning/src/routing/scoring.rs Outdated

henghonglee force-pushed the issue-2189-score-params branch from 422d73d to 1c8c153Compare May 5, 2023 01:23

henghonglee requested a review from TheBlueMatt May 5, 2023 01:23

henghonglee marked this pull request as ready for review May 5, 2023 04:15

henghonglee changed the title ~~[Issue 2189] Changes to score params~~[Issue 2189] Score Fee Params as a passed in parameterMay 5, 2023

henghonglee force-pushed the issue-2189-score-params branch 2 times, most recently from c3e3764 to 490f401Compare May 9, 2023 00:53

henghonglee force-pushed the issue-2189-score-params branch 3 times, most recently from 6d882ab to 567a225Compare May 9, 2023 04:50

arik-so self-requested a review May 9, 2023 16:51

arik-so reviewed May 9, 2023
View reviewed changes

henghonglee force-pushed the issue-2189-score-params branch from 567a225 to d1e9af7Compare May 9, 2023 23:34

henghonglee requested a review from arik-so May 9, 2023 23:35

henghonglee force-pushed the issue-2189-score-params branch 5 times, most recently from 8aacbe7 to a2d0363Compare May 10, 2023 05:11

henghonglee force-pushed the issue-2189-score-params branch 3 times, most recently from 04dc495 to 0614a6aCompare May 10, 2023 18:21

henghonglee force-pushed the issue-2189-score-params branch from 0614a6a to ecd7992Compare May 10, 2023 19:53

Move functions around to colocate impl of FeeParams and DecayParams
86af670

henghonglee force-pushed the issue-2189-score-params branch from ecd7992 to 86af670Compare May 10, 2023 22:32

arik-so approved these changes May 11, 2023
View reviewed changes

TheBlueMatt approved these changes May 11, 2023
View reviewed changes

TheBlueMatt merged commit e61b128 into lightningdevkit:mainMay 11, 2023

wpaulino mentioned this pull request Aug 15, 2023
Pass scoring params through the router #2189
Closed