The post Shiba Inu Dev Uncovers LEASH Token Supply Backdoor appeared on BitcoinEthereumNews.com.

Top developer Kaal Dhairya exposes how LEASH supply secretly increased 10%. Pre-authorized contracts bypassed renounced ownership to trigger a rebase event. Community offered a choice between negotiation attempts or a complete v2 rebuild. Shiba Inu’s top developer, Kaal Dhairya, has broken the silence on the mysterious LEASH token supply increase that happened on August 11, 2025. In a detailed disclosure, Dhairya explained how the token’s supply jumped from 107,646 to 118,411 tokens despite years of messaging about fixed supply and disabled rebasing capabilities. The developer revealed that a hidden rebase pathway remained functional even after ownership renouncement across the contract system. While the setup appeared decentralized with owner addresses showing zero status, pre-authorized orchestrator contracts retained the ability to trigger supply changes through backdoor mechanisms. Shiba Inu Developer Exposes Contract Architecture Flaws Dhairya’s explanation mentioned how the LEASH token contract inherited elastic-supply logic from earlier development phases, maintaining connections to a monetary policy system that could accept rebase commands. The policy contract only responded to pre-whitelisted orchestrator addresses that were configured before ownership renouncement occurred. The technical setup created a deceptive appearance of trustlessness while preserving functional control over supply adjustments. When developers publicly claimed keys were “burned” and rebasing was “permanently disabled,” the contract architecture told a different story through its preserved authorization pathways. The rebase mechanism proportionally adjusts all holder balances when activated, theoretically maintaining percentage ownership while changing absolute token counts. This affects market calculations, explorer data, liquidity pool mathematics, and integration systems built on fixed-supply assumptions. Dhairya presented the LEASH DAO with two distinct paths forward following the supply revelation. The first option involves attempting negotiations with the original developer to secure public commitments against future rebase triggers or to permanently disable remaining control pathways. The developer acknowledged that previous negotiation efforts had failed, including attempts…

---

Filed under: News - @ August 12, 2025 9:25 pm