Holesky Safe - 2025Q2+July Budget Provision - Support & Maintenance / Project closure

Community Grants / Initiatives
1

Hello, dear Lido community! This is Ivan from Protofire team.
As you may know, the Lido teams are winding down all Safe-related operations on the Holesky network and transitioning to the recently launched Hoodi Safe.

With that in mind, we’re planning to sunset Holesky Safe and would like to request a final retrospective payment for this project.

Our team has been actively supporting Holesky Safe during that timeframe, focusing on maintaining its stability, security, performing all necessary updates and resolving issues.

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

  • [Update] Roll out Holesky Safe update as part of Roll Out #15
  • [Update] Remove the Safe Tx Service Status app from PRD
  • [Update] Resize the network’s logo in mobile view in the Connect Wallet view
  • [Update] Remove the “Push notifications settings” option
  • [Update] Display a banner about the sunset of the Holesky Safe
  • [Issue] Resolve indexing progress stuck at 0 blocks per minute
  • [Issue] Investigate and fix transactions stuck on the signing step when using WalletConnect
  • [Issue] Fix the Sentry bug: “Error forwarding request due to no free connections left”
  • [Update] Support the migration process from Holesky to Hoodi
  • [Update] Create monitoring alerts for PostgreSQL
  • [Update] Create monitoring alerts for Kubernetes (K8s)
  • [Update] Create monitoring alerts for Redis
  • [Update] Create monitoring alerts for RabbitMQ
  • [Update] Implement DevOps security measures
  • [Feature] Upgrade Safe contracts to version 1.4.1-3
  • [Update] Update Transaction Services to the latest version
  • [Update] Optimize TxService memory consumption
  • [Update] Tune PostgreSQL, Redis, and RabbitMQ parameters for better performance
  • [Update] Fix issues with alerts and monitoring systems
  • [Issue] Resolve issues related to certificates auto-renewal
  • [Issue] Investigate and resolve high RAM utilization issues
  • [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] Conduct risk management analysis for infrastructure and security
  • [Update] Implement security measures for AWS environments

In line with the original proposal, we are now requesting a budget to cover the expenses incurred from April to July inclusive (4 months).

Budget Request: $8,000 in DAI
Purpose: To cover infrastructure costs and compensate the Protofire team for providing support services from April to July inclusive (4 months).
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