onchaind crash: “Could not find resolution for output 2” on anchors + lost_state channel

[tikistack-sudo]

Summary

Core Lightning v25.12.1 onchaind crashes for an anchors + static_remotekey channel with:

STATUS_FAIL_INTERNAL_ERROR: Could not find resolution for output 2

even though that output belongs to the remote and is already spent.

Environment

• Core Lightning version: v25.12.1
• Build: [package or self-built from source, include git commit if you have it]
• Network: bitcoin mainnet
• Backend: bitcoind (no txindex, pruned? yes/no)
• Host: Raspberry Pi (64‑bit, OS: [your distro/version])

Channel details

• Peer id: 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f
• short_channel_id: 928319x1161x0
• funding_txid: 004dee0b164d82f5ecf716a70f659e206644f46ae0a3bfc5f4aeeaf1d32dbc4d, vout: 0
• channel_type.names: ["static_remotekey/even","anchors/even"]
• lost_state: true
• state: ONCHAIN
• status: ["ONCHAIN:Owning subdaemon onchaind died (61952)"]

Relevant listpeerchannels snippet:

{
  "channels": [
    {
      "peer_id": "03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f",
      "channel_type": {
        "bits":,[2][3]
        "names": ["static_remotekey/even", "anchors/even"]
      },
      "state": "ONCHAIN",
      "lost_state": true,
      "scratch_txid": "84bbfec75a53ab60785d66c4f9a7f096793c610fb0c93ac5bdfbf5c5bb95eb33",
      "short_channel_id": "928319x1161x0",
      "channel_id": "4dbc2dd3f1eaaef4c5bfa3e06af44466209e650fa716f7ecf5824d160bee4d00",
      "funding_txid": "004dee0b164d82f5ecf716a70f659e206644f46ae0a3bfc5f4aeeaf1d32dbc4d",
      "funding_outnum": 0,
      "close_to_addr": "bc1pt27ne5sn5zkfzfj7ls0rs2dhqwxmudksur6a8l5pt4k0yjrut7ys35swky",
      "opener": "local",
      "closer": "local",
      "features": ["option_static_remotekey", "option_anchors"],
      "status": [
        "ONCHAIN:Owning subdaemon onchaind died (61952)"
      ]
    }
  ]
}

Logs around the crash

... INFO lightningd: Server started with public key 02577b9cde9daca28d01c27b323dfa38ddc1114258b7091aba45f9c00eb61678e0 ...

lightning_onchaind: Could not find resolution for output 2 (version v25.12.1)
...
**BROKEN** 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f-onchaind-chan#1:
STATUS_FAIL_INTERNAL_ERROR: Could not find resolution for output 2
**BROKEN** 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f-chan#1:
Owning subdaemon onchaind died (61952)


Commitment transaction

This is the on-chain tx spending the funding outpoint:

    txid: d9be1412596fab9b9c0417010393c2493f208220dac0efb2bb5f76be020d6db3

    blockheight: 934855



Output 2 (index 2) has since been spent on-chain.

The spending transaction is not recognized by my Bitcoin Core wallet, so output 2 appears to be remote‑owned.

Output 4 (belonging to me) have not shown up in CLN listfunds



Channel transitions through CHANNELD_NORMAL → AWAITING_UNILATERAL → FUNDING_SPEND_SEEN → ONCHAIN.

onchaind logs “Could not find resolution for output 2”, then:

    STATUS_FAIL_INTERNAL_ERROR: Could not find resolution for output 2

    Marks the channel as **BROKEN** and exits, leading to status ONCHAIN:Owning subdaemon onchaind died (61952).

lost_state is true on this channel.

Questions

    Is onchaind expected to handle anchors + lost_state channels without aborting when there is a remote‑only output like this?

    Is there a known fix or patch for this scenario in a newer CLN release?

[enaples]

From what I can see, the close_to_address of your channel is different from the one owning the funds of index 2 of the closing transaction.
Have you recently updated your CLN version? Do you recall which version you had when you opened the channel?
Just to be sure, you bitcoin node is not pruned and has not txindex in config file, is it correct?

[enaples]

Since you shared funding_txid, I was able to retrieve the closing transaction from some bitcoin blockchain explorer:

