1/ Let's talk about @MagicNewton's DCA. [Conclusion on page 4] There are discussions about zk, TEE, etc., and I was curious about where they are used, so I kept it for now. But I was curious about how it works, so I tried to figure it out. The picture below shows the agent after the DCA is completed: 1. Proof generated 2. Funds moved 3. Proof verified There are three steps like this. [1. Proof generated] When you click on Proof generated, it appears as shown in the picture below. First, there is this data, which will be used later. Here, TEE is used, but you cannot see the original data. [2. Funds moved] When you click on Funds moved, a transaction appears. It's roughly a transaction saying that KAITO was purchased with USDC. This part is a bit complicated. Looking at the input data, executing function 0xd4ed377d, delegatecall runs in a loop.

2/ This is how it proceeds. The first argument is executing the 5000000 transferFrom function of 0xd29447c1. The second argument is also executing the 4918295909822 transferFrom function of 0x0e9d7d22. You can think of it as this process. The internals are quite similar, but the tokens are different. stor_6_0_19, stor_5_0_19 are the differences. The third argument. Now that we have the tokens, we proceed with the swap. USDC → LIFI diamond → swap → cbBTC → WETH → KAITO, this is the process. I keep using lifi, but lifi jumper is originally a project that does cross-chain bridging. The tokens haven't come out yet. It would be nice if it clicks when doing cross-chain. Single-chain swaps are also possible. However, these days, it seems like they are doing it together with magicNewton while attaching intent. lifi attaches intent with @rhinestonewtf, @biconomy, etc. So, this is how the swap is done. I don't know why it changed to cbBTC and then back again during the swap, but it seems like that's how the aggregating works.