cronicc
cronicc
The key values in RPC JSON commands inherited from BTC/ZEC all use camel case. We use spaces in many of the newly added commands. This is inconsistent with the style...
This should be enforced on the Mainchain as well as the SDK side. https://github.com/HorizenOfficial/zend_oo/blob/18f934386b08ca0c497c9dedb2da7988f3ced888/src/main.cpp#L735-L746
sc_create, sc_send, sc_sendmany, send_certificate RPC commands should have a "from address" argument
It is currently not possible to choose from which MC address utxo will be picked to send to a SC or to add a fee to the certificate submission transaction....
Since fixing https://github.com/HorizenOfficial/zend_oo/issues/36 the `decoderawcertificate` and `getrawcertificate` RPC commands are not needed anymore. `getrawtransaction` and `decoderawtransaction` now also work for certificates.
We have a clear distinction between transparent address RPC commands (no prefix) and shielded address RPC commands (`z_` prefix). For some of the sidechain related RPC commands, the `sc_` prefix...
Both commands accomplish the same thing using different APIs. Investigate where both commands are used and if choosing one and removing the other is possible. If API features in one...
Both commands accomplish the same thing using different APIs. Investigate where both commands are used and if choosing one and removing the other is possible. If API features in one...
In broad terms we currently have two types of RPC commands that are able to send transparent transactions: 1. Commands inherited from bitcoin that use the deprecated account model (`sendtoaddress`,...
The expected behavior for transactions that calculate the transaction fee based on transaction size is to use a rate of 1sat/byte. This is the case for any transparent transactions created...
#133 depends on this.