Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.11.0.0 2017-08-15T20:03:37Z 2017-08-15T20:03:37Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-08-12T14:24:39Z urn:sha1:827afcb7ea10eb2bf03ffb7ad2520f29cd53019f Not used yet. 2017-08-12T19:36:31Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-08-12T09:59:54Z urn:sha1:2ec15a693165db96dd7e75ee060ea4622a47ab7a 2017-08-09T09:28:41Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-08-09T08:31:00Z urn:sha1:635929eaca6b376708d7c5fabf9b743b8a706981 We won't even talk to a peer which claims a wrong version for its top block. This will avoid syncing to known bad peers in the first place. Also add IP fails when failing to verify a block. 2017-08-07T08:33:04Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-07-02T21:41:15Z urn:sha1:5be43fcdbad5ed034b07831473e07f47b7b10947 A block queue is now placed between block download and block processing. Blocks are now requested only from one peer (unless starved). Includes a new sync_info coommand. 2017-05-27T10:35:54Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-05-27T10:35:54Z urn:sha1:072102cfd23c47d36f4d51875026339a767f22ae All code which was using ip and port now uses a new IPv4 object, subclass of a new network_address class. This will allow easy addition of I2P addresses later (and also IPv6, etc). Both old style and new style peer lists are now sent in the P2P protocol, which is inefficient but allows peers using both codebases to talk to each other. This will be removed in the future. No other subclasses than IPv4 exist yet. 2017-02-21T17:38:18Z Riccardo Spagni ric@spagni.net 2017-02-21T17:38:18Z urn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359 2017-02-12T12:33:45Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-02-11T19:38:18Z urn:sha1:9faef1f83abe4f1eafad9a605511cb2624201cdd - fix wrong block being used when a new block is received between a node elaying a fluffy block and sending a new fluffy block with txes a peer did not have - misc a neverending ping pong requesting the same missing txids when a new block is received in the meantime, causing the top block to not be the one we need - send the original fluffy block message block height when sending a new fluffy block, not the current top height, which might have been updated since - avoid sending back the whole block blob when asking for txes, send only the hash instead - plus misc cleanup and additional debugging logs 2017-02-08T13:45:15Z kenshi84 kenshi84@protonmail.ch 2017-01-26T15:07:23Z urn:sha1:8027ce0c75f882de0523e668defa0bc3c8564e96 2016-11-09T19:24:27Z Dion Ahmetaj Dion Ahmetaj 2016-10-26T19:00:08Z urn:sha1:d61bd8187e170cd4ae56f5047cc172d257c26237 Added a new command to the P2P protocol definitions to allow querying for support flags. Implemented handling of new support flags command in net_node. Changed for_each callback template to include support flags. Updated print_connections command to show peer support flags. Added p2p constant for signaling fluffy block support. Added get_pool_transaction function to cryptnote_core. Added new commands to cryptonote protocol for relaying fluffy blocks. Implemented handling of fluffy block command in cryptonote protocol. Enabled fluffy block support in node initial configuration. Implemented get_testnet function in cryptonote_core. Made it so that fluffy blocks only run on testnet. 2015-12-31T06:39:56Z Riccardo Spagni ric@spagni.net 2015-12-31T06:39:56Z urn:sha1:de0392685063d93dbdad3a6b1a2712eaf94dd51a