# Known Bugs ## dMute DAO Bug An initial deployment of the dMute contract on mainnet launch was misconfigured and deployed with a missing argument which prevented mute from redemptions, permanently locking any mute that was deposited in the contract forever. \ \ As a fix, the Mute team minted the locked token amount on L1, burned the same amount of mute tokens from the zkSync L1 Bridge, and redeployed and distributed those mute to the affected addresses on L2, ensuring the total token supply of Mute remained the same. \ \ Amounts burned from L1 bridge and minted/redistributed on L2: **2694479.313675894551572218 Mute**\ \ All users who locked tokens in the linked contract below have been made whole. The total token supply of Mute remains unaffected. \ \ Relevant Links: \ \ [dMute Contract on L2](https://explorer.zksync.io/address/0xd9Ee4c1e04059D4B0dd02b747282511bEE4E5fB5)\ [New minted Mute + existing treasury mute deposited to L2](https://etherscan.io/tx/0xb66d57064311810acf387ce96141ac770c19b7578ce3f9d99f1f375b86df97f0) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.koi.finance/info/known-bugs.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.