cronicc
cronicc
MinGW build failing with: ``` /bin/bash ../libtool --tag=CXX --mode=link /mnt/build/depends/x86_64-w64-mingw32/share/../native/bin/ccache x86_64-w64-mingw32-g++ -std=c++11 -Wformat -Wformat-security -Wstack-protector -fstack-protector-all -DBITCOIN_TX -pipe -O2 -g -fopenmp -fwrapv -fno-strict-aliasing -Wno-builtin-declaration-mismatch -Wreturn-type -pthread -Wl,--dynamicbase -Wl,--nxcompat -Wl,--high-entropy-va -L/mnt/build/depends/x86_64-w64-mingw32/share/../lib...
``` make: Entering directory '/home/cronic/Downloads/src/my_projects/zen_sidechain_testnet/depends' funcs.mk:257: warning: overriding recipe for target '/home/cronic/Downloads/src/my_projects/zen_sidechain_testnet/depends/sources/download-stamps/.stamp_fetched-rust-rust-1.42.0-x86_64-unknown-linux-gnu.tar.gz.hash' funcs.mk:257: warning: ignoring old recipe for target '/home/cronic/Downloads/src/my_projects/zen_sidechain_testnet/depends/sources/download-stamps/.stamp_fetched-rust-rust-1.42.0-x86_64-unknown-linux-gnu.tar.gz.hash' funcs.mk:257: warning: overriding recipe for target '/home/cronic/Downloads/src/my_projects/zen_sidechain_testnet/depends/work/build/x86_64-unknown-linux-gnu/rust/1.42.0-4dc79af843d/.stamp_extracted' funcs.mk:257: warning: ignoring...
Except for the library name itself.
https://search.maven.org/artifact/io.horizen/zendoo-sc-cryptolib  Metadata information in pom.xml has to be changed to text instead of variables.
ZencashOfficial -> HorizenOfficial
We have reserved the maven namespace `io.horizen`, all references to `com.horizen` should be changed. As far as I can tell this is not a hard requirement to get the package...
All of the `zen-cli help $command` messages should include examples for zen-cli as well as for curl. Compare e.g. ``` $zen-cli help getrawtransaction [...] Examples: > zen-cli getrawtransaction "mytxid" >...
RPC command output is not sufficiently checked by our current RPC tests, otherwise we'd have detected https://github.com/ZencashOfficial/zen/issues/172 earlier. A RPC test should be added validating each RPC command against expected...
First we should check if both of these endpoints (/node/allPeers, /node/connectedPeers) are needed. Are they doing the exact same thing? If yes remove one of them. Secondly, exposing additional information...