Gao | 郜

Build stuff; ex Googler; alum @Cornell

[Gao | 郜 @gaohan137]

https://t.co/SzjvAFd8Xz

[Gao | 郜 @gaohan137]

TIL @ApertureFinance daily Intents Volume (LPs rebalancing) is greater than @bananagun's swap volume $50M vs. $15M

[Gao | 郜 @gaohan137]

https://t.co/vHRfBJLvcS

[McDavid @RobMcStodda]

To all the @ApertureFinance vaultoors who bore witness to the @terra_money extinction event.. head to our Discord and bind your dusty Terra address to your 0x.

We have something smol in store for you (🔜 like next week) 🙏.

[Gao | 郜 @gaohan137]

@SarahChieng Hey Sarah, we @ApertureFinance is hiring smart contract / backend eng for our Bay Area office. If you know anyone @ MIT, please msg me.

[Paul Graham @paulg]

Visa seemed like a disaster when it was first launched. The kind of people who attack new things today would have been all over it. From the Wikipedia article:

[Gao | 郜 @gaohan137]

@xin__wan Does this mean that on-chain liquidity often would win with smaller orders? (Off-chain liquidity has bigger overall volume, but on-chain liquidity wins more frequent). May be obvious, but just wanted to double check.

[Gao | 郜 @gaohan137]

@sepyke @aadams @Uniswap Something like this?

[Gao | 郜 @gaohan137]

@aadams Got ya! Is the data fetched from subgraph or from an archival node? Initially, when we were fetching directly from nodes, sending multiple PRCs (even with multi-call) is a bit slow. Hence we created an ephemeral contract to batch get everything via contract deployment.

[Gao | 郜 @gaohan137]

Something along the line like: only give Aperture permission to handle 1 position and all the subsequent positions derived from the original position would be much better. This is basically to let child positions to inherit its parent position's permission.

[Gao | 郜 @gaohan137]

@Uniswap's NonfungiblePositionManager (NPM) was innovative at its time. But as we onboard more sophisticated users, it's starting to show problems. Specifically, it is not flexible/declarative enough to grant permissions.

[Gao | 郜 @gaohan137]

NPM at its current state only allows the owner to approve a service provider to use either 1 position or all of its position. There is nothing in between. As we build our liquidity management platform, this inflexibility grants unnecessary trust to us and has security risks.

[Gao | 郜 @gaohan137]

@0x94305 Got ya. I'm also a bit torn on this. Essentially, we need to balance between JIT, passive LP and swappers. And their incentives are not exactly aligned at times. A pure JIT (no MEV) helps swapper but displeases passive LPs. Would be great to devise a robust incentive system.

[Gao | 郜 @gaohan137]

@0x_Osprey Isn't this the same as asking everyone to serve as a senator in the congress? If you don't serve as a senator, then your opinions do not matter...? It has some truth in it, but the ability to delegate is also important.

[Gao | 郜 @gaohan137]

Hey @OpenZeppelin , can you guys create canaries or any appropriate engineering processes to make sure Relayer works consistently? We use it for mission critical component and Relayer has been stuck for at least twice over the past 2 months.

[Gao | 郜 @gaohan137]

@0x94305 Curious what is your opinion on JIT itself? I originally thought it would help swappers to achieve low slippage. But after seeing your thread, I think JIT is opening the door to more MEV and also hurt passive LPs. Is it worth to ban/penalize it in UniV4 hook?

[Gao | 郜 @gaohan137]

JIT is bad for both swappers and organic passive LPs. The pure existence of JIT creates an imbalance of information: what traders can see/simulate against on-chain data vs. what actually will land on-chain. @aadams can UniV4 hooks be used to penalize such behavior?

[Gao | 郜 @gaohan137]

@aadams Not an ad: check out Charles Schwab investor checking account: https://t.co/FlD5L107zb. Has fee rebate and use standard Visa foreign exchange rate.

[Gao | 郜 @gaohan137]

@xin__wan @danrobinson @0x94305 Can hooks in UniV4 help mitigate JIT? A brute force idea is to ban same-block add/withdraw liquidity using hooks.