memoscan

0xd86c…57a5

All memos sent from and to 0xd86c…57a5.
0x3644f69d…2497sent to0xd86cbc18…57a5·#25,804,132·0xcc5b337c…97b547
Addressed to the party controlling 0xd86cbc1892bfda05f3d7e6c17c71709b6ae957a5 and the funds associated with the ChainConnect.com bridge incident of 26 July 2026. We are writing to you directly because we would prefer to resolve this matter without further escalation. Our proposal is as follows: you may retain 15% of the recovered funds as a whitehat bounty. Please return the remaining 85% to 0x3644F69D24A96BB964267278d29d16da73Cd2497 on Ethereum. Upon receipt of the returned funds, ChainConnect will acknowledge you publicly and in writing as a whitehat, recognise the retained 15% as a bounty for the vulnerability you identified, and will not pursue civil claims or undertake independent identity-attribution efforts in connection with this incident, subject to applicable law and the rights of third parties. If the funds are not returned, ChainConnect will pursue all lawful recovery options available to it, including notifying law-enforcement authorities and engaging specialist blockchain-investigation firms. The relevant addresses have been identified and circulated to exchanges and analytics providers, and tracing efforts are ongoing. We would prefer the first outcome and believe it is the reasonable one for both sides. The decision is yours. Please reply on-chain from 0xd86cbc1892bfda05f3d7e6c17c71709b6ae957a5. We will correspond only with a party that demonstrates control of that address by signing a message. Any offer sent from an address other than 0x3644F69D24A96BB964267278d29d16da73Cd2497 is not authorised by ChainConnect. — ChainConnect, 28 July 2026
0x68d447e2…9b30sent to0xd86cbc18…57a5·#25,653,739·0xf5dc5e59…c2a610
ChainConnect confirms that the controller of 0xd86cbc1892bfda05f3d7e6c17c71709b6ae957a5 has fulfilled the agreed return terms for the ChainConnect bridge incident of 26 July 2026. We confirm receipt of 280 ETH to 0x840B3De19e3FAB72fa9A168bD8Dd71B678c57989 in tx 0xe78bfae09b6b8fab1057f472f605044dea8d066b73e5012837050a5bc6d6eb00. The retained amount is acknowledged as the agreed whitehat bounty. ChainConnect considers its commitments under the agreement fulfilled and the matter resolved with the controller of 0xd86cbc1892bfda05f3d7e6c17c71709b6ae957a5. ChainConnect, 31 July 2026
0x9c961a0d…b1easent to0xd86cbc18…57a5·#25,645,977·0xe8eed8a4…ef8083
Glad you choose to do the needful. Our proposal is as follows: you may retain 15% of the recovered funds as a whitehat bounty. Please return the remaining 85% to 0x9c961a0dDC3dF10456b05EBEc5138737aF28B1eA on Ethereum. Addressed to the party controlling 0xd86cbc1892bfda05f3d7e6c17c71709b6ae957a5 and the funds associated with the ChainConnect.com bridge incident of 26 July 2026. We are writing to you directly because we would prefer to resolve this matter without further escalation. Upon receipt of the returned funds, ChainConnect will acknowledge you publicly and in writing as a whitehat, recognise the retained 15% as a bounty for the vulnerability you identified, and will not pursue civil claims or undertake independent identity-attribution efforts in connection with this incident, subject to applicable law and the rights of third parties. If the funds are not returned, ChainConnect will pursue all lawful recovery options available to it, including notifying law-enforcement authorities and engaging specialist blockchain-investigation firms. The relevant addresses have been identified and circulated to exchanges and analytics providers, and tracing efforts are ongoing. We would prefer the first outcome and believe it is the reasonable one for both sides. The decision is yours. Please reply on-chain from 0x9c961a0dDC3dF10456b05EBEc5138737aF28B1eA. We will correspond only with a party that demonstrates control of that address by signing a message. Any offer sent from an address other than 0x9c961a0dDC3dF10456b05EBEc5138737aF28B1eA is not authorised by ChainConnect. ChainConnect, 29 July 2026
0x9c961a0d…b1easent to0xd86cbc18…57a5·#25,645,949·0xa6df21e2…d0c85b
Glad you choose to do the needful. Our proposal is as follows: you may retain 15% of the recovered funds as a whitehat bounty. Please return the remaining 85% to 0x9c961a0dDC3dF10456b05EBEc5138737aF28B1eA on Ethereum. Addressed to the party controlling 0xd86cbc1892bfda05f3d7e6c17c71709b6ae957a5 and the funds associated with the ChainConnect.com bridge incident of 26 July 2026. We are writing to you directly because we would prefer to resolve this matter without further escalation. Upon receipt of the returned funds, ChainConnect will acknowledge you publicly and in writing as a whitehat, recognise the retained 15% as a bounty for the vulnerability you identified, and will not pursue civil claims or undertake independent identity-attribution efforts in connection with this incident, subject to applicable law and the rights of third parties. If the funds are not returned, ChainConnect will pursue all lawful recovery options available to it, including notifying law-enforcement authorities and engaging specialist blockchain-investigation firms. The relevant addresses have been identified and circulated to exchanges and analytics providers, and tracing efforts are ongoing. We would prefer the first outcome and believe it is the reasonable one for both sides. The decision is yours. Please reply on-chain from 0x9c961a0dDC3dF10456b05EBEc5138737aF28B1eA. We will correspond only with a party that demonstrates control of that address by signing a message. Any offer sent from an address other than 0x9c961a0dDC3dF10456b05EBEc5138737aF28B1eA is not authorised by ChainConnect. ChainConnect, 29 July 2026
0x68d447e2…9b30sent to0xd86cbc18…57a5·#25,630,567·0xbfb0873f…9701b1
Addressed to the party controlling 0xd86cbc1892bfda05f3d7e6c17c71709b6ae957a5 and the funds associated with the ChainConnect.com bridge incident of 26 July 2026. We are writing to you directly because we would prefer to resolve this matter without further escalation. Our proposal is as follows: you may retain 15% of the recovered funds as a whitehat bounty. Please return the remaining 85% to 0x840B3De19e3FAB72fa9A168bD8Dd71B678c57989 on Ethereum. Upon receipt of the returned funds, ChainConnect will acknowledge you publicly and in writing as a whitehat, recognise the retained 15% as a bounty for the vulnerability you identified, and will not pursue civil claims or undertake independent identity-attribution efforts in connection with this incident, subject to applicable law and the rights of third parties. If the funds are not returned, ChainConnect will pursue all lawful recovery options available to it, including notifying law-enforcement authorities and engaging specialist blockchain-investigation firms. The relevant addresses have been identified and circulated to exchanges and analytics providers, and tracing efforts are ongoing. We would prefer the first outcome and believe it is the reasonable one for both sides. The decision is yours. Please reply on-chain from 0xd86cbc1892bfda05f3d7e6c17c71709b6ae957a5. We will correspond only with a party that demonstrates control of that address by signing a message. Any offer sent from an address other than 0x68d447e2a4c6e7c1945725939a0cbcb4a67f9b30 is not authorised by ChainConnect. Sender  0x68d447e2a4c6e7c1945725939a0cbcb4a67f9b30, the bridge deployer signatory.  ChainConnect, 28 July 2026