monzero-core.git/src/cryptonote_core/cryptonote_core.cpp, 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.
Merge pull request #43782018-09-21T18:41:53ZRiccardo Spagniric@spagni.net2018-09-21T18:41:53Zurn:sha1:0645dcdbdbdb7497445cae5e4772e5210fe5a1f4
ac934663 rpc: add a "is an update available" flag in get_info (moneromooo-monero)
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:be001326d1baac0b00d79d2d0a7f42662dc1be1frpc: add a "is an update available" flag in get_info2018-09-14T09:28:03Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-06-18T14:31:34Zurn:sha1:ac9346637a353851610f028239b2df7762341d35
Make it easier for a user to be told when to update
v8: per byte fee, pad bulletproofs, fixed 11 ring size2018-09-11T13:38:07Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-07-18T21:24:53Zurn:sha1:5ffb2ff9b7c301eda5811a939c705f26627c4735require canonical multi output bulletproof layout2018-09-11T13:37:39Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-03-31T09:49:53Zurn:sha1:c444b1b22922b423256c6d15887a27e77d060d7fBulletproof aggregated verification and tests2018-09-11T13:37:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-03-30T19:29:42Zurn:sha1:2a8fcb421bc41eb254f95379dd73238915dd509d
Also constrains bulletproofs to simple rct, for simplicity
bulletproofs: add aggregated verification2018-09-11T13:37:32Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2018-02-03T14:36:29Zurn:sha1:bacf0a1e2ff54ef1fc77e3f6ec92e87946084c1a
Ported from sarang's java code