Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.9.2 2016-03-11T15:09:50Z 2016-03-11T15:09:50Z Howard Chu hyc@symas.com 2016-03-11T12:25:28Z urn:sha1:b937a2c915861900d047d4d4a24af31c454e3540 and all other associated IPC 2015-02-20T21:28:03Z rfree2monero rfreemonero@op.pl 2015-02-20T21:28:03Z urn:sha1:ae2a50659f7dc74a5446a0dc3a5f8f78563b9e1f new update of the pr with network limits more debug options: discarding downloaded blocks all or after given height. trying to trigger the locking errors. debug levels polished/tuned to sane values. debug/logging improved. warning: this pr should be correct code, but it could make an existing (in master version) locking error appear more often. it's a race on the list (map) of peers, e.g. between closing/deleting them versus working on them in net-limit sleep in sending chunk. the bug is not in this code/this pr, but in the master version. the locking problem of master will be fixed in other pr. problem is ub, and in practice is seems to usually cause program abort (tested on debian stable with updated gcc). see --help for option to add sleep to trigger the error faster. 2015-02-20T21:13:00Z rfree2monero rfreemonero@op.pl 2015-01-05T19:30:17Z urn:sha1:eabb519605cab00dbaa5a1868d229f09c74570a6 commands and options for network limiting works very well e.g. for 50 KiB/sec up and down ToS (QoS) flag peer number limit TODO some spikes in ingress/download TODO problems when other up and down limit added "otshell utils" - simple logging (with colors, text files channels)