Reported upstream a couple of months ago: https://travis-ci.community/t/no-space-left-on-device-for-system-z/5954

While ccxt does a great job unifying most functions / settings, not everything is or can be unified.
I think it would be good to provide a separate wiki/documentation page which documents exchange-specific properties.

The behavior is there now and all is working well - but to find it users need to search through issues (which are not easy to navigate) to find certain exchange-specifics - and o

Clients that are built around the API need some additional information to work effectively. This is the following:

1. Peer list API: show more information about connected peers including the block height / cumulative difficulty of the peer. Basically, so the API provides at least as much information as the server TUI does.

2. Status information: Similarly, the minimum amount of info the stat

Background

When dynamically rejecting an inbound channel, the connecting peer should receive an indication of why their request was rejected.

Examples of existing messages:

1. Minimum channel size not reached
2. Multiple channels not supported

Steps to reproduce

1. Open a channel that will get dynamically rejected
2. Get generic rejection message

Expected behaviour

To be done on lbrytech repo probably.
The wallet is currently configured as defined originally in ElectrumX, there are some docs for it already in there.

Keep in mind that we added new configuration keys and should clean up the unused ones at some point, so we need something easy

Actual docs (https://www.getmonero.org/resources/developer-guides/wallet-rpc.html#get_transfer_by_txid) tells us what get_transfer_by_txid return only transfer object, and did not mention what it return a transfers array too.

example (testnet):

• `curl -X POST http://localhost:18082/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_transfer_by_txid","params":{"txid":"a5447204b

All read&write on BlockPool.numPending has been protected by BlockPool.mtx, the atomic operate maybe redundant.

when I following :

https://github.com/input-output-hk/cardano-sl/blob/master/docs/how-to/build-cardano-sl-and-daedalus-from-source-code.md

Then:
nix-build -A cardano-sl-static --cores 0 --max-jobs 2 --no-build-output --out-link master

result:
error: attribute 'cardano-sl-static' in selection path 'cardano-sl-static' not found

when I build with cardano-sl-node-static. how much

I would love to add some new exchanges in there for you (and me) and would be happy to do so with just a little guidance as to which objects you're using for it without me doing a full code dig.

Assuming this is easily extensible. If not, I guess that would be my feature request... lol. Extensible exchange objects with documentation.

For a university school project I will be making some edits to your documentation which will aim to make writing more technical

Please add edits if you would like :)

There are lots of configurable settings in the config.json file.

https://github.com/xmrig/xmrig/blob/master/src/config.json

Where can I find detailed documentation on what the settings do?

Problem

Currently when a user receives a PN, we show a very generic message (no indication of sender, body, etc). This will change in the future (e.g. with status-im/status-react#7043), so it would be good to be more explicit about the fact that we are showing a generic PN message due to the db being locked. Also, since we may receive PNs from users we've since removed

Is there a way to cancel an order before the unfilledtimeout expires, in a way that the local sqlite database remains consistent with the exchage?
Please note that the RPC command /forcesell or /forcebuy do not help with this. In the case of a SELL, one would like to cancel the SELL order in Order Book before the sale is actually executed. It seems a bit different from forcing a SELL with the RPC

A user asked me on slack if estimatefee returns BTC per Byte or BTC per Kilobyte... honestly I don't know and it's a bit hard to tell. I compared mainnet full nodes bcoin vs Bitcoin Core and observed a wild divergence (outputs below).

From Bitcoin Core help:

Estimates the approximate fee per kilobyte needed for a transaction to begin
confirmation within conf_target blocks if possible

Hello everyone,

This is just a very small improvement that I think can help:

Adding average "buy" price and average "sell" price under the % of profit (and using profit period as a reference).

So let's say you have profit set to 1 (so 1h):
We calculate the average of buy price for the trades made in the last hour =
(buy price1quantity1 + buy price2quantity2 ...) / total quantity of bu

Hi,

I the documentation here it says: "Support for accessing multiple exchanges per algorithm, which opens the door to cross-exchange arbitrage opportunities."

Does catalyst really support multiple exchanges using the same algorithm? If so - how this can be done? (no documentation for it)

Thanks!

Client.get_historical_klines returns a list of 12 elements,. What do all of them represent and where is this documented?

Documentation only mentions the 5 OHLCV values, unless I am missing something.

I changed types/coin.go reDnmString to make the benchmark BenchmarkAccountMapperGetAccountFoundWithCoins pass

	reDnmString = `[a-zA-Z][a-zA-Z0-9]{2,15}`

Seems that capitalized character like LTH is not accepted if we don't change.

	reDnmString = `[a-z][a-z0-9]{2,15}`