smstack.eth pfp

smstack.eth

@sm-stack.base.eth

64 Following
4 Followers
smstack.eth pfp
0 reply
1 recast
1 reaction
smstack.eth pfp
Personally I'm a huge fan of ZK fault proofs, but reducing the challenge period to a few hours seems to be quite dangerous. ZK fault proof reduces the dispute game from ~70 onchain rounds to a single validity proof. With this, the ORU can enhance the capital efficiency and get more resilience to weak censorship attacks. However, if Ethereum gets 51% attacks and validators does not vote to the block with honest challenger tx, the attacker can win and finalize malicious state root, which leads to exploit of bridge funds. The only ways to save ORUs in these attacks is to maintain the challenge period sufficiently long and do social fork of Ethereum L1. If we manage to fork before the malicious state root is finalized, the bridge funds will be safe. So, what is the proper challenge period? One clear thing is, rollup will lose the ability to be recovered from strong censorship attacks if it reduces this to a few hours.
0 reply
0 recast
0 reaction
smstack.eth pfp
0 reply
0 recast
1 reaction
smstack.eth pfp
1 reply
0 recast
1 reaction
smstack.eth pfp
0 reply
0 recast
1 reaction
smstack.eth pfp
0 reply
0 recast
1 reaction
smstack.eth pfp
0 reply
0 recast
0 reaction
smstack.eth pfp
0 reply
1 recast
1 reaction