Been knee deep in DEX integrations for @GeniusTerminal the last couple of weeks. Having mainly worked with orthodox Uni V2 and V3 deployments in the past, extending support for variations on the V3 and CLMM design made me realize a couple of things about the DEX space: 1.

Plz guys, I need more reputation to vouch

Someone needs to jailbreak the NEOs so that we can have underground clanker fights

wait, so solana is just one giant google bigtable?

Convinced any sort of KOL tracker and leaderboard is just a honeypot for the IRS

Launchpads shouldn’t use vanity addresses They should use deterministic addresses to combat honeypot pairs

Launchpads shouldn’t use vanity addresses They should use deterministic addresses to combat honeypot pairs

oh, got my @nockchain miner working

Sometimes, size does matter

I'm just going to have to keep doing this, aren't I?

Support the chain !!

Did this mfer conjugate "this is"

Will be supporting this because experimentation is cool If you have trouble finding routing, make an account on @GeniusTerminal We have multiple aggregators that support V4 hooks and we can always get you in

What happened last night

x402 this, x402 that I will build a clanker free space. A space free of non-technical people talking about AI wallets. I will show them that manual input is better for retail. That it creates a dopamine fueled cycle. Down with hardware, long live wetware

Since I have had to do this countless times over the last couple of days, here is how to get the creation code needed to find the init code hash for create2 implementations: cast run <tx_hash> \ --rpc-url <rpc_url> \ --format-json > trace.json Find the input for the CREATE2

27 DEX deployments CREATE2 logic verified and tested 13 more to go

> contract only verified on snowtrace > only way to view source code

If you use contract creation code in your CREATE2 logic...fuck you