toly 🇺🇸

GM!

Can blue sky control a session key and sign stuff?

This is super cool!

gm!

we just launched Solarplex live - a real time communities feed that uses @bsky.app as an open protocol.

you create a community, and all of your posts can now be filtered via that.

we're going to be adding a lot more features to this - our plan is to use @bsky.app to power Solarplex's convos!

looks like threads wont actually support activitypub at launch. wonder what their fast follow looks like

https://techcrunch.com/2023/07/05/adam-mosseri-says-metas-threads-app-wont-have-activitypub-support-at-launch/

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

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.

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.

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.

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.

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.

Why not a really dead simple L2 that only runs an amm but it’s an L2 in multiple chains. If it’s sequencer fails to include a tx that’s locally posted, a local implementation of the amm takes over the root in exit mode and local coins can exit.

Issue a da challenge to fund out

gm

👋

👋

What if you need to change gm to GM?

gm

Gm

Gm

Gm

Gm BlueSky