BLUE
Profile banner
T
toly 🇺🇸
@toly.bsky.social
Wartime OSS maintainer. Co-founder of Solana Labs. Follows, retweets, likes are not endorsements. NFA, mostly technical gibberish. Be kind!
261 followers46 following25 posts
Ttoly.bsky.social

Can blue sky control a session key and sign stuff?

1
Ttoly.bsky.social

This is super cool!

0
Ttoly.bsky.social

A local censorship fault will not be automatically by all the other chains. So it has to be long enough such that all the LPs detect it and exit.

0
Ttoly.bsky.social

Yea. That’s fine. Local amm code takes over the last valid root in exit mode. So all the LPs can exit

1
Ttoly.bsky.social

Nah, you need some timeout. If sequencer posts a different block on every chain, it could double spend and instant exit local coins.

0
Ttoly.bsky.social

I think you can guarantee instant finality by executing locally. But not 100% sure.

1
Ttoly.bsky.social

Sequencer signature must work on all chains, so once you have the data locally, you can always post it to the remote. All you need is a sequence number to prove it signed a different block for the same height.

1
Ttoly.bsky.social

Just a sequence number for each rollup block will work. The nodes can copy from local chain and post it to the remote at any time since the sequencer already signed it locally.

1
Ttoly.bsky.social

Sequencer would have signed conflicting blocks or roots.

1
Ttoly.bsky.social

If the data or roots on any of the chains diverge, that’s a fault and a local implementation takes over the last valid root and everyone exits.

1
Profile banner
T
toly 🇺🇸
@toly.bsky.social
Wartime OSS maintainer. Co-founder of Solana Labs. Follows, retweets, likes are not endorsements. NFA, mostly technical gibberish. Be kind!
261 followers46 following25 posts