{
  "txid": "d9be1412596fab9b9c0417010393c2493f208220dac0efb2bb5f76be020d6db3",
  "hash": "dbb08df472a18948f23c67950402f4048304e99880ffda7ead883c884d31b50f",
  "version": 2,
  "size": 487,
  "vsize": 322,
  "weight": 1285,
  "locktime": 551151871,
  "vin": [
    {
      "txid": "004dee0b164d82f5ecf716a70f659e206644f46ae0a3bfc5f4aeeaf1d32dbc4d",
      "vout": 0,
      "scriptSig": {
        "asm": "",
        "hex": ""
      },
      "txinwitness": [
        "",
        "3045022100f83d6c2b821babb5cb94a037ed90b6ec0ebe332e36d449324ca589d595cc3a9d022051387124c3c898f10195384aa337d23d2a2343600000c6a07619b75df18b531a01",
        "304402206d71530a0f02e20da79ddaf434a32e20f1b64ca7ca5d26c5f86db997187c7cc10220661c781cf979635b4432e218a6b222b07bae17658ee302ae05849a01e54b7ba601",
        "522102866eff81125768309b5c99be0e58960df5b6514ed7a263ba74aef4c9664ba07f2103d5077bdf7c81a24a1b4d37b0fe4ec0a3417c8ea4ba76dc6b43fe2186044a8da652ae"
      ],
      "sequence": 2162067111
    }
  ],
  "vout": [
    {
      "value": 0.00000330,
      "n": 0,
      "scriptPubKey": {
        "asm": "0 398a8cbe6f59a95497ff435a1578e8f0a15a16b71854ce5c5bdd79c3ea2b661f",
        "desc": "addr(tb1q8x9ge0n0tx54f9llgddp278g7zs4594hrp2vuhzmm4uu863tvc0s0zr2al)#cqp2m7dg",
        "hex": "0020398a8cbe6f59a95497ff435a1578e8f0a15a16b71854ce5c5bdd79c3ea2b661f",
        "address": "tb1q8x9ge0n0tx54f9llgddp278g7zs4594hrp2vuhzmm4uu863tvc0s0zr2al",
        "type": "witness_v0_scripthash"
      }
    },
    {
      "value": 0.00000330,
      "n": 1,
      "scriptPubKey": {
        "asm": "0 a76f47898afb5901e1239574edb29ac0c2c0442059abd7203975f35f0b231573",
        "desc": "addr(tb1q5ah50zv2ldvsrcfrj46wmv56crpvq3pqtx4awgpewhe47zerz4es70pt23)#9xkm7fq9",
        "hex": "0020a76f47898afb5901e1239574edb29ac0c2c0442059abd7203975f35f0b231573",
        "address": "tb1q5ah50zv2ldvsrcfrj46wmv56crpvq3pqtx4awgpewhe47zerz4es70pt23",
        "type": "witness_v0_scripthash"
      }
    },
    {
      "value": 0.00002101,
      "n": 2,
      "scriptPubKey": {
        "asm": "0 c150ae701cb82f66ac849163178742d4237993448d4dba20dadbc45fb4a00a4a",
        "desc": "addr(tb1qc9g2uuquhqhkdtyyj9330p6z6s3hny6y34xm5gx6m0z9ld9qpf9qyflsp4)#87zcuqhz",
        "hex": "0020c150ae701cb82f66ac849163178742d4237993448d4dba20dadbc45fb4a00a4a",
        "address": "tb1qc9g2uuquhqhkdtyyj9330p6z6s3hny6y34xm5gx6m0z9ld9qpf9qyflsp4",
        "type": "witness_v0_scripthash"
      }
    },
    {
      "value": 0.00178817,
      "n": 3,
      "scriptPubKey": {
        "asm": "0 95f8cc8d8f6d98fe95c25642dcc1e3de1902c66a779ea0e691606a8f8fa2d04d",
        "desc": "addr(tb1qjhuverv0dkv0a9wz2epdes0rmcvs93n2w702pe53vp4glraz6pxsmkc55s)#j3000cvs",
        "hex": "002095f8cc8d8f6d98fe95c25642dcc1e3de1902c66a779ea0e691606a8f8fa2d04d",
        "address": "tb1qjhuverv0dkv0a9wz2epdes0rmcvs93n2w702pe53vp4glraz6pxsmkc55s",
        "type": "witness_v0_scripthash"
      }
    },
    {
      "value": 0.00316794,
      "n": 4,
      "scriptPubKey": {
        "asm": "0 f8d71d1adaeccbf0bc82997177a26d5ab783b610e6d4f0ef46fd19a43d0b7758",
        "desc": "addr(tb1qlrt36xk6an9lp0yzn9ch0gndt2mc8dssum20pm6xl5v6g0gtwavq8tykae)#n8l9tmp3",
        "hex": "0020f8d71d1adaeccbf0bc82997177a26d5ab783b610e6d4f0ef46fd19a43d0b7758",
        "address": "tb1qlrt36xk6an9lp0yzn9ch0gndt2mc8dssum20pm6xl5v6g0gtwavq8tykae",
        "type": "witness_v0_scripthash"
      }
    }
  ]
}

