Skip to content

INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS and the asset invoice could not be received correctly for the asset. #1844

@levmi

Description

@levmi

Discussed in #1831

Originally posted by SevenLiquor October 1, 2025
The title actually reflects the two issues I encountered while using the asset channel.
version:litd 0.15.2-alpha
OS:ubuntu
The scene where the problem occurred:
There are four nodes labeled ABCD.
channel 1 : A------B traproot channel
channel 2 : B------C btc channels
channel 3 : C------D traproot channel
1 and 2 are the asset channels of the same asset.

The operation I carried out was: A applied for the invoice, and D made the payment.
A command:

 litcli ln addinvoice --asset_id xxxxxxxxxxxxx --asset_amount xxxxxxxxxxxx 

D command:

 litcli ln payinvoice --pay_req xxxxxxxxxxxxxxx --asset_id xxxxxxxxxxxxx

Question 1
Payment failed and this error occurred: INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS

This problem does not occur every time a payment is made. I haven't identified any pattern for its occurrence yet, and among the nodes I have, only one has experienced this issue at present.
Useful logs:
node D:

2025-10-01 20:36:38.004 [INF] UNIV: Fetching 1 roots
2025-10-01 20:36:51.958 [INF] LNWL: Verifying new musig2 sig for session=cded1657048ff17fc63256e0f7e7a01a5d4a6d919941ecbdd43101288ef98514, nonce=NoncePair(verification_nonce=034f3866cc9c2d1a7394debc043ce1c00a30ec0e610515df28eeefdc40060fa66a0362095bf94515bb230c586dc531b7e7549c1d9b59c7765eaec402546448cd58c7, signing_nonce=0396c82db6400d1829f7cb142b66593fc5686723d3c6447a7ba1c01e821243444303d1958f72bf163d80e6bc336e5a08a2f6d3e2d82f108d4a9af73d8b8ba3e56cdc)
2025-10-01 20:36:51.972 [INF] LNWL: Generating new musig2 sig for session=f1f1b0dfa6a4d218800c1465689e9aea5b41a75cf48155db974138f4cb4d9433, nonces=NoncePair(verification_nonce=035a3bcbb18287804a9e0cf48f16d344e8134a9f71f058bc2b24d0cc942f6c863c03e1739ca5ffb185228e7b8c602abd8137e522b86afd0fc7cb1695e98099fec64e, signing_nonce=0238215d99cfa05b1dbbb955cbcd544c5502d2ea8d0ae1320be950a64ec21b198f03b3640bf136e7a7cb6931dfc111bc0c1eb739d0d7b31cbe99e0d0714ec68a6da6)
2025-10-01 20:36:52.198 [INF] HSWC: ChannelLink(b165086ea9184270b16c1ccd38edfe220fb5da00a06347e1d6ab58424fe266f7:0): settling htlc edfd7de8bd4433fca49afa5c6d225b442f46e74df4efbe5d7b28c8fcf02ad820 as exit hop
2025-10-01 20:36:52.213 [INF] LNWL: Generating new musig2 sig for session=9eb73b8fac915e3559fe3b2ba3211328056f5bec0dad4b0830f4a3e33a8e8589, nonces=NoncePair(verification_nonce=022e905adde6566d156254c9a72d5c5b230fd6ac0498e958ef96368fb1be09556b020c9db3e1ad590d6c1f8613d0539cf45a6529b6212e125c12226c7648efb2875d, signing_nonce=027127471ffb13598bc0daa5476653c88712e3aebfa52877afa024ea0d7cb6514103597e2602e1aed98bccffba698cc38f836acbc9459462ad932f5d6e8491bf6607)
2025-10-01 20:36:52.439 [INF] LNWL: Verifying new musig2 sig for session=758b5edc1c77dbb3bb94fba1859e7ce04a5f8545ed35cd739efb70e8f2aa2b6b, nonce=NoncePair(verification_nonce=033f895391bb3f6602fec42e7f4fb599bc9e8d50acfc8fbb7a3f9a6e8d6ee85ebc02b88861cba19cfeb2719f5e21bd50e232d4ca0b46cf200ab40042de0db868e7c2, signing_nonce=0299b267a86150707c870d50e3d2655f9fae3930599d41f0483519835afbf26681030f5fb5db1d42f23905af78e6ca374cacc416dd889b183cbe8b6542a5283b85c7)
2025-10-01 20:36:58.006 [ERR] RPCS: [/universerpc.Universe/SyncUniverse]: unable to sync universe: unable to fetch roots for universe sync: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 132.232.109.84:8444: i/o timeout"
2025-10-01 20:37:11.067 [INF] GRPH: Processed channels=0 updates=181 nodes=59 in last 59.999751469s
2025-10-01 20:37:11.623 [INF] LITD: Handling gRPC request: /litrpc.Proxy/BakeSuperMacaroon
2025-10-01 20:37:11.627 [INF] LITD: Handling gRPC request: /lnrpc.Lightning/DecodePayReq
2025-10-01 20:37:11.630 [INF] LITD: Handling gRPC request: /lnrpc.Lightning/DecodePayReq
2025-10-01 20:37:13.268 [INF] LITD: Handling gRPC request: /tapchannelrpc.TaprootAssetChannels/SendPayment
2025-10-01 20:37:17.489 [INF] RPCS: Got quote for 3998644 asset units at 1168797774609.000 asset/BTC from peer 303363636335373065633661616666303864353433356233343133663462346166383137353732386131656432343465343731303132316338663561663665613037 with SCID 17733310497929727879
2025-10-01 20:37:17.557 [INF] LITD: Handling gRPC request: /lnrpc.Lightning/GetNodeInfo
2025-10-01 20:37:17.583 [INF] LITD: Handling gRPC request: /lnrpc.Lightning/GetNodeInfo
2025-10-01 20:37:17.629 [INF] LNWL: Generating new musig2 sig for session=816c2152c6b0d82ba9839900249679b89ed25fa99000907f511accd0e63be191, nonces=NoncePair(verification_nonce=024b7037ba48845478d8518385989aecd91974682ddd02a40e133fed1417ff6ca103c336f5f86b47649d6edfe9da60133f59afd2f9e6912a32013573e9676335f802, signing_nonce=037b6e2fdebac18de118dbfb796923db4ac10e1fc8994bbc5d0249cb20d4fd7e4c02d8d2730ea93b2295dc7bc0c40e534816e6f6ea7700b2ab9b86c9aa9a59b2f736)
2025-10-01 20:37:17.754 [INF] LITD: Handling gRPC request: /lnrpc.Lightning/GetNodeInfo
2025-10-01 20:37:19.238 [INF] LNWL: Verifying new musig2 sig for session=02b2feb78f74aa3e2227b7dbe90ea42217d79b5d70897af6863a92ba3788ea8f, nonce=NoncePair(verification_nonce=02c8263d3d82d6fa010afc6ac740ecd947229d0719628246ec9f82e7fcdfc84f36035611b830c5c6a780ed6f4491f9ac1cc6a97251b22c489c3ad8050bbe47951ec3, signing_nonce=02d0b6bf6310df0c2ece3abded03590965393d1319c3a51f211ab15cf735dcbe1d039fc25b216d57a79228d5b23b01c370cb59fc21fb688dd4719b351da2e922eda8)
2025-10-01 20:37:22.208 [INF] LNWL: Verifying new musig2 sig for session=17cbe0fea80fbaaa968f8bcdeb643123c0d3cc338ba7f7dd2b17fcdfc1b8f9bd, nonce=NoncePair(verification_nonce=02e8d6a78bb2a3859c92f72c484406508e1a02d88d1007b7d3592f51b0d225746003effeb6727559a65bc28a95503cbcc7f043e6cbb934469b9d30fb6878085d1c13, signing_nonce=031f12524c7a7a845ed9cd782ba5f725be895ab7be9466848345163de15c6e20c802a006e9c606afe5e0abd20f15c50c72bbdad0c8eabf4343cc2e5b29566558bd19)
2025-10-01 20:37:22.223 [INF] LNWL: Generating new musig2 sig for session=5b4f0128dac6fe9cebc51fc9b1d2655024d3a3e46a3bec3be978356d2414a9ff, nonces=NoncePair(verification_nonce=02153c611cabc8a60f133cab1fc7b43bd6984c1f9e009a3b86107ae7a336811c2602f11346c2dd707bc6807ed38a5900665e2c300e45acf7c94904a7cc35b12d0b52, signing_nonce=035a0cdbc4a8551cd5cba303f32d5846ba0a4fc56cc295a1c8bd0b3477b3f5bfad029798296d2b54a5c1ba176a178b8bd3aadf195c6e0761f4f1877b26a42ad759a2)
2025-10-01 20:37:22.446 [ERR] CRTR: Payment 11cc20641fd3c7bd3ea8a3563469a022c08794ecd1bde07ca5ca726a25961ac3 failed: final_outcome=incorrect_payment_details, raw_err=IncorrectOrUnknownPaymentDetails(amt=171116 mSAT, height=917233)@3
2025-10-01 20:37:22.457 [WRN] CRTR: Attempt 3013 for payment 11cc20641fd3c7bd3ea8a3563469a022c08794ecd1bde07ca5ca726a25961ac3 failed: IncorrectOrUnknownPaymentDetails(amt=171116 mSAT, height=917233)@3
2025-10-01 20:37:22.470 [WRN] CHDB: Payment(11cc20641fd3c7bd3ea8a3563469a022c08794ecd1bde07ca5ca726a25961ac3): cannot register HTLC attempt: payment has already failed, current status: Failed
2025-10-01 20:37:22.471 [ERR] RPCS: [/tapchannelrpc.TaprootAssetChannels/SendPayment]: payment failed: FAILURE_REASON_INCORRECT_PAYMENT_DETAILS
2025-10-01 20:37:22.471 [ERR] CRTR: Payment 11cc20641fd3c7bd3ea8a3563469a022c08794ecd1bde07ca5ca726a25961ac3 failed: incorrect_payment_details
2025-10-01 20:38:11.067 [INF] GRPH: Processed channels=0 updates=69 nodes=94 in last 59.999940862s
2025-10-01 20:38:13.006 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03ccc570ec6aaff08d5435b3413f4b4af8175728a1ed244e4710121c8f5af6ea07@43.173.253.2:9735
2025-10-01 20:38:13.006 [ERR] RPCS: [/lnrpc.Lightning/ConnectPeer]: already connected to peer: 03ccc570ec6aaff08d5435b3413f4b4af8175728a1ed244e4710121c8f5af6ea07@43.173.253.2:9735

