Bitcoin

importaddress (and possibly other legacy-only wallet functions), when used on a descriptor wallet, return a fairly nondescript error:

$ ./bitcoin-cli -regtest importaddress test
error code: -4
error message:
This type of wallet does not support this command

The RPC help of importaddress doesn't mention nor further explain this incompatibility, nor what alternative to use inste

Describe your environment

N/A

Describe the enhancement

Currently it seems the max_open_trades can have significant impact on profit. The only way I have been able to find a good number is to run several back

Problem

Loss and latency metrics might be interesting from the gossip ping-pong protocol.

Proposed Solution

Capture and report them.

Creating a new issue based on lbryio/lbry-sdk#877

• Update ensure_directory_exists() to check that the directory is writable by the current process.
• If it's not, return a useful error
• Add tests to cover the case when
  • download directory does not exist
  • download dir exists but is not writable
  • dir exists an

The fuzz tests we have don't run on my machine anymore with go1.18. dvyukov/go-fuzz is basically deprecated at this point. We should upgrade to language-native testing.F even if it's not that great yet.

Basically the fuzz tests should stay the same, but the build step is changed:

• remove make-level fuzz references
• fuzz tests that don't need to import from other packages can live in

Description

The "send payment" dialogue after seller taker accepted my offer is telling me to "start payment using sepa instant"; the account I used is normal sepa.

Version

1.8.0

S

Reading currencies, alphavantage returns a greeting note ("welcome") and this note raises an error in alphavantage.py line 363.

            elif "Note" in json_response and self.treat_info_as_error:
                raise ValueError(json_response["Note"])

For this reason, alphavantage does not work in home assistant.

We introduced a concept of receipts, a public information any customer can access in #3612.

Currently, it can be visible to the end-user if it's sent over by email via the API, or something along those lines.
Once we're done reconstructing our invoice checkout page in #3567 I think we could add a button somewhere that would simply say receipt similar to what we have with back to store butt