#17851 added std::to_string to the list of locale dependent functions, along with a large number of usage exceptions. It was pointed out that some of these usages are actually likely bugs, and should be fixed rather than hidden as exceptions.

Information Exposure
Vulnerable module: requests
Introduced through: requests@2.18.4
Detailed paths
Introduced through: dvf/blockchain@dvf/blockchain#1369cac2094d36e694da1209d7d4f923264f7f50 › requests@2.18.4
Remediation: Upgrade to requests@2.20.0.
Overview
Requests is a Non-GMO HTTP library for Python

Affected versions of this package are vulnerable to Information Exposure. Upon receiv

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

Using latest version 0.15.0.1. (Edit : on Ubuntu 18.04)
After the CLI wallet was locked, the prompt showed the password in clear while typing.
I'm not a big CLI user so this happened only twice so far, but I thought it's worth reporting this issue.
Not sure if a screenshot is useful, but here's one below anyway.

![image](https://user-images.githubusercontent.com/16813929/72224145-2e286100-35

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

Endpoint: Creates a new Account for the given Wallet.
POST /api/v1/wallets/{walletId}/accounts

account is successfully created when passing "spendingPassword":"null" wallet with spending password.

When I open Tribeca (localhost:3000) it shows Tribeca [dev] instead Tribeca [prod]. I've already changed in env file dev to prod. How should I procedure?

Ps.: My balance doesn't show either.

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.

https://github.com/Jeiwan/blockchain_go/blob/bf64f33069ee081913289e548c4b6917c667f614/blockchain.go#L138

When I try to run this code and print all the transactions' information, I found that Vout is wrong.
I think outIdx should be replaced by out.Value.

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

I'd like to see an Ethereum address added to the custom property of the FUNDING.yml file for GitHub Sponsors. This would allow a canonical address to send funds to. For example, I'm building a project that allows developers to setup one recurring donation that is split between all of their dependencies with an Ethereum address: https://sustainus.io

Hi!

I was using get_batch_stock_quotes on regular basis and suddenly it stopped working (without updating av or any other python libraries). Calling the function for some list of stocks produces the error:

File ".../site-packages/alpha_vantage/alphavantage.py", line 292, in _handle_api_call
raise ValueError(json_response["Error Message"])
ValueError: This API function (BATCH_STOCK_Q

Hi all and Carles,

I think we should forget about the ping and pongs and pong width etc... It's too confusing and useless (especially for newcomers).

Ping width = width
Pong width = target

So using Boomerang or PingPong, you set up a width and a target, and it's more clear for everyone.

So when you do PingPong you buy at a price and want to sell at price + target (width pong). Once yo

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!

Describe the bug
Binance updated their system a few days ago, now the user account WS stream need ping lisenKey to keep a live every 30 minitues. In current version v0.7.4 I found the user account stream dropped every 1-2 hours, I guess the reason maybe we need ping lisenKey every 30 minitues.

Please see the docs here: https://github.com/binance-exchange/binance-official-api-docs/blob/mast