<aside>
💡
To offer comments or additions to this tracker, contact Julian Ma ([email protected])
</aside>
Description
This document lists blockers and tracks conversations related to FOCIL. It is meant for researchers interested in contributing to its development.
Current FOCIL Design Parameters
- Commitee-based: 16 committee members create local inclusion lists, which are aggregated into one aggregate inclusion list.
- Size: Each local inclusion list is at most 8 kilobytes each. There could be around 20 average sized transactions in each local inclusion list so around 320 average sized transactions in all local inclusion lists. A block contains around 100-200 transactions.
- Conditional: The aggregate inclusion list does not constrain the beacon block validity if the execution payload is full.
- Spot: The aggregate inclusion list created in slot $n$ constrains the validity of the beacon block in slot $n$.
- Unordered: The aggregate inclusion list does not impose ordering constraints on the execution payload.
- Anywhere-in-block: Transactions from the aggregate inclusion list could be included anywhere in the execution payload.
- Expiring: The aggregate inclusion list created in slot $n$ only constrains the validity of the beacon block in slot $n$ and does not constrain the validity of later beacon blocks.
Resources