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/🧵

根据VanEck的最新报告，随着矿工“投降”迹象的出现，比特币市场可能正接近短期底部——这一信号曾次预示着之前的触底反弹……

VanEck：比特币可能正在进入短期底部。

根据 CryptoQuant 的最新分析，与全球金融市场中的许多其他资产（尤其是黄金、白银和科技股）相比，比特币明显失去上涨动力。原因在于……

CryptoQuant 指出了比特币为何落后于黄金、白银和科技股的原因。

原创 / Odaily 星球日报（@OdailyChina）
作者 / Wenser（@wenser2010）
作为“加密货币晴雨表”，Strategy 的股价始终牵动市场神经，其表现与现金流稳定性、指数地位等关键因素紧密相连。最新消息显示，12 月 15 日至 21 日，Strategy 通过出售普通股融资 7.48 亿美元，现金储备升至 21.9 亿美元，并已暂停买入比特币；目前公司持有比特币...

MSTR抄底还是观望？你必须了解的Strategy三大关键问题

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