At ACI, we acknowledge that Aave Labs bypassed the established workflow and BD pipeline for the MegaETH deployment.
We also acknowledge the earlier precedent of bypassing Skywards by escalating a slightly non-compliant Snapshot vote for an ARFC.
At this point, it is clear that some Aave Labs contributors are choosing to operate on top of workstreams built and maintained by other service providers rather than coordinating through the shared process and generating net-new BD pipelines. We take note of that reality.
Accordingly, we will adapt.
On MegaETH specifically, ACI will continue to execute its mandate. We will make Skywards services available on demand for any proposal related to this network, regardless of the proposing party. We will support authors with payload preparation, publication of AIPs where relevant, and execution within our service provider scope.
We will make Masiv infrastucture available for any incentives campaign desired on the network.
However, to maintain consistency, efficiency, and to mitigate overlap, we will not allocate BD bandwidth to MegaETH. We will focus our BD efforts on other pipelines where coordination and attribution are aligned with the DAO’s processes. If Aave Labs wants to lead BD for this deployment, they are free to do so, and they should own the outcome end-to-end.
We just want roles to be explicit, so DAO-funded work isn’t duplicated and responsibility is unambiguous.