Shiba Inu Developer Addresses Wallet Hack and LEASH Supply Concerns

robot
Abstract generation in progress

Shiba Inu developer Kaal Dhairya confirmed the Deployer 1 wallet hack will not impact essential ecosystem systems despite community concerns.

The affected wallet is linked to LEASH, which recently saw a supply increase, prompting discussions on security and possible contract changes.

Proposed solutions for LEASH include negotiations with the original developer or launching LEASH v2 under a new audited non-rebase contract.

Shiba Inu developer Kaal Dhairya has addressed the recent breach involving the Deployer 1 wallet, which was confirmed to be compromised by the account “Woof decentra.” The wallet, identified as 0xA221af4a429b734Abb1CC53Fbd0c1D0Fa47e1494, was reported to have been taken over by attackers who are now using it for unauthorized transactions and token launches. The wallet’s owner urged the community to disregard any recent activity originating from the address.

Following the disclosure, concerns quickly spread within the SHIB community due to the wallet’s assumed association with the LEASH token contract. Dhairya assured users that no essential Shiba Inu ecosystem systems are linked to the compromised wallet. He noted that while the wallet has been and could continue to be used to launch new tokens, there is a risk that these could be fraudulent.

LEASH Token Supply Issue

The situation coincides with a separate development involving the LEASH token. On August 11, the total supply of LEASH increased by nearly ten percent, contradicting the long-held belief that its supply was fixed with rebase functions disabled. Dhairya explained that despite renounced addresses, the capability to adjust supply remained through a chain of connected contracts established by an earlier developer.

To address the LEASH supply issue, Dhairya outlined two potential courses of action. The first option involves attempting negotiations with the original developer, though past efforts in this regard have not yielded results. The alternative is to introduce a LEASH v2 token under a new audited and non-rebase contract. This move would require approval from the Shiba Inu DAO before implementation.

Dhairya’s clarification emphasizes that while the breach of the Deployer 1 wallet does not threaten core systems, caution remains necessary. Tokens launched from the compromised wallet should be approached with skepticism, as they may be part of scam activity. The developer’s remarks aim to inform the community and guide decision-making on both immediate security measures and the future of the LEASH token.

The post Shiba Inu Developer Addresses Wallet Hack and LEASH Supply Concerns appears on Crypto Front News. Visit our website to read more interesting articles about cryptocurrency, blockchain technology, and digital assets.

SHIB-1.26%
LEASH-12.47%
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • 1
  • Repost
  • Share
Comment
0/400
Elchavovip
· 1h ago
What will happen now? I didn't understand anything; it would be better if this team doesn't try to scam.
View OriginalReply0
Trade Crypto Anywhere Anytime
qrCode
Scan to download Gate app
Community
English
  • 简体中文
  • English
  • Tiếng Việt
  • 繁體中文
  • Español
  • Русский
  • Français (Afrique)
  • Português (Portugal)
  • Bahasa Indonesia
  • 日本語
  • بالعربية
  • Українська
  • Português (Brasil)