Content
@
0 reply
0 recast
0 reaction
androidsixteen
@androidsixteen.eth
Reading the Snapchain doc: https://warpcast.notion.site/Snapchain-Public-0e6b7e51faf74be1846803cb74493886 Going to cast all my stupid questions in this thread as they come up 🧵👇
14 replies
10 recasts
38 reactions
androidsixteen
@androidsixteen.eth
> Proof of Stake — Another approach is to follow Ethereum’s staking model. Anyone can run a Hub by staking ETH on a contract I think PoA would be better than this — this turns validator elections into an ETH bridging / event messaging problem, which is arguably worse
3 replies
0 recast
4 reactions
kia
@kia.eth
PoA is awfully prone to censorship
1 reply
0 recast
0 reaction
androidsixteen
@androidsixteen.eth
Give examples where the validator set is a decent size (10+) and are controlled by reasonably distinct entities?
2 replies
0 recast
0 reaction
kia
@kia.eth
your argument being that you can't just have stake to write and would need to have consensus between all write hubs to publish a block. thus, system is still prone censorship by whoever has more ETH?
1 reply
0 recast
0 reaction
androidsixteen
@androidsixteen.eth
No, I'm just saying PoS using ETH in a system where ETH is not the native asset forces you to use a bridge, and now we're back at square one re: who validates the bridged events and/or assets
1 reply
0 recast
0 reaction
kia
@kia.eth
why do you need a bridge? and where is this a bridge to? why can't staking just be done on OP or L1 and hubs rub those nodes to verify?
1 reply
0 recast
0 reaction
