memoscan
← all memos

Memo 0x24849b40…bb6912 on Ethereum

Do you mean that the multi-sig wallet 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f, controlled by 6 out of 11 Externally Owned Accounts (EOAs), is governed by DAO voting? Could you please explain how this works? I haven't heard how a multi-sig wallet can execute a proposal without signatures from the EOAs in this case. If you assert that these EOAs do not belong to developers, then let me correct my statement: I can't transfer affected user funds into a multi-sig wallet controlled by 6 out of 11 unknown entities without even a compensation proposal. Regarding the charges, the Balancer team should take full responsibility for the loss suffered by users due to the buggy code you deployed and the unqualified auditing firms you hired. The first exploit transaction occurred on August 27, 2023, at 07:52:23 UTC, and the exploit method was exposed thereafter. However, you took no action to rescue the funds, not even by copycatting, allowing the exploit to continue for several days until September 2, 2023. I have already presented my proposal and agreed to transfer affected funds to a multi-sig wallet owned together by your team. All the left I am requesting is a reasonable compensation proposal, which you seem unwilling to provide. I am curious, even if I were to transfer the funds to your 6 out of 11 multi-sig wallet now, without a compensation plan, what would you intend to do with them? If you insist on blustering via on-chain message instead of creating a multi-sig wallet and working on a compensation plan, I am prepared for your legal action, and I am ready to meet you in court. However, you shall find yourself in the defendant's seat also.