Last night, @cumbercapital reached out with a problem: he had accidentally sent $60k USDC on Arbitrum to the address of a token on Base.
Happy to say that today we were able to successfully recover it.
Here's how (rescue repo link at the end)
1/🧵 

Twitter

昨晚，@cumbercapital聯絡我們，提出了一個問題：他不小心在Arbitrum上將6萬美元的USDC傳送到了Base上的一個代幣地址。

很高興地說，今天我們成功地追回了這筆資金。

以下是具體過程（救援倉庫連結在最後）
1/🧵

根據 CryptoQuant 的最新分析，與全球金融市場中的許多其他資產（尤其是黃金、白銀和科技股）相比，比特幣明顯失去上漲動力。原因在於……

CryptoQuant 指出了比特幣為何落後於黃金、白銀和科技股的原因。

原創 / Odaily 星球日報（@OdailyChina）
作者 / Wenser（@wenser2010）
作為“加密貨幣晴雨表”，Strategy 的股價始終牽動市場神經，其表現與現金流穩定性、指數地位等關鍵因素緊密相連。最新消息顯示，12 月 15 日至 21 日，Strategy 通過出售普通股融資 7.48 億美元，現金儲備升至 21.9 億美元，並已暫停買入比特幣；目前公司持有比特幣...

MSTR抄底還是觀望？你必須瞭解的Strategy三大關鍵問題

根據VanEck的最新報告，隨著礦工“投降”跡象的出現，比特幣市場可能正接近短期底部——這一信號曾次預示著之前的觸底反彈……

VanEck：比特幣可能正在進入短期底部。

2/ I went straight to the contract deployment on Base to find out how it was deployed. If deployed via the `CREATE` opcode, then we can deploy a rescue contract on Arbitrum from the same deployer and nonce, and it would end up at the same address.

2/ 我直接去了 Base 上的合約部署頁面，想看看它是怎麼部署的。如果是通過 `CREATE` 操作碼部署的，那麼我們就可以用同一個部署器和 nonce 在Arbitrum上部署一個救援合約，最終它會到達同一個地址。

3/ It was unfortunately created by another contract, which could have meant disaster. Thankfully, that contract was deployed by the same deployer just three transaction prior -- only a slight complication.
And even more thankfully, it was indeed deployed via `CREATE` 

3/ 不幸的是，它是由另一個合約創建的，這可能意味著災難。值得慶幸的是，該合約在三筆交易之前由同一個部署者部署——只是稍微複雜了一點。
更值得慶幸的是，它確實是通過 `CREATE` 部署的。

4/ Just like EOA `CREATE` deployments are deterministic based on nonce, smart contract deployments are as well. Contracts have their own, somewhat invisible nonce specifically used and only incremented when they themselves deploy a new smart contract.

4/ 就像 EOA 的 `CREATE` 部署基於 nonce 確定性一樣，智能合約部署也是如此。合約擁有自己專屬的、幾乎不可見的 nonce，該 nonce 僅在它們自己部署新的智能合約時才會遞增。

5/ In order to conduct a rescue, we simply needed:
- Access to the deployer wallet (0x2CD5)
- Deploy a smart contract factory using the deployer's nonce 2
- Deploy a rescue contract from that factory using the factory's nonce 0
All in all, it looks something like this: 

5/ 為了進行救援，我們只需要：
- 訪問部署者錢包 (0x2CD5)
- 使用部署者的 nonce 2 部署智能合約工廠
- 使用工廠的 nonce 0 從該工廠部署救援合約
總而言之，它看起來像這樣：

6/ The factory and rescue contracts themselves are very simple. Check them out below -
The factory only has one function, which creates a new Rescue contract.
The Rescue contract transfers USDC upon deployment.
There's also a generic rescue in case anything else gets sent in. 

6/ 工廠和救援合同本身非常簡單。請查看以下內容：
該工廠只有一個功能，即創建一個新的救援合約。
救援合同在部署時轉移USDC 。
如果還有其他東西被送進來，還會有一個通用的救援措施。 

7/ Big shout out to @mjayceee for being so responsive and cooperative throughout the process, and getting it all set up and run this morning.
I'm glad we were able to get the funds back and make @cumbercapital whole again. https://twitter.com/2573380344/status/1915848525092688070

7/ 非常感謝@mjayceee在整個過程中的積極響應和合作，今天早上就把一切都安排好了，並順利運行。
很高興我們能夠收回資金，讓@cumbercapital恢復元氣。https://twitter.com/2573380344/status/1915848525092688070

Oh right, repo link: https://github.com/QuitCrypto/Rescue-USDC
And rescue tx: https://arbiscan.io/tx/0x556373755a365c778608ad2464a181b15268995f5e2f7a4e10e9281fa5d1e17b

哦對了，repo 鏈接：https://github.com/QuitCrypto/Rescue-USDC
救援交易：https://arbiscan.io/tx/0x556373755a365c778608ad2464a181b15268995f5e2f7a4e10e9281fa5d1e17b