toly 🇺🇸
@toly.bsky.social
Wartime OSS maintainer. Co-founder of Solana Labs. Follows, retweets, likes are not endorsements. NFA, mostly technical gibberish. Be kind!
Can blue sky control a session key and sign stuff?
July 7, 2023 at 5:01 AM
Can blue sky control a session key and sign stuff?
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.
July 2, 2023 at 1:37 PM
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.
Yea. That’s fine. Local amm code takes over the last valid root in exit mode. So all the LPs can exit
July 2, 2023 at 4:10 AM
Yea. That’s fine. Local amm code takes over the last valid root in exit mode. So all the LPs can exit
Nah, you need some timeout. If sequencer posts a different block on every chain, it could double spend and instant exit local coins.
July 2, 2023 at 4:09 AM
Nah, you need some timeout. If sequencer posts a different block on every chain, it could double spend and instant exit local coins.
I think you can guarantee instant finality by executing locally. But not 100% sure.
July 2, 2023 at 4:05 AM
I think you can guarantee instant finality by executing locally. But not 100% sure.
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.
July 2, 2023 at 4:04 AM
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.
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.
July 2, 2023 at 4:03 AM
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.
Sequencer would have signed conflicting blocks or roots.
July 2, 2023 at 3:23 AM
Sequencer would have signed conflicting blocks or roots.
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.
July 2, 2023 at 3:21 AM
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.
Sequencer X posts all the blocks on N chains. If they don’t include the expected txs, there is a local fault, and the local implementation takes over the root and users can exit. If roots diverge, that’s a fault, etc…
July 2, 2023 at 2:36 AM
Sequencer X posts all the blocks on N chains. If they don’t include the expected txs, there is a local fault, and the local implementation takes over the root and users can exit. If roots diverge, that’s a fault, etc…
It would mirror on all N, each can post txs that must be included. If it ever diverges, there is an attributable fault everyone exits from the last valid root.
July 2, 2023 at 2:32 AM
It would mirror on all N, each can post txs that must be included. If it ever diverges, there is an attributable fault everyone exits from the last valid root.
Why does it need 1 layer instead of N? When there is a fault, each layer only cares about its own tokens, all the remote are worthless.
July 2, 2023 at 2:14 AM
Why does it need 1 layer instead of N? When there is a fault, each layer only cares about its own tokens, all the remote are worthless.
It could be used to swap eth to sol, stuff like that.
July 2, 2023 at 1:50 AM
It could be used to swap eth to sol, stuff like that.
Issue a da challenge to fund out
July 2, 2023 at 1:45 AM
Issue a da challenge to fund out
What if you need to change gm to GM?
May 17, 2023 at 3:32 AM
What if you need to change gm to GM?