forked from oxen-io/oxen-core
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This implements a confirmation mechanism into the pulse quorum to enhance the security of pulse blocks without introducing desyncing of the Oxen chain to achieve consensus. The general design implemented here is explained in the `docs/sent-l2-confirmation/sent-confirmations.md` document (and so see that for details rather than this commit message). Other smaller changes included here that intersect (but aren't directly part of the confirmation mechanism): - Combine the virtually identical `tx_extra_ethereum_new_service_node` and `NewServiceNodeTx` instead a single 'eth::event::NewServiceNode`, and likewise for removal requests and removals. - Update the naming of L2 events to match the more informative names in oxen-io/eth-sn-contracts#58 - Increase L2 refresh times to once per minute. - Remove useless pass-through wrapper functions for txpool operations from blockchain.cpp, and just have tx_pool call directly into the db via blockchain's `db()` reference. - Remove l2 monotonic height checks from consensus consideration; they are dangerous in that a malicious quorum could stall the chain by putting an excessive value that honest nodes couldn't follow. - Various related code cleanup in passing. - renamed some functions such as `get_locked_key_image_unlock_height` that have become rather misnamed by the eth transition. - Simplify tx_pool sorting which was, for completely inexplicable reasons, a pair<tuple<A,B,C>, D> rather than a tuple<A,B,C,D>. - Refomatting
- Loading branch information
Showing
36 changed files
with
1,555 additions
and
1,418 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.