Output 0: 330 sats - P2WSH - Anchor
Output 1: 330 sats - P2WSH - Anchor
Output 2: 2,101 sats - P2WSH - HTLC
Output 3: 178,817 sats - P2WSH - to_local OR to_remote
Output 4: 316,794 sats - P2WSH - to_local OR to_remote

Consider that the output [0, 1] could be below dust limit. Output 2 is the reason why the channel was force close. One of output [3, 4] is yours. Is it appears when you call listfunds?

[enaples]

Here the error before crash for completeness:

lightningd-1 2026-02-06T15:48:15.918Z DEBUG   lightningd: Adding block 104: 42b43bceb92c18c88fabfd66680ca6db42c164aee96cdd288fd97d9f9d211fd5

lightningd-1 2026-02-06T15:48:15.919Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-chan#1: 
Got UTXO spend for 5ae82270d7c24bafa75a38e1b765bc0dd35f3acd73ea1019505cd74c1ab3bfb9:0: 380cab7b86251fd7c5503dde57042cfbd73454f83a1f846fc1180216242921c5
lightningd-1 2026-02-06T15:48:15.919Z INFO    033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-chan#1:
 State changed from CHANNELD_NORMAL to FUNDING_SPEND_SEEN
lightningd-1 2026-02-06T15:48:15.922Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1:
 pid 24783, msgfd 85
