Most of our test scripts are written in python. We don't have enough reviewers for bash scripts and they tend to be clumsy anyway. Especially when it comes to argument parsing.

Thus, contrib/devtools/previous_release.sh should be rewritten in python

Useful skills:

Experience with Bash and Python

Want to work on this issue?

The purpose of the good first issue label is t

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

see: dvf/blockchain#50

The underlying exploit to tamper with a blockchain is described there

props to: @TimelessP

The fix should be fairly simple:
affected file: blockchain/blockchain.py

https://github.com/dvf/blockchain/blob/4010cf3273e19146a9cd7b37cf355cb751ffef88/blockchain.py#L82

A noted, currently it reads:

if length > max_length and self.valid

In the past the node and the wallet were in the same repo. When the wallet was extracted into a separate repo, integration tests were moved to - https://github.com/mimblewimble/grin-wallet/tree/master/integration
It would be beneficial to provide a simple way to run integration suits as part of node tests too.
There are several possible options (there are some other for sure):

• Move part of th

Currently the lncli listinvoices --reversed flag has no effect, as it
is of type cli.BoolTFlag https://github.com/lightningnetwork/lnd/blob/ad0a89b844ec9f55b3ca4ddbb4d368dd8e3c0ea9/cmd/lncli/commands.go#L2848
which is true by default.

Correct behavior can be triggered by lncli listinvoices --reversed=True
or lncli listinvoices --reversed=False.

Is this behavior intended? I get th

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

In a few locations across the codebase, memset is used to clear secrets from memory before discarding the memory. However, most compilers will see this as a dead-store and remove the memset call. It is therefore better to use memset_s (from C11) or similar to actually clear those secrets. The actual locations are:

• autotrust.c part of a submodule, let's ignore it for now
• ~getentropy

tendermint debug tool can be used to continuously collect data. We haven't written any documentation/tutorials for it.

Write documentation and/or a mini-tutorial on how to collect profiling data continuously

hello,
for use tribeca on BitFINEX account, in which wallet we should needs to have deposit/balance
BitFINEX Balance wallet should be exchange wallet or margin wallet

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?

CCXT-REST - Open Source Unified REST API of 100+ Crypto Exchange Sites. Built-on top of the powerful ccxt open source project. Available as docker image or a standalone node service.

Full disclosure : I am the author of ccxt-rest

Bug Report

Problem

The amount is the first field in a transaction. When you fill this out, and then add recipient by scanning their QR code, the amount is reset.

Expected behavior

Amount is maintained unless user cancels the Tx.

Actual behavior

Set Tx amount.
Scan recipient QR code.
Amount is cleared and must be re-entered.

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

It look like some currencies have more precision in the mouseover display on the plot than others. For example, EOS shows many digits past the decimal while ETH only shows two. Adding a few more digits would make interpreting the charts much easier. The left plot shows the rounding I'm describing and the right shows the higher precision that EOS displays.

![rounding](https://user-images.githubu

This isn't an issue but a recommendation. The api and docs for the commission models are confusing for the crypto markets, as they are ported directly from zipline. Virtually all of the crypto exchanges I know of charge a percentage of the total quote currency used when buying/selling an asset (so 0.1% of the BTC value for an alt/btc pair, or usd value for btc/usd pair).

Yet the catalyst api h

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.

Many of the sentinel errors in x/staking are r