Hourglass overview #59
Conversation
MadelineAu
requested review from
dabit3,
wesfloyd,
bryangreen,
shrimalmadhur,
antojoseph,
NimaVaziri,
scotthconner,
MC1823315,
mmurrs and
non-fungible-nelson
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
||
| ### TaskMailbox | ||
|
|
||
| The `TaskMailbox` is an EigenLayer core contract deployed to Ethereum and each support L2 network, and is responsible for: |
| The `TaskAVSRegistrar` is a per-AVS EigenLayer middleware contract that is responsible for: | ||
|
|
||
| * Handling Operator registration for specific Operator Sets of your AVS. | ||
| * Providing the offchain components with BLS public keys and socket endpoints for the Aggregator and Executor operators. |
There was a problem hiding this comment.
Providing the offchain components with BLS public keys
This piece is no longer accurate. Keys live in the KeyRegistrar core contract now. The rest about the socket endpoints is correct though
| * Providing the offchain components with BLS public keys and socket endpoints for the Aggregator and Executor operators. | ||
|
|
||
| The default `TaskAVSRegistrar` is a copy of the provided contract and works as provided. `TaskAVSRegistrar` can be extended | ||
| to include additional onchain logic for your use case. |
There was a problem hiding this comment.
Technically the TaskAVSRegistrar "is a minimal contract, inheriting the default functionality of the Hourglass TaskAVSRegistrarBase contract, that can be extended to add or modify functionality"
| * Validating the task lifecycle. | ||
| * Creating fee markets for your AVS. | ||
|
|
||
| It's empty by default and works out of the box, but can be extended to include additional onchain validation logic for your AVS. |
There was a problem hiding this comment.
Probably also want to add something like:
Your AVS contract can also implement the
AVSTaskHookif you need direct hook functionality, replacing the defaultAVSTaskHookcontract provided.
| The Aggregator is responsible for: | ||
|
|
||
| * Listening to events from the Mailbox contract on chain for new tasks | ||
| * Discovering Executors by querying the `AVSRegistrar` contract, retrieving their metadata containing a BLS public key and a socket (URL) endpoint that references the Executor's gRPC server. |
There was a problem hiding this comment.
Out of date. Peering is done by interacting with the AVSRegistrar (operator sets for exec/aggregator), AllocationManager (operator set members) and KeyRegistrar (public keys for members)
|
|
||
| ### Task processing in main.go | ||
|
|
||
| `main.go` implements the offchain binary run by Operators running the Hourglass Executor. That is, the core business logic |
There was a problem hiding this comment.
main.gorepresents the entrypoint for the Performer process that is managed and run by Operators running an Hourglass Executor
Added an architecture and implementing with Hourglass overview. The location of these files will need to be moved into the DevKit/Hourglass section once #56 is merged.