Safe deployment on Hoodi

Community Grants / Initiatives
5

Hello, dear Lido community!

Following the deployment of Hoodi Safe and the initial three months of support and maintenance, we are now entering the 3rd and 4th quarters of 2025. During this period, we will continue integrating new features, providing technical support, and, of course, monitoring and optimizing the infrastructure - all while keeping the Hoodi Safe instance as up-to-date and aligned with Safe Global as possible. Accordingly, we would like to request funding for this period in the form of a grant.

–

In Q2 2025, we carried out regular updates, resolved issues, and implemented several new features - all of which have contributed to increased usage and an improved user experience for Hoodi Safe.

Below is a row summary of the key tasks and activities we have completed during this period:

  • [Issue] Investigate and resolve the issue where a duplicate “readonly” account appears after creating a multisig.
  • [Issue] Diagnose and fix the error connecting to the blockchain on both environments.
  • [Issue] Address the client request regarding safe-core-sdk not working with Hoodi.
  • [Issue] Troubleshoot transactions on Hoodi Testnet that are stuck in the Processing state.
  • [Feature] Add the Safe App for Lido Easy Track.
  • [Issue] Investigate and resolve the error occurring during RPC connection attempts.
  • [Issue] Review and resolve the issue report related to Hoodi Safe.
  • [Update] Create monitoring alerts for PostgreSQL.
  • [Update] Create monitoring alerts for Kubernetes (K8s).
  • [Update] Create monitoring alerts for Redis.
  • [Update] Implement security measures for DevOps processes.
  • [Update] Update Transaction Services to the latest version.
  • [Update] Investigate and optimize memory consumption of the TxService.
  • [Update] Tune PostgreSQL, Redis, and RabbitMQ parameters for improved performance.
  • [Issue] Resolve issues related to certificates auto-renewal.
  • [Issue] Analyze and resolve the high RAM utilization issue.
  • [Update] Set up a new UptimeRobot account for monitoring.
  • [Update] Update the external Helm chart.
  • [Update] Update environment variables as required.
  • [Update] Mirror content from the support form to an additional URL.
  • [Issue] Investigate and resolve the status page domain takeover issue.
  • [Issue] Analyze and fix occasional CGW 503 errors.
  • [Update] Implement security measures for AWS environments.
  • [Feature] Integrate the Tenderly tool into the system.
  • [Update] Create monitoring alerts for RabbitMQ.
  • [Update] Fix issues with alerts and monitoring systems.
  • [Update] Conduct risk management analysis for infrastructure and security.

In line with the original proposal, we are looking to secure funding for Q3 and Q4 2025 (6 months at the original monthly fee) to cover team support and maintenance efforts as well as infrastructure costs. We will provide regular updates regarding tasks and issues resolved as usual.

Budget Request: $12,000 in DAI
Purpose: To cover infrastructure costs and compensate the Protofire team for providing support services for 2025Q3 and 2025Q4.
ETH Network Address: 0x63d6287D5b853cCfedbA1247fBEb9a40512F709A

We appreciate the continued support from the Lido ecosystem and look forward to further productive collaboration!

Sincerely,
Ivan Bandaryk,
Field CTO @ Protofire DAO

2 Likes
Lido Ecosystem Grants Organization (LEGO) Reports