lightningd-1 2026-02-06T15:48:15.922Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-chan#1: 
channel->static_remotekey_start[LOCAL] 0
lightningd-1 2026-02-06T15:48:15.923Z DEBUG   hsmd: new_client: 1
lightningd-1 2026-02-06T15:48:15.923Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-connectd: 
peer_downgrade
lightningd-1 2026-02-06T15:48:15.929Z DEBUG   lightningd: Got first depth change 0->1 for 380cab7b86251fd7c5503dde57042cfbd73454f83a1f846fc1180216242921c5
lightningd-1 2026-02-06T15:48:15.930Z DEBUG   gossipd: REPLY WIRE_GOSSIPD_NEW_BLOCKHEIGHT_REPLY
with 0 fds
lightningd-1 2026-02-06T15:48:15.931Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1:
Tracking output 5ae82270d7c24bafa75a38e1b765bc0dd35f3acd73ea1019505cd74c1ab3bfb9:0: FUNDING_TRANSACTION/FUNDING_OUTPUT
lightningd-1 2026-02-06T15:48:15.931Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Remote per-commit point: 033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a
lightningd-1 2026-02-06T15:48:15.931Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Old remote per-commit point: 033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a
lightningd-1 2026-02-06T15:48:15.931Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
reducing max_possible_feerate from 2500000...
lightningd-1 2026-02-06T15:48:15.934Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
... to 4015
lightningd-1 2026-02-06T15:48:15.934Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
commitnum = 3, revocations_received = 3
lightningd-1 2026-02-06T15:48:15.934Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Their unilateral tx, old commit point
lightningd-1 2026-02-06T15:48:15.934Z INFO    033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-chan#1: 
State changed from FUNDING_SPEND_SEEN to ONCHAIN
lightningd-1 2026-02-06T15:48:15.935Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
billboard perm: Tracking their unilateral close
lightningd-1 2026-02-06T15:48:15.936Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Resolved FUNDING_TRANSACTION/FUNDING_OUTPUT by THEIR_UNILATERAL (380cab7b86251fd7c5503dde57042cfbd73454f83a1f846fc1180216242921c5)
lightningd-1 2026-02-06T15:48:15.936Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Deriving keyset 3: per_commit_point=033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a 
self_payment_basepoint=02e3b2d060da273f88c950668c6775f1886f1612adce6f62a1e7715b01c31af7a4 
other_payment_basepoint=03fb033e66c580211cf74a3f18c142982a521d58e013deddf405bd6825e2ddf4f1 
self_htlc_basepoint=03da233776bc38dc3d15a2b9a478ef126d168bdaf4f34a43fca659d36f60491fe6 
other_htlc_basepoint=026b87ce278b93b1897e236b2dec0ce7b52b1b41cc8f47cfbd1e63aef8ce11f0a7 
self_delayed_basepoint=02af91be58320625633067d2047a32e5884d9b54ad6228445a71ebe8c7fa49a809 
other_revocation_basepoint=0236713ebe4ac57092474a464498ed4aaa55088060fabfd687fc1a9aaaef1bb56c
lightningd-1 2026-02-06T15:48:15.940Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Deconstructing unilateral tx: 3 using keyset:  self_revocation_key: 
03196e1b7e8b2f387e64a0142cadf694742d94c9ae76624333779fc9f239f73c8e self_delayed_payment_key: 
03a66bced82cbf3c890109239b9f9d818c570e66fbbd816a825c63c6fd9d87445b self_payment_key: 
02c512880c81e02f10b54b85fd236800f5dad7d80fc5186d74048ac42b2299f639 other_payment_key: 
03fb033e66c580211cf74a3f18c142982a521d58e013deddf405bd6825e2ddf4f1 self_htlc_key: 
03575970a3bd7269f61eff284212bf2bd601e7354af7e799a3f28d2210ef1bf481 other_htlc_key: 
03e7416e29f2fab210cbe328b2e0647587420676b9b1080b939e4602f0ae93e9e3
lightningd-1 2026-02-06T15:48:15.940Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Output 0: 0020515beb78b1125911558a77ff7a71d76daf576ea6490d4e1ac2e9e9fc6a4290ef
lightningd-1 2026-02-06T15:48:15.940Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: Output 1: 
00209ae58e501ebe2ff64d78e524f41659b5e33825a21887c4b428c79c7073b47025
lightningd-1 2026-02-06T15:48:15.940Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: Output 2: 
0020a8845abfd3f6719c076a9b31de0438db043f9c9ffcaff3fee931c5e910a643e1
lightningd-1 2026-02-06T15:48:15.940Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: Output 3: 
00205936acdb20a3b4f1aff5070e01a60e3c6c3dd07b4bb412e423c3ffab58582c2c
lightningd-1 2026-02-06T15:48:15.940Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: Output 4: 
0020c4280dda3a573307d0af3f9af0781a57acfc3521fb21ec01b5591625a5468e46
lightningd-1 2026-02-06T15:48:15.941Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Script to-them: 5: 0020fd20ab878425aef1b229dbb598bcf9a065fc3e0047dfa50d35bc92eb567d58a2 
(632103196e1b7e8b2f387e64a0142cadf694742d94c9ae76624333779fc9f239f73c8e6755b2752103a66bced82cbf3c890109239b9f9d818c570e66fbbd816a825c63c6fd9d87445b68ac)
lightningd-1 2026-02-06T15:48:15.941Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: Script to-me: 
00205936acdb20a3b4f1aff5070e01a60e3c6c3dd07b4bb412e423c3ffab58582c2c
lightningd-1 2026-02-06T15:48:15.941Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Tracking output 380cab7b86251fd7c5503dde57042cfbd73454f83a1f846fc1180216242921c5:0: THEIR_UNILATERAL/ANCHOR_TO_US
lightningd-1 2026-02-06T15:48:15.941Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Ignoring output 380cab7b86251fd7c5503dde57042cfbd73454f83a1f846fc1180216242921c5:0: THEIR_UNILATERAL/ANCHOR_TO_US
lightningd-1 2026-02-06T15:48:15.941Z DEBUG   033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Grinding for commitment to_remote (ours)
lightning_onchaind: Could not find resolution for output 1 (version v25.12.1)
0x104fe915b ???
        send_backtrace+0x4f:0
0x104f4e097 status_failed
        common/status.c:207
0x104f33d5b handle_their_unilateral
        onchaind/onchaind.c:3210
0x104f314c3 main
        onchaind/onchaind.c:0

