该用户的聊天记录定位。
Already done, and im being told that only Hyperunit can resolve it. They are fast with replying to new tickets by saying "We will have a look into this" just to vanish
Already done, and im being told that only Hyperunit can resolve it. They are fast with replying to new tickets by saying "We will have a look into this" just to vanish
im offering 10 ETH to whoever is first out to help putting up enough pressure by exposing this scam and reverting the funds
im offering 10 ETH to whoever is first out to help putting up enough pressure by exposing this scam and reverting the funds
Need help escalating a Unit recovery case involving 100.56 ETH. About 100.56 ETH has been stranded for ~6 days after a failed Unit deposit. Support has replied a few times but no actual recovery status or tx hash has been provided. Facts: - Original Ethereum tx: 0x8a57c0f0b3dcfec9f9d8a1eef37c1bdad2b2140485c7cd806145938a0c1b00a4 - Unit operation: 0x8a57c0f0b3dcfec9f9d8a1eef37c1bdad2b2140485c7cd806145938a0c1b00a4:34_2_2_0_7 - Unit API/explorer shows this operation as failed with no destinationTxHash. - The ETH is still sitting in the Unit protocol address: 0x1467CFFc154672Eb9b03D6160113D22F38dE84D9 Current balance there is still ~100.567 ETH. We also tried the revert flow, but the revert UI derived `_8`, while the explorer/API only recognizes `_7`; `_8` returns 404. Can someone from Unit/Hyperliquid please escalate this and provide either: 1. the final refund/credit tx hash, 2. the current manual recovery status, 3. or a clear explanation if this is blocked by compliance/Guardian review? This is a substantial amount and generic confirmation-wait responses are not applicable anymore; the original Ethereum tx has far more than the required confirmations. Hyperunit is completely ghosting my tickets...
Need help escalating a Unit recovery case involving 100.56 ETH. About 100.56 ETH has been stranded for ~6 days after a failed Unit deposit. Support has replied a few times but no actual recovery status or tx hash has been provided. Facts: - Original Ethereum tx: 0x8a57c0f0b3dcfec9f9d8a1eef37c1bdad2b2140485c7cd806145938a0c1b00a4 - Unit operation: 0x8a57c0f0b3dcfec9f9d8a1eef37c1bdad2b2140485c7cd806145938a0c1b00a4:34_2_2_0_7 - Unit API/explorer shows this operation as failed with no destinationTxHash. - The ETH is still sitting in the Unit protocol address: 0x1467CFFc154672Eb9b03D6160113D22F38dE84D9 Current balance there is still ~100.567 ETH. We also tried the revert flow, but the revert UI derived `_8`, while the explorer/API only recognizes `_7`; `_8` returns 404. Can someone from Unit/Hyperliquid please escalate this and provide either: 1. the final refund/credit tx hash, 2. the current manual recovery status, 3. or a clear explanation if this is blocked by compliance/Guardian review? This is a substantial amount and generic confirmation-wait responses are not applicable anymore; the original Ethereum tx has far more than the required confirmations. Hyperunit is completely ghosting my tickets...
Need help escalating a Unit recovery case involving 100.56 ETH. About 100.56 ETH has been stranded for ~6 days after a failed Unit deposit. Support has replied a few times but no actual recovery status or tx hash has been provided. Facts: - Original Ethereum tx: 0x8a57c0f0b3dcfec9f9d8a1eef37c1bdad2b2140485c7cd806145938a0c1b00a4 - Unit operation: 0x8a57c0f0b3dcfec9f9d8a1eef37c1bdad2b2140485c7cd806145938a0c1b00a4:34_2_2_0_7 - Unit API/explorer shows this operation as failed with no destinationTxHash. - The ETH is still sitting in the Unit protocol address: 0x1467CFFc154672Eb9b03D6160113D22F38dE84D9 Current balance there is still ~100.567 ETH. We also tried the revert flow, but the revert UI derived `_8`, while the explorer/API only recognizes `_7`; `_8` returns 404. Can someone from Unit/Hyperliquid please escalate this and provide either: 1. the final refund/credit tx hash, 2. the current manual recovery status, 3. or a clear explanation if this is blocked by compliance/Guardian review? This is a substantial amount and generic confirmation-wait responses are not applicable anymore; the original Ethereum tx has far more than the required confirmations.
Need help escalating a Unit recovery case involving 100.56 ETH. About 100.56 ETH has been stranded for ~6 days after a failed Unit deposit. Support has replied a few times but no actual recovery status or tx hash has been provided. Facts: - Original Ethereum tx: 0x8a57c0f0b3dcfec9f9d8a1eef37c1bdad2b2140485c7cd806145938a0c1b00a4 - Unit operation: 0x8a57c0f0b3dcfec9f9d8a1eef37c1bdad2b2140485c7cd806145938a0c1b00a4:34_2_2_0_7 - Unit API/explorer shows this operation as failed with no destinationTxHash. - The ETH is still sitting in the Unit protocol address: 0x1467CFFc154672Eb9b03D6160113D22F38dE84D9 Current balance there is still ~100.567 ETH. We also tried the revert flow, but the revert UI derived `_8`, while the explorer/API only recognizes `_7`; `_8` returns 404. Can someone from Unit/Hyperliquid please escalate this and provide either: 1. the final refund/credit tx hash, 2. the current manual recovery status, 3. or a clear explanation if this is blocked by compliance/Guardian review? This is a substantial amount and generic confirmation-wait responses are not applicable anymore; the original Ethereum tx has far more than the required confirmations.
Hyperliquid