Konstantin Nick

Will update this with tests similiar to #313

On some other calls it seems to do fine e.g. ```json {"jsonrpc":"2.0","method":"generatetoaddress","params":{"address":"ert1qfkht0df45q00kzyayagw6vqhfhe8ve7z7wecm0xsrkgmyulewlzqumq3ep","nblocks":1},"id":3} ``` I suspect it might be that the jrpc2 library cannot handle named string arrays correctly or something...

```json {"jsonrpc":"2.0","method":"blindrawtransaction","params":{"hexstring":"longhex.."},"id":5} ``` also seems to work, but it has only one single string param

> Can we remove travis in this PR too? Hm simply removing `travis.yml` is not enough

Could you maybe share some logs when trying to sweep the UTXO?

What I like about your solution @guggero is that it allows the musig2 codebase to be adaptible to future musig2 (e.g. breaking `1.X`)changes. However I personally don't think that we...

Just for clarity, you were running bitcoin core yourself serving block filters and using them from your watch-only lnd instance and switching over to using bitcoind directly as the backend...

At peerswap we rolled the dice and landed on: Id | Name | Description -- | -- | -- 42069 | swap_in_request| peerswap 42071 | swap_out_request| peerswap 42073 | swap_in_agreement|...

Hi @bufo24 #8723 will fix this right?

> I would personally have expected the memo on a TAP address to follow the second pattern, where the memo is only for the creator of the address, not also...