lightningd-1 2026-02-06T15:48:15.970Z **BROKEN** 033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
Could not find resolution for output 1 (version v25.12.1)
lightningd-1 2026-02-06T15:48:15.970Z **BROKEN** 033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
backtrace: common/status.c:207 (status_failed) 0x104f4e097
lightningd-1 2026-02-06T15:48:15.970Z **BROKEN** 033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
backtrace: onchaind/onchaind.c:3210 (handle_their_unilateral) 0x104f33d5b
lightningd-1 2026-02-06T15:48:15.970Z **BROKEN** 033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
backtrace: onchaind/onchaind.c:0 (main) 0x104f314c3
lightningd-1 2026-02-06T15:48:15.970Z **BROKEN** 033845802d25b4e074ccfd7cd8b339a41dc75bf9978a034800444b51d42b07799a-onchaind-chan#1: 
STATUS_FAIL_INTERNAL_ERROR: Could not find resolution for output 1
Lost connection to the RPC socket.Lost connection to the RPC socket.Lost connection to the RPC socket.

[tikistack-sudo]

Have you recently updated your CLN version? Do you recall which version you had when you opened the channel?
Just to be sure, you bitcoin node is not pruned and has not txindex in config file, is it correct?

I believe i did update but dont recall which version i used to open the channel. I opened the channel with tx
004dee0b164d82f5ecf716a70f659e206644f46ae0a3bfc5f4aeeaf1d32dbc4d
and believe i had the most recent release of that time. my bitcoin node is not pruned. it does say txindex=1 in config file (~/.bitcoin/bitcoin.cong)

Consider that the output [0, 1] could be below dust limit. Output 2 is the reason why the channel was force close. One of output [3, 4] is yours. Is it appears when you call listfunds?

It does not appear when i call listfunds. Output 4 is supposed to be mine.

[enaples]

Have you already tried with lightning-cli dev-rescan-outputs? Make sure that in your lightning.conf there is developer entry. Take a look here.

[tikistack-sudo]

yes. it only shows outputs that have been confirmed onchain but doesn't resolve my first issue. Due to lack of completing output 2 it wont proceed to output 4 which has my [our_msat]. Peer has already received there msat.

[enaples]

You can try rescan option in lightning.conf as reported here.

Since your funding transaction has around 1350 confirmation, add rescan=1700 should be safe and should not take too much time. Your node should be able to rebuild its internal state

[tikistack-sudo]

i believe the funds went to an 'intermediary' wallet address, since it was a unilateral close done by my peer. the intermediary address doesnt belong to my wallet and the cln was interrupted before forwarding to a wallet addr that belongs to my hsm secret. thoughts?

[enaples]

Thanks for the patience. Try to use lightning-hsmtool doing the following lightning-hsmtool <your_P2WPKH_address> <peer_node_id> <max_channel_dbid> <hsm_secret>.

Be aware! Your funds are locked to a P2WSH not a P2WPKH so lightning-hsmtool probably will fail.

You should try:
lightning-hsmtool guesstoremote bc1qlrt36xk6an9lp0yzn9ch0gndt2mc8dssum20pm6xl5v6g0gtwavqsrje8k 03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f 100 /path/to/your/hsm_secret

If it doesn't succeed, try to increase the max_channel_dbidup to 1000.

If it succeed, at some point it should print your address (bc1qlrt36xk6an9lp0yzn9ch0gndt2mc8dssum20pm6xl5v6g0gtwavqsrje8k) and the associated private key in hex format.

Now, you need to convert it in a WIF key. You can do it easily with python. Here a simple script:

import hashlib

hex_key = '<your_hex_key_here>'
key_bytes = bytes.fromhex(hex_key)
extended = b'\x80' + key_bytes + b'\x01'

checksum = hashlib.sha256(hashlib.sha256(extended).digest()).digest()[:4]

# Base58Check encode
payload = extended + checksum
alphabet = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'
num = int.from_bytes(payload, 'big')
result = ''
while num > 0:
    num, rem = divmod(num, 58)
    result = alphabet[rem] + result
# Should strart with L or R
print(result)

Now, afaik, only Electrum Wallet (and bitcoin-core) allows you to import WIF keys.
So,

1. Download Electrum Wallet (and verify the keys)
2. File --> New/Restore --> give a name to the wallet
3. Chose "Import Bitcoin addresses or private keys"
4. Try to add p2wsh:<printed result from python script> (I do not know if it works since p2wsh could be any locking script so maybe Electrum does not know which script you used)

Let me know if you where able to recover the funds!

Please, let me know if you were able to retrieve the funds!