Content pfp
Content
@
0 reply
0 recast
0 reaction

Pawel Pokrywka pfp
Pawel Pokrywka
@pawelpokrywka
Idea: Protecting Your Validator from Attacks During Block Proposal to Prevent MEV Theft Recently, I read a paper on validator deanonymization (linked in the last comment). TL;DR: An attacker could find the IP address used by your validator. Then, when you're about to propose a block with significant MEV (Miner Extractable Value), the attacker can launch a cheap DoS (Denial of Service) attack on your internet connection. You would miss the opportunity to propose a block. The attacker would then DoS the next validator and repeat this until their validator is selected. This would allow them to propose a block, essentially stealing your winning lottery ticket and grabbing all the MEV.
3 replies
0 recast
4 reactions

polymutex pfp
polymutex
@polymutex.eth
Cool idea, but difficult because there is no standardization around APIs for port forwarding by VPN providers. I think the endgame is to run validators over Tor and use a different Tor circuit for attestations vs block proposals. But with the trend of stakers' latency reqs, seems like swimming against the current.
1 reply
0 recast
1 reaction

Pawel Pokrywka pfp
Pawel Pokrywka
@pawelpokrywka
Regarding standarization of port forwarding, I found a nice project called Gluetun. It's a docker image allowing you to connect to any supported public VPN. It updates list of servers and abstracts away all provider-specific details. It allows to setup port forwarding - currently only for 2 providers - but I believe more providers could be added. I believe the DoS issue will vanish with introducing of Secret Leader Election. However, we I'm not aware of any plans to introduce it in Pectra or Fusaka, so it may take some time. https://ethereum.org/en/roadmap/secret-leader-election/ You mentioned Tor, so you may be interested in Nym mixnet. I follow this project for some time. There were some efforts to integrate it with libp2p. I don't know how it helps prevent DoS, probably have the same latency issues you mentioned, but from the privacy perspective seems very cool. https://github.com/ChainSafe/rust-libp2p-nym
0 reply
0 recast
1 reaction