Cryptocurrency

I accidentally -torcontrol=1 today (instead of -listenonion=1) and was confused that it was accepted, as the argument needs to be host:port.

Expected outcome would be an error message and exiting.

Useful skills:

• C++
• Understanding of bitcoin core's initialization sequence

Want to work on this issue?

For guidance on contributing, please read [CONTRIBUTING.md](http

Describe the enhancement

In the docs, I'm not seeing any /api/v1/healthcheck endpoint or whatnot (heartbeat specific, not referencing ping). Potentially returning the time of last heartbeat and any errors (if present).

This would be highly useful for monitoring and ensuring nothing crazy is going wrong. This would make monitoring from another server much easier and with some simple sc

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

Background

When doing a closechannel, you need to give a txid and index, separately. Having the option to provide a channel point would be useful.

Marnix
What would be the risk in accepting a chan_point in closechannel? :thinking_face:

guggero
_on the RPC level it's a channel point. so

Currently stratumserver has no unit tests. This will improve the quality and allow future commits to be TDD safe. All units will be tested to ensure the module as a unit itself is tested.

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.

The instructions and infrastructure for building on windows are not very good. It takes too long and there are too many manual steps and too much ambiguity and it takes too long between each manual step. We need to do better. I followed the instructions at build options on nano.org. I did not try to follow the steps taken by the CI build which maybe would been better because at least there would b

Add custom clj-kondo hooks for macroses to ensure that lint rules are followed inside them.

Macros to be handled:

• fx/defn - similarly to defn with check on metadata for ::events
• fx/merge - seems like it could be lint'ed as thread macro, plus warn on limitations
• defview
• letsubs - lint as let + check on types for

Summary

We should charge extra gas when doing serialization.

Epic: #8917

Problem Definition

Today we only charge gas for doing storage operations and loops. For simple operations we only charge gas for a known expensive operations, like signature validation. Serialization is also known to be expensive (especially the "text mode" like JSON). And if there is lot of back and forth t

Those two things tend to stall a bit on startup. It would be nice to have the [0%]... output for them.