GregTheGreek
@gregthegreek.eth
Question for the community When hacks occur, we typically see three outcomes post hack: 1. Funds sent to exchange 2. Funds sent to mixer 3. Funds sent cross chain Regarding point 3, most of these transfers are not TRULY permissionless. Usually a relay or solver is involved in providing the transfer. If we were to SOCIALLY (not protocol level) coordinate to “slow down” the attack surface, would the community like that? Examples: 1. once a “confirmed” (needs definition) hack occurs we start slowing operations (similar to a cex). Instead of a 5s transfer, maybe 5-10minutes. 2. addresses begin getting blocked (eg we do not facilitate the transfer) 3. (controversial) we facilitate it, but transfer funds to an escrow “rescue” contract where a multisig of security experts (SEAL, etc..) can process it or return to affected team. Chase profits, or potentially help insulate “confirmed” attacks that affect retail users. 🤷♂️ https://frame.weponder.io/api/polls/29516
1 reply
1 recast
4 reactions
shazow
@shazow.eth
i dunno about redirecting (could be convinced if it's not a critical piece of infrastructure and can be done without negative side effects), but slowing down arbitrary components is asking for a cascade of negative side effects. imagine someone is trying to move funds across last second to avoid liquidation (can imagine this being done increasingly just-in-time with intents and robust bridging).
0 reply
0 recast
1 reaction
