[bug]: Unable to fundchannel - message payload is too large #1250
Comments
|
Thanks for this report! I know exactly what's going on here. The fix will be able to be applied directly to the nodes once we get out rc3. |
github-project-automation
bot
moved this from 👀 In review
to ✅ Done
in Taproot-Assets Project Board
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
We are trying to create a channel from speed4 to speed3, using fundchannel command, receiving the following error
Your environment
Mainnet
tapcli getinfo { "version": "0.5.0-alpha.rc2 commit=v0.5.0-rc2", "lnd_version": "0.18.4-beta.rc2", "network": "mainnet", "lnd_identity_pubkey": "038dbb70e3484da0bed806156f5270d39b480a659c82fb4b56ba3dcbe0edd74d55", "node_alias": "speed4", "block_height": 874391, "block_hash": "000000000000000000005d8175570bdf70133d57b2c7820a1445082a9c53eb39", } lncli getinfo 67503f3564b2:/src# lncli getinfo { "version": "0.18.4-beta.rc2 commit=lightning-terminal-v0.14.0-alpha.rc2", "commit_hash": "890764a28af254243c64856c4addf6b9dc674716", "identity_pubkey": "038dbb70e3484da0bed806156f5270d39b480a659c82fb4b56ba3dcbe0edd74d55", "alias": "speed4", "color": "#f2f2f2", "num_pending_channels": 0, "num_active_channels": 1, "num_inactive_channels": 0, "num_peers": 3, "block_height": 874391, "block_hash": "000000000000000000005d8175570bdf70133d57b2c7820a1445082a9c53eb39", "best_header_timestamp": "1734005631", "synced_to_chain": true, "synced_to_graph": true, "testnet": false, "chains": [ { "chain": "bitcoin", "network": "mainnet" } ], "uris": [ "038dbb70e3484da0bed806156f5270d39b480a659c82fb4b56ba3dcbe0edd74d55@44.207.210.37:8737" ], "features": { "0": { "name": "data-loss-protect", "is_required": true, "is_known": true }, "5": { "name": "upfront-shutdown-script", "is_required": false, "is_known": true }, "7": { "name": "gossip-queries", "is_required": false, "is_known": true }, "8": { "name": "tlv-onion", "is_required": true, "is_known": true }, "12": { "name": "static-remote-key", "is_required": true, "is_known": true }, "14": { "name": "payment-addr", "is_required": true, "is_known": true }, "17": { "name": "multi-path-payments", "is_required": false, "is_known": true }, "19": { "name": "wumbo-channels", "is_required": false, "is_known": true }, "23": { "name": "anchors-zero-fee-htlc-tx", "is_required": false, "is_known": true }, "25": { "name": "route-blinding", "is_required": false, "is_known": true }, "27": { "name": "shutdown-any-segwit", "is_required": false, "is_known": true }, "30": { "name": "amp", "is_required": true, "is_known": true }, "31": { "name": "amp", "is_required": false, "is_known": true }, "45": { "name": "explicit-commitment-type", "is_required": false, "is_known": true }, "47": { "name": "scid-alias", "is_required": false, "is_known": true }, "51": { "name": "zero-conf", "is_required": false, "is_known": true }, "55": { "name": "keysend", "is_required": false, "is_known": true }, "181": { "name": "simple-taproot-chans-x", "is_required": false, "is_known": true }, "2023": { "name": "script-enforced-lease", "is_required": false, "is_known": true }, "2025": { "name": "taproot-overlay-chans", "is_required": false, "is_known": true } }, "require_htlc_interceptor": false, "store_final_htlc_resolutions": false } uname -mrsv Linux 6.8.0-1017-aws #18~22.04.1-Ubuntu SMP Thu Oct 3 19:57:42 UTC 2024 x86_64 bitcoind --version || btcd --version Bitcoin Core version v23.0.0 litcli --v litcli version 0.14.0-alpha.rc2 commit=v0.14.0-alpha.rc2Steps to reproduce
Firing the following fundchannel command gives us
Expected behavior
A successful fund channel and publishing of onchain tx
Actual behavior
Failing with message payload error, attaching the output and command here
Output
Logs
The text was updated successfully, but these errors were encountered: