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
Is your feature request related to a problem? Please describe.
Ugly title for asset new asset. The asset node gets New Asset title after entering the codename.
Describe the solution you'd like
auto rename by referring the codeName --> iconName
set iconName as variable.
Describe alternatives you've considered
Additional context
Add any other context or screenshots
The setting used to store the selected pairs from binance to be synced has a bad name PAIRS that should be updated to something more descriptive. Currently is defined as a constant here https://github.com/rotki/rotki/blob/develop/rotkehlchen/db/constants.py#L3
The task to close this issue is:
A useful feature where the user specifies the quantity to take in an orderbook and callback returns the average price paid for that lot size. For example if the offers in the order book for BTC-USD was the following:
Price | size
11,000 | 1
10,500 | 1
10,000 | 1
If the user specified quantity 3, the callback would return 10,500.
I believe this is incorrect behavior. Both false and null are intended to derive an X-address without a tag, but null seems to derive the same result as the tag 0.
> xrpl.deriveXAddress({publicKey: "ED02C98225BD1C79E9A4F95C6978026D300AFB7CA2A34358920BCFBCEBE6AFCD6A", tag: false, test: false})
'X7FbrqVEqdTNoX5qq94rTdarGjeVYmkxi8A1TKAJUnyLL9g'
> xrpl.deriveXAddress({publicKey: "ED0
at the beginning of every epoch, there is a period of time when beacon is unavailable (until enough ballots are seen by the node and beacon value determined)
during this time, syncer will see that beacon is not available and will not request tortoise to verify a layer.
but the problem is: syncer uses two goro
Our current JSON-RPC wiki is outdated.
A lot of commands were changed, new commands were added and some were removed.
Some description might need to be rewritten in a more comprehensible way.
This is a good first issue for anyone who wants to start familiarizing with the PIVX sources.
This bounty is to improve test coverage on the Matic contracts repo. The repo contains the following contracts:
For an overview of
Can this library be use to handle more than 1 wallet, bitcoin-cli.exe have the createwallet command with a unique id and the connection can have the --rpcwallet with the same id.
What are the alternative if I need to handle more than 1 wallet. Thanks
Add a description, image, and links to the cryptocurrencies topic page so that developers can more easily learn about it.
To associate your repository with the cryptocurrencies topic, visit your repo's landing page and select "manage topics."
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