Skip to content

Aeon notify#152

Merged
aeonix merged 15 commits intoaeonix:masterfrom
stoffu:aeon-notify
Nov 2, 2019
Merged

Aeon notify#152
aeonix merged 15 commits intoaeonix:masterfrom
stoffu:aeon-notify

Conversation

@stoffu
Copy link
Copy Markdown

@stoffu stoffu commented Oct 9, 2019

monero-project#4333
monero-project#4479
monero-project#4481
monero-project#4408
monero-project#4960
monero-project#5069
monero-project#5053
monero-project#5128

This should be useful for quickly noticing double spend attacks if they ever occur after the fork...

@stoffu stoffu force-pushed the aeon-notify branch 3 times, most recently from 1386ea2 to 34fac99 Compare October 9, 2019 09:49
moneromooo-monero and others added 15 commits October 9, 2019 18:57
…pc} /monero#4333

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.
…/monero#4408

The warning threshold is set to allow a false positive every
ten days on average.
These aren't processed as a shell does, so this may surprise users
This will trigger if a reorg is seen. This may be used to do things
like stop automated withdrawals on large reorgs.

%s is replaced by the height at the split point
%h is replaced by the height of the new chain
%n is replaced by the number of new blocks after the reorg
This runs a command whenever the block rate deviates too much
from the expectation
The 10 minute one will never trigger for 0 blocks, as it's still
fairly likely to happen even without the actual hash rate changing
much, so we add a 20 minute window, where it will (for 0 blocks)
and a one hour window.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants