Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature]: Do not keep MC data for blinded hops. #9321

Open
ziggie1984 opened this issue Nov 28, 2024 · 1 comment
Open

[feature]: Do not keep MC data for blinded hops. #9321

ziggie1984 opened this issue Nov 28, 2024 · 1 comment
Labels
blinded paths enhancement Improvements to existing features / behaviour mission control

Comments

@ziggie1984
Copy link
Collaborator

Due to the ephermal nature of the blinded route and its hop pubkeys it does not make sense to persist this data. Therefore we should only keep this data in memory during the payment process and remove it afterwards.

See also #9316

@ziggie1984
Copy link
Collaborator Author

A very nice design approach was mentioned by @ellemouton:

We should use the new namespace feature of the mission-control system to save the blinded path mission control data there separately. When looking for a path we would have to merge those different namespaces together (which is the difficult part of this change) so we have the whole data available for pathfinding. Then during startup because Route-Blinding data is ephemeral we wipe this blinded route namespace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blinded paths enhancement Improvements to existing features / behaviour mission control
Projects
None yet
Development

No branches or pull requests

1 participant