Node A

2025-10-01 20:37:15.755 [INF] LITD: Handling gRPC request: /universerpc.Universe/QueryAssetRoots
2025-10-01 20:37:16.163 [WRN] GRDB: Node=0382a077559ca2c93b2bbc7833417c33d7dbe07e18f9f9723b9de16bb9b7f25fcf not found in graph cache
2025-10-01 20:37:16.164 [WRN] GRDB: Channel=1006119110123716609 not found in graph cache
2025-10-01 20:37:16.749 [INF] LITD: Handling gRPC request: /litrpc.Status/SubServerStatus
2025-10-01 20:37:20.683 [INF] LNWL: Verifying new musig2 sig for session=e089aa239654a1d80eaef3db7936eec8077e65e07e5af4008944c083bf0d9bca, nonce=NoncePair(verification_nonce=023f41e9fe672764a6f03664a472efde6bb82b69da43e4965bf609fd21d2a2f0f40391fde9799259b08b5046614798c94ab1985d6b51c868c3fe2af0cd9a722b1da0, signing_nonce=039dc4e2a1099704b953b43cbe0df13b6afb002359184c264d8fd1878804077e30023831a4b914f9a29d94392f9050a1b82cacaeb507ec1fe68e1897f27965584197)
2025-10-01 20:37:20.697 [INF] LNWL: Generating new musig2 sig for session=9ad94a357e5233b9b38bede959c1a423035a0b0bf83e1b74f42d94a3cf1370a4, nonces=NoncePair(verification_nonce=03906c3d641cdec138321bdfa6650f895d7bd0565563276af63b88391b1038ab6902facf66ace000016e9cf5939331efdbf2d544b329c0a9ca6fca244603d148e47d, signing_nonce=03a8f2e0cec3d00789b60d44e42de7cc0a1b68df8a5e0fa9f61769da22858326de027cf13ea83e15cf61453735904389834dac831b1f354e6e7480e2da7fdaa98874)
2025-10-01 20:37:20.747 [ERR] RPCS: [/routerrpc.Router/SubscribeHtlcEvents]: unknown fail resolution: external validation failed
rpc error: code = Unknown desc = unknown fail resolution: external validation failed
2025-10-01 20:37:20.758 [INF] LNWL: Generating new musig2 sig for session=493ff5e9f66b1c8df74954ffa93c5918df4f86dc4334b492b98578007e52044d, nonces=NoncePair(verification_nonce=034458c513e035702a0dbc3dd062aff38681267ced45552d426589887f602d2901037bc04ae65cadaa1be90c9b38e1e06eb96f249a7b724ac32d8cca0ee12a950d7e, signing_nonce=0218e3d5e812bc5be53f7417e2cdc38930082778fa21bda55b5982cdfcf65e6be502994b9dfc660692b80eb0ff6ff893cd018b83754015e66c6387f4038efbe84d47)
2025-10-01 20:37:20.802 [INF] LNWL: Verifying new musig2 sig for session=3e56ac0600d42e4ec89699816b0ca85d57cc070cc9943923cf9f37a2112e790b, nonce=NoncePair(verification_nonce=02b3ab2d16ceee16b29c56390786165756d15ac4e645979170cd5659d777ab9411027acbd66eeb9ae37d6375a7d63b3428f8e300bff6559cad8ddd091447d3ca583d, signing_nonce=0294b75988d3814b9f691cc03d7d9e64deaa715269fdee2bd7acda14de64c5f9d1027d1c557b5840b53efc44e14dd80cf7556ba848083125a017bae90b2690118724)

