EigenLayer is being actively developed

The core structural design of EigenLayer is not yet finalized and could undergo changes. Despite our efforts to assess any potential conflicts between Omni AVS and both the current and potential future designs of EigenLayer, our ability to conduct a comprehensive integration assessment was limited due to the lack of detailed information about EigenLayer's future design.

Omni Network stated they plan to deploy the protocol in two phases — they will deploy the restaking smart contracts without implementing slashing and reward mechanisms in the first phase, which is the scope of this audit. The second phase will be deployed after the design of EigenLayer is finalized and implemented.

One should note that Slasher, the key component of EigenLayer, is under active development and its design decisions may affect the functionality of Omni AVS. For instance, during our audit, we found that the current design of Slasher, which is deployed on mainnet, is not compatible with the Omni AVS because an operator must opt in to slashing and the AVS should confirm this before accepting their registration. We communicated this information to Omni Network, and we were informed that EigenLayer stated that the future design of Slasher will not involve an opt-in process, unlike the current Slasher contract on mainnet.

Additionally, since the slashing feature is not implemented yet, Omni AVS should enable the allowlist mechanism and collaborate with trusted operators during the initial phase. Omni Network confirmed their intention to do so.

Overall, it is our opinion that Omni Network should actively communicate with the EigenLayer community in order to ensure that the future design changes of EigenLayer do not break the functionality of Omni AVS.