steliosrammos

I've got a similar issue. In block 481824, the tx hash dfcec48bb8491856c353306ab5febeb7e99e4d783eedf3de98f3ee0812b92bad is mistakenly returned by the library as 48a387570eeffb07e8e84642efe36bc4088285fc04db91743a9850bfd1611af2 (which does not exist). Edit: I see now you've mentioned...

The phrasing was a little ambiguous. It all happens after clicking the `Test Connection` in the settings. Here are the logs after clicking `Test Connection`: ``` 2021-12-07T13:44:59Z UpdateTip: new best=00000000000000000006bf92c8f8cf45266190e4541f18572db711eaf884d74c...

Awesome! If that's the case it might be worth noting the `RoutingError`, `InternalError` and `InvalidInputError` all set the error prototype to `RejectionError` as well.

This is quite frustrating, is any work being done to fix it?

What about the first case where only the `description_hash` is passed, without a `description`?

Not sure whether anyone has compiled a list of applications using Mutiny-Net yet, that would be helpful to decide on the default. I believe the Fedi app is using it....