• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
Hermes ProtocolHermes Protocolby0x0000000000c7BAc9413C74bC84E4D82740B66Ca60xlightyear.eth

[HIP-50] Deprecation of Ulysses Gauges (Batch 3)

Voting ended 3 months agoSucceeded

I. Summary

This proposal recommends the deprecation of Hermes gauges connected to the Ulysses protocol and a subsequent update to the user interface to transition Ulysses integration into a “Withdraw-Only” state.

Since the initial integration of Ulysses, our platform has shipped and matured the Meta-Bridge, a native cross-chain product designed to support modern token standards and protocol-owned bridging flows. As the broader cross-chain market has evolved, the industry has consolidated around sovereign, native standards (such as LayerZero OFTs and xERC20s) that allow protocols to retain full control over their assets, messaging, and upgrade paths.

Because the Meta-Bridge already fulfills this role natively—and is fully supported by our existing UI and incentives framework, continuing to direct emissions and UI surface area toward Ulysses is no longer the most efficient use of protocol resources.

This proposal formalizes a transition toward the Meta-Bridge and other native-standard integrations, ensuring our incentives, product surface, and capital allocation remain aligned with where the market and our partners are actively building.

II. Motivation & Rationale

The Shift Toward Sovereign Infrastructure

When Ulysses was integrated, the cross-chain landscape was fragmented, and liquidity-layer solutions were necessary to bridge gaps between chains. However, the market has matured. Protocols today prioritize ownership and sovereignty. They are increasingly opting for native cross-chain token standards (like OFTs and xERC20s) that allow them to control their own infrastructure rather than delegating custody and bridging logic to a third-party liquidity protocol like Ulysses.

The Meta-Bridge was built specifically to support this shift, enabling protocols to retain end-to-end control while benefiting from a unified, native user experience.

Market Traction & Resource Allocation

Ulysses has not seen the level of sustained adoption necessary to justify ongoing incentives in the current market environment. This outcome reflects evolving industry preferences rather than any deficiency in the underlying technology.

Continuing to allocate Hermes emissions and gauges to Ulysses pools dilutes incentive efficiency and fragments liquidity. By deprecating these gauges, we can concentrate incentives on Meta-Bridge routes and other native-standard integrations that are already seeing active usage and align more closely with partner demand.

Immutability & User Safety

It is important to clarify that this is a UI and Incentive shift, not a shutdown of the underlying blockchain infrastructure.

  • Immutable Contracts: The Ulysses smart contracts are immutable. They cannot be paused, upgraded, or shut down by us or anyone else.
  • Funds are Safe: Users will retain the ability to interact with the smart contracts indefinitely.
  • UI Transition: Upon the passing of this proposal, the official UI will start a transition to simply remove "Deposit" functionality for Ulysses and hide these pools from the active "Earn" sections as they are removed through governance proposals. The "Withdraw" functionality will remain accessible through the UI to facilitate an easy exit for current liquidity providers.

III. Governance Details

Actions

If passed, this proposal will execute the following:

  1. Remove Gauges: Remove gauges for all Ulysses-related pools, stopping all Hermes emissions to these strategies.
  2. UI Update: Update the frontend to "Withdraw Only" mode for Ulysses, guiding users to migrate liquidity to newer, standard-aligned pools.

Timeline

This proposal will follow the standard Hermes Gauge approval governance process:

  1. Temperature Check (3 days): Open forum discussion and early sentiment gathering.
  2. On-Chain Vote (3 days): Formal token-holder vote through the governance module.
  3. Execution Queue (2 days): Mandatory delay before execution to allow final review or veto mechanisms.

IV. Calldata

Target: 0xE64278005e0F00cd6199d000386b018d7C000000 Function: removeGauge(address) Value: 0

Gauge Name: Metis HERA Gauge Address:

  • 0xC797F622CF862903dBb21365a2BeC5e05B96DA3D Calldata:
  • 0x3a045145000000000000000000000000c797f622cf862903dbb21365a2bec5e05b96da3d

Gauge Name: Metis GAMEFI Gauge Address:

  • 0xFE2d7aF372D479C14Dc2aFB81Df44cC48E053848 Calldata:
  • 0x3a045145000000000000000000000000fe2d7af372d479c14dc2afb81df44cc48e053848

Gauge Name: stS / wS Gauge Address:

  • 0xD41985AFb28B18Db794cd5211D8E0A963656F625 Calldata:
  • 0x3a045145000000000000000000000000d41985afb28b18db794cd5211d8e0a963656f625

Gauge Name: arb WETH / swell WETH Gauge Address:

  • 0xe819e212FFA29025c4cFED2d56Fb90ED55F61F43 Calldata:
  • 0x3a045145000000000000000000000000e819e212ffa29025c4cfed2d56fb90ed55f61f43

Gauge Name: arb WETH / op WETH Gauge Address:

  • 0xCa60A020AB9F80f9792D8FC4FdebB49c4B31a26D Calldata:
  • 0x3a045145000000000000000000000000ca60a020ab9f80f9792d8fc4fdebb49c4b31a26d

Gauge Name: stS / BRUSH Gauge Address:

  • 0xbe816aF8EC1CcA9BFB563B0d13294fa6C6d4b7E7 Calldata:
  • 0x3a045145000000000000000000000000be816af8ec1cca9bfb563b0d13294fa6c6d4b7e7

Gauge Name: WBERA / WETH Gauge Address:

  • 0xb943BA7D403d87f4ec16bcCD442F1CaA750A74E4 Calldata:
  • 0x3a045145000000000000000000000000b943ba7d403d87f4ec16bccd442f1caa750a74e4

Gauge Name: stS / Anon Gauge Address:

  • 0xb55339d91E25bC6f48542aeA38Fb91039Ef4F38F Calldata:
  • 0x3a045145000000000000000000000000b55339d91e25bc6f48542aea38fb91039ef4f38f

Gauge Name: arb WETH / base WETH Gauge Address:

  • 0x9901732718F0435CE9c69e5e93109c86804F6F90 Calldata:
  • 0x3a0451450000000000000000000000009901732718f0435ce9c69e5e93109c86804f6f90

Gauge Name: arb WETH / metis WETH Gauge Address:

  • 0x915DB0B25AcC52974DFED9cbC55F043c98Cb0520 Calldata:
  • 0x3a045145000000000000000000000000915db0b25acc52974dfed9cbc55f043c98cb0520

Off-Chain Vote

Yay
8.62M bHermes-Votes100%
Nay
0 bHermes-Votes0%
Quorum:311%
Download mobile app to vote

Discussion

Hermes Protocol[HIP-50] Deprecation of Ulysses Gauges (Batch 3)

Timeline

Dec 26, 2025Proposal created
Dec 26, 2025Proposal vote started
Dec 29, 2025Proposal vote ended