Rationale
Aave instances demand have been all time high, after the great success of dedicated instances for liquid staking platforms like Lido and EtherFi, that attracted a new influx of incoming instances like Ethena.
But great things takes a lot of time to materialize. Until a deployment request reaches the ARFC stage it could take some months, making the frequency of production deployments to be low versus what the community expected back in the day.
Recap
Since the last 6 months, Catapulta have been on call to perform 2 production deployments, the latest Lido and EtherFi instances in Ethereum network, and contributed to the Aave DAO deployments codebase:
End of agreement
Due the current frequency of production Aave instance deployments during our 6-month service agreement with the Aave DAO and after talking with @bgdlabs team about deployments coordination, we decided to not pursue a service renewal request for Catapulta to the Aave DAO.
For the current frequency, @bgdlabs can handle all the incoming deployments and they have all the technical know-how to do so.
Have been a honor to participate as a services provider for the Aave DAO, and from Catapulta we are open to renew later in time once the demand ramps up.