Bitcoin

See bitcoin/bitcoin#22762 (comment)

This can be fixed by creating a new exception type and catching it in the right place.

Useful skills:

• C++ exceptions
• Addrman serialization
• Functional tests

Want to work on this issue?

For guidance on contributing, please read [CONTRIBUTING.md](https://github.com/bitcoin/bitcoin/blob/master/CON

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

Measure::this() is useful for easily adding timing around a function or a block. However, it is not ergonomic when the function takes more than one parameter. With zero or 2+ parameters, the long-form closure syntax is required. Similar workarounds are required when

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

In the output of list channels the private/public status of the channel is returned, but in the output of pending channels the status is not revealed. To allow for recognizing a pending open channel as a private requires waiting for the channel to confirm.

Ideally the PendingChannelsResponse would include the channel flags or the private/public status of the channel to know which type of chan

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.

As discussed on UX channel on Mattermost, we have plenty of features that sometimes may not be entirely clear to people who use BTCPay. Adding a concise description of features may help with this.

_For example, explaining a payment request as a invoice