Impromptu technical AMA on history expiry

1

The Graph

#Software Engineering #Tech #Text Editors 72 social mentions

2

Txto

Once the rollup client has all the historical data it needs and authenticated it, it should ingest it into it's own data structures. This can be tricky if the rollup is mostly driven by logs. I think it is preferable to consider a rollup update potentially valid iff it originates from an EOA. This means the rollup manger contract will be statically visible from the block body (in the `tx.to` field) and the rollup client won't need to do any EVM processing. That should be enough to bootstrap a rollup client! Realistically, they're going to faces similar issues as L1 in the near future and will want to implmement a similar snap-syncing mechanism and history expiry.

#Graphic Design Software #Events #iPhone 1 social mentions