One of my favorite #ETHDenver projects: frontrun malicious txs being sent from your account.
While dealing with phishers & again after our CryptoKitty rescue mission (link.medium.com/O2jFvLOca4) I wondered if this was possible. Txpool(s) are tricky but, yup, it's possible.
While dealing with phishers & again after our CryptoKitty rescue mission (link.medium.com/O2jFvLOca4) I wondered if this was possible. Txpool(s) are tricky but, yup, it's possible.
Scaling this service for mass use would be difficult, and is much better suited for large accounts with few transactions: cold storage, treasuries, etc. where you can customize based on end-user or include in a larger enterprise-type security/consulting offering.
For example, I know @Corpetty monitors contracts & asset movements in order to know as soon as possible if something is compromised or funky to quickly mitigate further loss after a bad thing happened.
This tool would also allow for a chance to *prevent* the initial loss.
This tool would also allow for a chance to *prevent* the initial loss.
One thing that changed (I think) between now & peak 2017 when I first thought of this is that @blocknative has been building crazy infra that captures txpools. This didn't exist in 2017 and if we had set it up then, it likely would only catch malicious txs thru our own node(s).
The reason txpools are funky is that there isn't a single txpool. Each node on the network has their own personal pool including txs sent thru that node & received from peers. This is how txs propagate.
To see all txs broadcasted instantly, you have to peer with ALL, instantly:
To see all txs broadcasted instantly, you have to peer with ALL, instantly:
