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

Add endpoint for decoding invoices #63

Merged
merged 4 commits into from
May 6, 2022
Merged

Add endpoint for decoding invoices #63

merged 4 commits into from
May 6, 2022

Conversation

w3irdrobot
Copy link
Contributor

Part of #21. Requested by @louneskmt. This should work. I kind of guessed what information would be needed from the endpoint. 🤷‍♂️

Copy link
Contributor

@louneskmt louneskmt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @w3irdrobot! Could you add: timestamp, min_final_cltv_expiry, route_hints, features and payee_pub_key as well? Then we should have all the necessary fields, like the other implems.

src/node.rs Outdated Show resolved Hide resolved
@johncantrell97
Copy link
Contributor

can you add grpc support for this as well? it shouldn't be much more since both grpc/http both use the same service implementation you already wrote. will just need to update the proto and then the grpc/node.rs implementation for it.

I'd like to make sure we don't let the grpc interface fall behind.

also can you rebase and fix the conflict in src/services/node.rs --- let me know if you need help there

@johncantrell97 johncantrell97 merged commit ee3d45d into L2-Technology:main May 6, 2022
@w3irdrobot w3irdrobot deleted the invoice-decode branch May 6, 2022 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants