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 support for new TAP channel RPCs #38

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add support for new TAP channel RPCs #38

wants to merge 2 commits into from

Conversation

jamaljsr
Copy link
Member

@jamaljsr jamaljsr commented Aug 16, 2024

This PR updates the generated types to include the new RPCs added to support TAP channels and asset payments in litd v0.14.0-alpha.

Depends on

@jamaljsr jamaljsr force-pushed the 0-19-staging branch 2 times, most recently from ce854ee to 88d4534 Compare September 11, 2024 04:23
@jamaljsr jamaljsr marked this pull request as ready for review January 14, 2025 05:47
@jamaljsr jamaljsr changed the title [WIP] Add support for new TAP channel RPCs Add support for new TAP channel RPCs Jan 14, 2025
Copy link
Collaborator

@ViktorTigerstrom ViktorTigerstrom left a comment

Choose a reason for hiding this comment

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

Generally looks good 🚀!
Though given that this is targeting the 0-19-staging branch, should we instead wait for the LNC release, and then make it instead target main, and also then include a version bump of lnc-core?

@@ -5,12 +5,12 @@
"main": "./dist/index.js",
"types": "./dist/index.d.ts",
"config": {
"lnd_release_tag": "v0.18.2-beta",
"lnd_release_tag": "v0.18.4-beta",
"loop_release_tag": "v0.28.5-beta",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we also bump this to v0.29.0-beta to match LNC?

@jamaljsr
Copy link
Member Author

Though given that this is targeting the 0-19-staging branch, should we instead wait for the LNC release, and then make it instead target main, and also then include a version bump of lnc-core?

Yes, I would wait for a tagged release of LNC, then bump the version numbers to match, before merging this PR.

Apologies, I probably should have waited before requesting review.

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.

2 participants