Question 2
Using the command to apply for the asset invoice, but what was received was BTC.

This problem was discovered when testing Question 1。

Occasionally, the payment is successful, but when I checked the asset quantity, I found that the local balance remained unchanged.

I couldn't find the log that I thought was useful. This is one of the invoices that shows this situation.

{
            "memo": "",
            "r_preimage": "3dae689ea108ccd43ad5c51000783d03f1bc2aaa07eb97c2613b9cfeaa882b6c",
            "r_hash": "386fc515df8ab97bd1be19075a32662107e5dda0cbbdaae885d36862bd2b68ac",
            "value": "171",
            "value_msat": "171116",
            "settled": true,
            "creation_date": "1759321555",
            "settle_date": "1759321820",
            "payment_request": "lnbc1711160p1p5d68wnpp58phu29wl32uhh5d7ryr45vnxyyr7thdqew7646y96d5x90ftdzkqdqqcqzzsxqzfvrzjqty4xssmclc8hes99yswg6zr6y0x60lunxrpwly379qdwmrw6w3afadtyuhqcx33lyqqqqlgqqqqqqgq2qsp5ydw7l82zyg3l2306kdxaxkcy0axyghxhv2u8vjh3vxkjrgsljhhs9qxpqysgq8sv6x5ssgeecugkyksxys0mqt4l9433jnljm95cccmkr0d5lxn4zudue56z40sr5ncs4u8gaeda6660dppmjz8whkxn56szkt6f4htcptr4zej",
            "description_hash": "",
            "expiry": "300",
            "fallback_addr": "",
            "cltv_expiry": "80",
            "route_hints": [
                {
                    "hop_hints": [
                        {
                            "node_id": "02c953421bc7f07be6052920e46843d11e6d3ffc9986177c91f140d76c6ed3a3d4",
                            "chan_id": "17702285839034888697",
                            "fee_base_msat": 1000,
                            "fee_proportional_millionths": 1,
                            "cltv_expiry_delta": 80
                        }
                    ]
                }
            ],
            "private": true,
            "add_index": "15685",
            "settle_index": "502",
            "amt_paid": "171116",
            "amt_paid_sat": "171",
            "amt_paid_msat": "171116",
            "state": "SETTLED",
            "htlcs": [
                {
                    "chan_id": "1007277995385356288",
                    "htlc_index": "4",
                    "amt_msat": "171116",
                    "accept_height": 917233,
                    "accept_time": "1759321820",
                    "resolve_time": "1759321820",
                    "expiry_height": 917316,
                    "state": "SETTLED",
                    "custom_records": {
                        "106823": "00"
                    },
                    "mpp_total_amt_msat": "171116",
                    "amp": null,
                    "custom_channel_data": {
                        "balances": [],
                        "rfq_id": ""
                    }
                }
            ],
            "features": {
                "8": {
                    "name": "tlv-onion",
                    "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
                },
                "25": {
                    "name": "route-blinding",
                    "is_required": false,
                    "is_known": true
                }
            },
            "is_keysend": false,
            "payment_addr": "235def9d422223f545fab34dd35b047f4c445cd762b8764af161ad21a21f95ef",
            "is_amp": false,
            "amp_invoice_state": {},
            "is_blinded": false,
            "blinded_path_config": null
        }

Other tag:
These two issues occurred in the main network environment. Due to the large number of connected channels, the performance of the nodes seemed to be affected, making my testing quite difficult. However, when I attempted to reproduce the results in Polar, none of these situations occurred.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions