Results 35 issues of Shorn

**Scenario:** The XBridge protocol currently uses a mix of `(float)`, `double`, `int64_t` and `uint64_t` and as such we are seeing precision issues eg when partial orders are created (ref: https://github.com/blocknetdx/blocknet/issues/570)...

bug

More info to follow...

bug

**Env:** Core wallet 4.3.3, Mac, Standard GUI.

bug

**Scenario:** requesting `xrGetBlockCount` via core console or cli returns unreliable results. **Issue:** There seems to be an upper limit on the queryCount parameter - possibly if the count is higher...

bug

**Info:** There is a hard upper limit to `queryCount`when appended to any XRouter call via console or cli (ie: when setting `node_count`). **To do:** - [ ] update all references...

improvement

**To do:** Write XB unit tests, using https://github.com/blocknetdx/blocknet/tree/master/test, and implementing: --- service node logic --- connector logic --- xb logic and trading tests more info to follow...

enhancement

**Scenario:** requesting `xrGetBlockCount` via core console or cli with a queryCount > 50 returns an error. ``` xrgetblockcount BLOCK 10 { “reply”: 2244915, “uuid”: “08ae7d53-49b7-498a-8d3d-9b3ece4d8a03” } xrgetblockcount BLOCK 100 {...

improvement

**Scenario:** To support the continuation of Go-XRouter development (https://github.com/blocknetdx/go-xrouter/issues/44), we need an analysis of the XRouter C++ code in order to tell whether there is an issue with the way...

**Scenario:** Sending some XRouter commands via wallet console requires the parameters to be uppercase eg: `xrgetblockcount ltc` fails, but `xrgetblockcount LTC` works as expected. Given that all other console commands...

improvement