Klerosboard
Case #662
Check the case specific data, case's creator, status and voting history
Evidence Period
1 day 15 hoursVoting Period
3 days 9 hoursAppeal Period
2 days 6 hoursEnforcement
Final DecisionAdd a tag to Address Tags: Does the tag comply with the required criteria?
Check the details on Kleros Court
Creator
3 Jurors
Jury Decision:
No, Don't Add It with 3 votes (100%)
- No, Don't Add It
No, Don't Add It
Vote:
No, Don't Add It
Date:
October 29 2025, 11:31
No, Don't Add It
Vote:
No, Don't Add It
Date:
November 1 2025, 01:03
No, Don't Add It
Vote:
No, Don't Add It
Date:
November 1 2025, 01:03
Evidence
Ambiguous public name tag
According to the "addresses.ts" file in one of Ichi's official GitHub repos here: https://github.com/ichidao/ichi-vaults-sdk/blob/a3e5c2e432cf6f42fd8f69991fe5c4c03557ba2b/src/utils/config/addresses.ts, there are multiple instances of the ICHIVault Deposit Guard contracts, with each instance associated with a DEX and a version number.
The public name tag "ICHIVault Deposit Guard" in this submission is ambiguous, as it doesn't clearly differentiate it from other instances at all, which is a violation of rule #8 in the address tag registry policy, which states that if several instances/versions of the same contract are deployed on the same chain, the public name tags must differentiate them. Instead of the generic "ICHIVault Deposit Guard", the public name tag should have been "ICHIVault Deposit Guard (Hydrex) v2", where "Hydrex" in the parentheses is the DEX the contract address is associated with, and "v2" is its version number.
Submitted by: 0x55DF...2beF in October 27 2025, 19:41