While using Optics V1, I made a mistake during the bridging process on Celoscan by entering the wrong format in the address parameter. Unfortunately, this could result in the funds becoming unrecoverable.
While searching for a solution, I discovered that the transaction might be reversible using Optics Recovery Mode. This process involves the community Optics v2 Multisig, which has access to the Recovery Manager as detailed in this thread: Optics Recovery Mode. The Multisig signers are listed here: Optics Recovery Signers.
As the funds represent a significant amount to me, I kindly ask for your support in recovering them. Therefore I propose putting the bridge in Recovery Mode to reverse the transaction.
Any guidance or assistance would be greatly appreciated.
Can you share more details about the transaction that you are referring to so I can forward your request to the Optics multisig owners? Which chains were you sending between and from what address. Also, what was the mistake?
Thanks for your response.
Would it be possible for me to disclose this in private (for certain reasons)?
Iāve sent you a friend request from ātqtā / āTQT#7935ā on Discord.
I checked with ChatGPT and it said the following things must be done for the reversal (if this is correct). Hopefully thereās still enough signers active
The only tool that can stop it
Contract Critical function Who can call it GovernanceRouter (0xdfb2a95900d6b7c8aa95f2e46563a5fcfb5505a1) initiateRecoveryTimelock() ā wait 6 h ā setRouterLocal(6648936, 0x0000000000000000000000000000000000000000) RecoveryManager multisig (4 / 7 signers) Ethereum (ETH) Blockchain Explorer
Step 1 ā Trigger recovery mode. Multisig calls initiateRecoveryTimelock(). A 6-hour clock starts. Step 2 ā Disable the Replica. After the timelock, they call setRouterLocal(, 0x0). That cuts the wire: every queued message (including yours) now reverts instead of executing. How the actual āreversalā happens Stopping the message just freezes it.
To get your tokens back the multisig has to manually unlock the assets that are still sitting in the BridgeRouter on the origin chain:
Verify balance ā your tokens are still on the origin BridgeRouterās balance because the send() call only locked them.
Direct transfer / bridge-back ā the multisig can either call the underlying ERC-20ās transfer() from the BridgeRouter to your wallet, or craft a fresh send() that mints the tokens back to you on the origin chain.
Exit recovery ā once the refund is done they can call exitRecovery() to reopen the bridge if they wish.
Please let me know if the rescue is possible, the amount now almost totals 30k which means a lot to me.
If itās not feasible, Iād understand and try to live with it. Atleast I wonāt live with false hope.
Hi @KateNora ,
Due to personal circumstances I would need the stuck tokens by end of the year.
Do you think this is possible?
Iām a bit worried since Iāve asked around but the people I know from the multisig havenāt been aware of anything and also because I havenāt been asked for more details by the team.