Skip to content

archiver stores "non-pending" l1 -> L2 forever #691

@LHerskind

Description

@LHerskind

Since it not explicit in #520 that the archiver should also keep a "for-ever" growing set of L1 -> L2 messages that are in the "non-pending" set to make it easy for RPC's to fetch data for consuming messages. Add an explicit store of these messages.

Consider storing a mapping from entryKeys => L1ToL2Message and simply store the entryKeys in the pending set as you can always lookup the data from the ever-growing set.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions