Safe deployment on Hoodi

Community Grants / Initiatives
1

Dear Lido Community,

My name is Ivan Bandaryk, I’m field CTO at Protofire DAO.

As part of our ongoing plan to support Lido protocol, we are proposing the deployment of a Safe Multisig wallet on the emerging Ethereum testnet called “Hoodi.” This will allow for a smooth transition of all Lido testnet-related operations and functionality from Holesky, which is expected to wind down soon.

With a proven track record of deploying Safe on more than 60 networks over the past 3.5 years, and specifically supporting Safe on Holesky for Lido over the past 1.5 years, we are confident in our ability to deliver a high-quality, reliable deployment and ongoing maintenance of Safe on Hoodi. Our approach ensures comprehensive support for the Lido ecosystem and community while maintaining a reasonable budget and financial load.

Scope of Work

The project consists of two main components:

  • Deployment:
    We will deploy the latest canonical version of Safe Multisig using the official Safe GitHub repositories.
  • Support & Maintenance:
    This includes code updates (Safe components), meaningful integrations (extra Wallets support, Safe Apps), infrastructure monitoring and optimization, as well as user support. All infrastructure costs are included.

Timeline

  • Deployment:
    Estimated duration: ~3 days, including testing.
    Target go-live for Hoodi Safe: March 24.
  • Ongoing Support & Maintenance:
    Begins immediately after deployment is completed.

Budget Request

Based on our experience supporting Holesky Safe, we propose the following financial structure:

  • $10,000 upfront for Deployment
    (Reduced from $15,000 in recognition of our long-term collaboration and deployment optimization)
  • $6,000 upfront for 3 months of Support
    Approximately 50% will cover infrastructure hosting and maintenance costs. The remaining funds will be used for user support, code updates, and integrations.

Payments can be made in DAI, USDC, or USDT.
ETH address: 0x63d6287D5b853cCfedbA1247fBEb9a40512F709A

We appreciate your consideration and look forward to the opportunity to contribute to the continued growth and success of the Lido ecosystem.

Sincerely,
Protofire DAO Team

3 Likes
LEGO Q1 2025 Report
Holesky Safe - 2025Q2+July Budget Provision - Support & Maintenance / Project closure
Lido Ecosystem Grants Organization (LEGO) Reports
2

Hello Ivan. I would like to extend thanks to Protofire for the great work they’ve done maintaining Safe on Holesky and the quick turnaround to also be able deploy it to, and maintain on, Hoodi. LEGO Council has agreed to proceed with the above-requested grant.

3

Hey Izzy, thanks for your kind words! We’re also happy to be working with your team and the LIDO community as a whole. Looking forward to a productive and long-term collaboration.

1 Like
4

Hey Ivan, the grant has been disbursed! Thank you for your assistance in deploying this vital community infrastructure.

2 Likes
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
6

Hi @Ivan_Protofire, LEGO council supports this grant, aiming to disburse it next week!

3 Likes
7

GM @Ivan_Protofire the grant is disbursed!

1 Like
8

Thank you @Alex_L for the update, and thanks to the whole Lido community for your trust! Looking forward to continuing our productive collaboration.

1 Like
9

Hello, dear Lido community!

After 9 months of Protofire Safe support on Hoodi we are entering into new support quarters: Q1 and Q2 of 2026.

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.

Along with the grant request, we are sharing the tasks and updates done during Q3 & Q4 2025 support period. Those include regular updates, resolved issues, and new feature implementations, all of which have contributed to increased utilization and an improved user experience for Safe on Hoodi.

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

  • [Update] Add the network to the Safe Tx Service Status App

  • [Issue] Verify smart contracts on the Hoodi testnet

  • [Issue] Provide user instructions for transaction creation using DELEGATE_CALL

  • [Issue] Analyze the low message size limit in Hoodi Safe

  • [Issue] Investigate and fix inability to create a multi-chain account

  • [Feature] Enable multi-chain Safe creation

  • [Issue] Investigate and fix why the enabled Spending Limit is being ignored

  • [Update] Rollout 16 (UI): Migrate Shared Protofire UI to the shared template branch

  • [Update] Rollout 16 (BE): Deploy Protofire Shared Safe backend

  • [Issue] Investigate why newly created Safes use contract version 1.3.0 instead of 1.4.1

  • [Update] Update the logo on the “Safe Creation” page

  • [Update] Rollout 16: Apply Protofire Shared Safe updates

  • [Update] Deploy a Safe Decoder Service instance

  • [Update] Migrate Staging UI to the shared branch

  • [Update] Migrate Production UI to the shared branch

  • [Issue] Investigate Delegate module issues on Protofire Safe (user support)

  • [Update] Create a script to identify Safe Client Gateways with errors

  • [Update] Adjust AWS RabbitMQ CloudWatch alarms

  • [Update] Harden access to Tenderly public routes

  • [Update] Switch the servers cluster to use object storage

  • [Feature] Enable admin-whitelisted access for Safe services

  • [Update] Update environment variables for the Transaction Builder

  • [Update] Disable Nginx version exposure

  • [Issue] Analyze compromised NPM packages

  • [Issue] Check alerts related to txServices indexing

In line with the original proposal, we are looking to secure funding for Q1 and Q2 2026 (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 2026Q1 and 2026Q2.
ETH Network Address: 0xA119E648900d9be01B52282536EEE021F9B370A0 (updated upon request from LEGO).

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
10

GM @Ivan_Protofire the grant was sent, thank you for your continued support and maintenance of Safe on Hoodi!

1 Like
11

Hoodi Safe - 2026Q3&Q4 Budget Provision - Support & Maintenance

Hello, dear Lido community!

After 15 months of Protofire Safe support on Hoodi we are entering into new support quarters: Q3 and Q4 of 2026.

As you may know, Safe has introduced licensing changes for third-party hosted instances (moved their backend repos from an MIT license to a Functional Source License), thus the current Hoodi Safe has the latest MIT version deployed. We are formalizing the licensing agreement with the Safe team and are already scheduling a full-scale rollout of the latest version of Safe components (including FSL ones).

During the new support period, we will be 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.

Along with the grant request, we are sharing the tasks and updates done during Q1 & Q2 2026 support period. Those include regular updates, resolved issues, and new feature implementations, all of which have contributed to increased utilization and an improved user experience for Safe on Hoodi.

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

  • [Feature] Integrate Safe App - CSV Airdrop v2.4.0

  • [Issue] BUG: /v1/spaces returns 403 instead of 401 for unauthenticated requests (GSD-13126)

  • [Feature] Integrate feature - Safe Spaces

  • [Feature] Integrate Feature - Nested Safes

  • [Feature] Integrate Safe App - Drain Account

  • [Feature] Add Networks to the Safe Utils

  • [Issue] Safe - Hoodi Safe accounts not indexing after activation (Lido)

  • [Issue] [Safe | Lido] Hoodi - Root cause analysis: indexing failures (RPC inconsistent log ranges)

  • [Issue] [Safe | Lido] Hoodi — Safe accounts not indexing - recurrence 2026-05-07

  • [Feature] Deploy Safe v1.5.0 to Ethereum Hoodi Testnet

  • [Issue] Protofire Safe: Fix poor visibility on lite theme on Welcome Page

  • [Feature] Zerion Integration - Balances, Portfolio & DeFi Positions

  • [Issue] Safe list is not displayed on Accounts page after connecting via MetaMask

  • [Update] Upgrade the version of the txBuilder safe app

  • [Update] Monitoring - adjust configurations

  • [Update] [K8s] Optimize Redis/RabbitMQ deployment and storage setup

  • [Update] Safe Config Service - Roll Out 17

  • [Update] Safe Events Service - Roll Out 17

  • [Update] Safe Client Gateway - Roll Out 17

  • [Update] Safe Tx Service - Roll Out 17

  • [Update] Safe Decoder Service - Roll Out 17

  • [Feature] Automatically pull chain information from the Safe Registry

  • [Feature] Add a search option to the network dropdown selector

  • [Update] Safe UI - Roll Out 17

  • [Feature] Research Safe Spaces Feature

  • [Feature] Research Safe Shield component

  • [Update] Prepare a list of RPC nodes for HAProxy for all networks

  • [Issue] Analyze compromised supply chain

  • [Feature] Adapt custom APIs for tx builder app

  • [Issue] [K8s Staging] Volume pool fault on Hetzner

  • [Update] [K8s] Update ingress configuration related to cert-manager/ACME

  • [Issue] Security analysis of UI patches

  • [Update] Hetzner - planned maintenance

  • [Update] [K8s] Update hcloud-cloud-controller-manager

  • [Issue] “Copy Fail” vulnerability - mitigation

  • [Update] Change UI’s CodeBuild compute type

  • [Update] Update Nginx version to 1.31

  • [Issue] Analyse compromised supply-chain attack

  • [Update] [K8s] TLS certificates issuing - refactor the approach

  • [Feature] Add necessary environment variables for SPACES on all CGW

  • [Update] Safe Update Analysis - Roll Out #18

  • [Update] Set up upgraded components for the Roll out 18 on DEV environment

  • [Update] Update environment variables for backend components

  • [Update] Make small balances visible by default on Safe UI

  • [Update] [K8s] Configure etcd backup

  • [Update] Deploy separate instance of Safe Decoder service

  • [Feature] Make Zodiac Safe apps load chain info from safe registry

  • [Update] Update config service import_default_config

  • [Issue] Safe Decoder stores NULL abis

  • [Issue] Investigate and Hide Spam Tokens in Safe Accounts

In line with the original proposal, we are looking to secure funding for Q3 and Q4 2026 (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 2026Q3 and 2026Q4.
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

1 Like