monzero-core.git/src/cryptonote_core/blockchain.h, branch v0.13.0.2Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.13.0.22018-10-08T19:42:38ZRevert "Merge pull request #4472"2018-10-08T19:42:38ZRiccardo Spagniric@spagni.net2018-10-08T19:42:38Zurn:sha1:f5df0e272e0c0b513c6e24425e169683ad00d55c
This reverts commit b26ab0b5803af4ffe23de11a45e43877301a4902.
Merge pull request #44722018-10-06T09:15:43ZRiccardo Spagniric@spagni.net2018-10-05T21:13:31Zurn:sha1:b26ab0b5803af4ffe23de11a45e43877301a4902
02d3ef7b blocks: use auto-generated .c files instead of 'LD -r -b binary' (xiphon)
add --block-notify to monerod and --tx-notify to monero-wallet-{cli,rpc}2018-09-29T08:44:18Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-09-03T14:19:15Zurn:sha1:734030046055f521a73e59b50fa2a16f48e34c8d
Those take a command line of the form "A [B]", with A being the
name (and optional path, if not in the caller's CWD, but fully
qualified path is recommended, avoids possible security issues)
to a program, and optional arguments. Any occurence of the two
character string "%s" will be replaced by the hash of the block
or transaction which triggered the notification.
Tokenization is barebones. If you want things like pipes, calls
to paths with spaces, etc, then use a script (though exec time
will suffer).
block-notify is called when a new block is added onto the chain.
tx-notify is called when a new transaction happens with the
wallet as source and/or destination.
It is the notification program's responsibility to determine what
to do in those cases.
Note that this is asynchronous, so it is very possible that:
- the notification programs will be run out of order
- several events happen before the notification for the first one
A Windows port would be nice if someone wants to make one.
remove obsolete daemon selection of fake outs and old tx construction2018-09-14T10:51:45Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-08-13T16:18:32Zurn:sha1:be001326d1baac0b00d79d2d0a7f42662dc1be1fv8: per byte fee, pad bulletproofs, fixed 11 ring size2018-09-11T13:38:07Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-07-18T21:24:53Zurn:sha1:5ffb2ff9b7c301eda5811a939c705f26627c4735Merge pull request #42042018-08-23T01:43:51Zluigi1111luigi1111w@gmail.com2018-08-23T01:43:51Zurn:sha1:4a4ea78ecd753e1ab6be7309ab549417d8d84d6d
b278b83 core: sync database based on bytes added, not blocks added (moneromooo-monero)
core: cache block template where possible2018-08-16T12:44:33Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2016-04-17T10:04:01Zurn:sha1:82d1b74500aa7ffab47f428f9ca26bb43cc2d8af
This avoids constant rechecking of the same things each time
a miner asks for the block template. The tx pool maintains
a cookie to allow users to detect when the pool state changed,
which means the block template needs rebuilding.
core: sync database based on bytes added, not blocks added2018-08-12T16:13:46Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-08-01T10:09:35Zurn:sha1:b278b83860da5eaaa122c219ad8c63f641e41cd3
Blocks have a very wide range, whereas actual size is the relevant
quantity to consider when syncing
Merge pull request #39732018-07-19T18:37:10Zluigi1111luigi1111w@gmail.com2018-07-19T18:37:10Zurn:sha1:d518dae4bf094de36bdf433d2f77f084c6c00162
50af357 alt_chain_info can now give more info about a particular alt chain (moneromooo-monero)
Merge pull request #38542018-07-19T18:35:25Zluigi1111luigi1111w@gmail.com2018-07-19T18:35:25Zurn:sha1:025187e6c9206fc970b66f7459919ce0131fc612
149da42 db_lmdb: enable batch transactions by default (stoffu)
34cb6b4 add --regtest and --fixed-difficulty for regression testing (vicsn)
9e1403e update get_info RPC and bump RPC version (vicsn)
207b66e first new functional tests (vicsn)