-
Notifications
You must be signed in to change notification settings - Fork 20
Description
For the purposes of understanding failure modes and for forensics of attack scenarios, we should have a method to capture all arriving transactions and blocks (including the IP address of the sender). Transactions that somehow are not mined and get dropped from the mempool, and blocks that were 'reverted' or become orphans are not captured in the blockchain, but their very presence may be indicative of various failure modes and outright attacks.
So RT tracking those is likely a part of the process of detecting attacks. And having the complete record of what came when, collected on multiple friendly nodes will facilitate forensics.
Separately, should review geographic distribution, resilience and DDoS protection for the active infrastructure of seeds, explorers, pools.
Also interested in scenarios of selfish mining and lazy mining.
https://gist.github.com/shelby3
https://www.ccn.com/japanese-cryptocurrency-monacoin-hit-by-selfish-mining-attack/