like i have to download another chain with global data in order to verify its state. but its way more bigger and faster than base layer, so i can't. lightning for example is a good scaling solution. because i don't require to know ledger state of everyone using lightning. its just a ledger between two parties that know each other (i think new lightning protocols allows more as well). if you scaling solution is just another chain with faster and more data, its not a scaling solution. i still have to download it all to verify it. or trust someone else.

Sidechain shitcoin garbage

What appears on Bitcoin: - A standard Bitcoin transaction BTC sent to a federation-controlled multisig address - Often includes a small metadata commitment (via OP_RETURN) referencing the peg-in claim on Liquid. What it proves: - BTC has been locked on Bitcoin A corresponding amount of L-BTC is issued on Liquid. What is not stored on Bitcoin: - Liquid transaction details - Liquid addresses - Confidential amounts or assets on Liquid Is this okay with you then or no? The issue could be the opreturn for peg-ins, which is typically ~36–40 bytes.

its not

but then again. you need to entire global state. which is not great as well.

I don’t see anything about “snapshots” stored on Bitcoin. Only peg in txs, peg out txs, and only opreturn in peg in. Global state of liquid is NOT store on bitcoin. Not trying to shill liquid btw. Trying to figure out where it fits in this discussion about L2s and data storage.

yeah i mean. i thought maybe it was hashing the state and anchoring it to the base layer. so you can verify the state on bitcoin and replay from there. but even if thats true, thats still a global state. my main issue is having a global, state. bitcoin already has the global state. i dont have to keep track of another. i think this is the most primitive version of what im trying to say: 📝 53cf9dbb…