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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

Forwarding Paths modes 馃洡 #222

Open
3 tasks
0xGabi opened this issue Aug 20, 2020 · 0 comments
Open
3 tasks

Forwarding Paths modes 馃洡 #222

0xGabi opened this issue Aug 20, 2020 · 0 comments
Labels
discussion
Projects
Roadmap to v1.0.0
Milestone
Forwarding Paths ...

Comments

@0xGabi
Copy link
Contributor

0xGabi commented Aug 20, 2020 •
edited

The current Connect API logic only calculates the shortest Forwarding Path. But in many cases, we may want more flexibility to allow:

  • Calculate all existing Forwarding Paths
  • Calculate a Forwarding Path giving a hardcoded ForwardingPathDeclaration
  • Calculate a Forwarding Path for an intent basket

When we build the full version, it would be nice to tell it things like:

  • I'd like to start with these steps (one or more steps in the path)
  • I'd like to use X app/account as the final forwarders (one or more last steps)
  • I'd like to have these X steps in the middle
  • A combination of either

In practice all this is doing is allowing the user to narrow our search space for forwarding pathing.
@0xGabi 0xGabi created this issue from a note in Roadmap to v1.0.0 (Up Next) Aug 20, 2020
@0xGabi 0xGabi added this to the Forwarding Paths modes milestone Aug 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
Roadmap to v1.0.0
  
Up Next
Milestone
Forwarding Paths modes
Development

No branches or pull requests
1 participant
@0xGabi