ffranr

I've reduced the scope of this PR to just converting `witnessToHex` into a method `ToHexStrings` on TxWitness`.

We should break this issue into smaller issues after discussion.

While digging into this bug, I noticed that the following erroneous change seems quite fundamental, yet surprisingly doesn't cause any tests to fail: https://github.com/lightninglabs/taproot-assets/pull/1810

See also: ``` 2025-09-18 21:12:19.471 [WRN] UNIV: encountered an error whilst syncing with server=(universe.ServerAddr) { ID: (int64) 2, addrStr: (string) (len=31) "universe.signet.laisee.org:8443", addr: (net.Addr) } : failed to execute sync:...

> ~Looking at that last log message, it looks like the minting transaction itself is what is missing the STXO proof.~ > > ~We write the final proofs in `storeMintingProof`...

Update: * I can reproduce the issue locally on every run. * A spend input (vpacket) STXO proof is incomplete: `AssetProof == nil`. * Because this is a spend input,...

Here's the input signet proof that fails to verify: [issue1809-verify-fail-input-proof.zip](https://github.com/user-attachments/files/22700933/issue1809-verify-fail-input-proof.zip)

> Here's the input signet proof that fails to verify: [issue1809-verify-fail-input-proof.zip](https://github.com/user-attachments/files/22700933/issue1809-verify-fail-input-proof.zip) I've reproduced the validation error with the proof binary and tapd `v0.7.0-rc1`. From stepping through the validation logic: *...

I can see that the channel point `7b57e36406cf36d5d8d5846adc7ab1890605cc00632419f6445e3fc53a0b327e:0` is listed in the asset transfer command output that you shared in [assetTx.txt](https://github.com/user-attachments/files/22878836/assetTx.txt). In that CLI output we can see that proof...

Thanks for sharing the logs. I noticed this entry in the log file, which corresponds by outpoint to the channel that was closed: ``` 2025-10-14 12:03:08.733 [INF] FRTR: ChainPorter executing...