Kimchi

OG Eth Degen || Blockchain scout

[Kimchi @0xSwims]

Yo @famous_dyl want to give insight here too please while you're at it?

Fucking retard.

[Dyl 🔥 @famous_dyl]

@0xSwims homie, the “X verification” is someone who just put a fake cryptographic OAuth on the token in order to look like it’s legitimately connected to @TradePools

it’s a very simple spoof and it’s impossible to verify that private key. everything points to this being a spoof.

[Kimchi @0xSwims]

Damn bros getting raped in comments.

Where's your "community" for the "official"

No real traders. Just bundles and farming. Walking clown.

[Dyl 🔥 @famous_dyl]

THIS IS A SCAM $POOLS

0x7fe3778b2520a5868fb8bc16fea0f33dd9e7122a

DO NOT BUY THIS TOKEN.

It is verifiably a spoof intended to look like its connected to @TradePools

The can be verified simply. Check a legitimate signature like $FRONG and it is 64 bytes. This fake $POOLS token is signed with 32 bytes. None of the X account data is verifiable. It is obviously a fake token that was intended to be misleading.

There is a large group of shills trying to push this narrative. I’m not saying the biggest $POOLS is connected to the Uniswap team, but its more likely than this obvious fake spoof. It’s undeniable - someone made this token to be intentionally misleading and look like it was connected to @TradePools

BEWARE!

[Kimchi @0xSwims]

Two as in $Tpools and the xAuth $Pools.

Not the cabal larp rape at 1m

[Kimchi @0xSwims]

So indecisive right now, on-chain isn't clear between the two. Someone sway me with data.

$pools

[Kimchi @0xSwims]

@famous_dyl You've been calling the biggest one the official one consistently.

Keep it up brother

[Kimchi @0xSwims]

@famous_dyl @TradePools Little man's stature got bruised.

This sounds more like weak conviction about the slowing momentum of your own scam, hence the deflection and vague statements. Now, get blocked.

[Kimchi @0xSwims]

@famous_dyl PeOpLe mAy bE fArMiNg

You're the ONLY one bullposting.

You and cryptowolfy are known rapists dude. Fuck off hahaha.

[Kimchi @0xSwims]

Yo @famous_dyl want to give insight here too please while you're at it?

Fucking retard.

[Dyl 🔥 @famous_dyl]

@0xSwims homie, the “X verification” is someone who just put a fake cryptographic OAuth on the token in order to look like it’s legitimately connected to @TradePools

it’s a very simple spoof and it’s impossible to verify that private key. everything points to this being a spoof.

[Kimchi @0xSwims]

@famous_dyl @zacklabadie Also incorrect, on each of these statements. Waiting for this answer though.

Faggot

[Kimchi @0xSwims]

No, the biggest $Pools doesn't have it. Keep larping so I can keep proving you wrong @famous_dyl.

And if anyone can add X verification metadata, that means you can do it too, so go ahead and give it a try big man! @famous_dyl

Keep lying to your followers.

[Dyl 🔥 @famous_dyl]

@0xSwims anyone can add the X verification metadata, the others who did it just copied the oldest / biggest one. The biggest $POOLS has it too. This whole convo is rediculous tbh. I’ve gone deep onchain.

[Kimchi @0xSwims]

@famous_dyl @TradePools Not if it's launched through the Pools protocol, which it was. Otherwise Uniswap's contract would deny creation.

Continue please.

[Kimchi @0xSwims]

So indecisive right now, on-chain isn't clear between the two. Someone sway me with data.

$pools

[Kimchi @0xSwims]

@famous_dyl The call data you're referring to had the Apple touch logo (not even fucking in the realm of the $pools logo) and the public website of the launchpad. Further disproving you. Keep going!

[Kimchi @0xSwims]

@famous_dyl Done! In the meantime prove the biggest $Pools has it:

[Dyl 🔥 @famous_dyl]

@0xSwims anyone can add the X verification metadata, the others who did it just copied the oldest / biggest one. The biggest $POOLS has it too. This whole convo is rediculous tbh. I’ve gone deep onchain.

[Kimchi @0xSwims]

'The claims being made are not authentic.

Where his argument goes too far
A properly signed JWT is different.
A JWT has:
header.payload.signature
The signature is generated over the header + payload. A server can verify that signature using the appropriate secret/public key. If the signature is valid and the issuer is trusted, you have cryptographic evidence that the issuer issued that exact set of claims.
So:
“The payload contains only publicly available information, therefore the JWT proves nothing.”
False.
The information in the payload can be publicly available while the signature still provides authenticity/integrity.
But there’s an important caveat for your TradePools situation
Even a valid signed JWT doesn’t automatically prove:
“This specific person/entity authenticated with TradePools.”
What it proves is closer to:
“The trusted JWT issuer signed a token asserting that this handle/ID/wallet corresponds to this authenticated session/subject.”
Whether that constitutes proof of authentication depends on how TradePools generated the JWT.
For example:
Strong case:
User logs into TradePools → TradePools verifies login → TradePools signs JWT → server verifies JWT
Then the JWT is meaningful evidence that TradePools authenticated that session/identity.
Weak case:
Client submits handle + wallet → backend blindly signs JWT
Then the JWT proves only that TradePools’ signing system signed those claims, not that the underlying identity was actually authenticated. '

[Kimchi @0xSwims]

Here is the Hex code for the larp $pools. Check yourself.

0xac9650d800000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000003c00000000000000000000000000000000000000000000000000000000000000344dec14be1000000000000000000000000000000e200088d55c39a11f609e5f667729ad49b00000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000000120000000000000000000000000000000000000000033b2e3c9fd0803ce800000000000000000000000000000000004c4ccc709ef590f7c81102c0689f0263d4e90000000000000000000000000000000000000000000000000000000000000160000000000000000000000000000000000000000000000000000000000000000b706f6f6c732e74726164650000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000005504f4f4c5300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001c00000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000e000000000000000000000000000000000000000000000000000000000000001200000000000000000000000000000000000000000000000000000000000000180000000000000000000000000000000000000000000000000000000000000002b506f6f6c7320e2809420637265617465206120746f6b656e206f6e20526f62696e686f6f6420436861696e000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001468747470733a2f2f706f6f6c732e74726164652f000000000000000000000000000000000000000000000000000000000000000000000000000000000000002868747470733a2f2f706f6f6c732e74726164652f6170706c652d746f7563682d69636f6e2e706e670000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000104b6982b48000000000000000000000000385b36ff682ab4c76e7c37a66b96aabc466471d500000000000000000000000000000000000000000000000000000000000000607f70721be5727bf5b58460c6c69fae4a1b8776d5a67157ebee49dd400e831336000000000000000000000000ce57498d3474dcc244dfb6710ffbe6d4441cd2b20000000000000000000000000000000000000000033b2e3c9fd0803ce800000000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000020000000000000000000000000be4eba417999c7269c6d631eaef82ad3f2bcdd9e00000000000000000000000000000000000000000000000000000000

[Kimchi @0xSwims]

@richwithm3 Hate subminal messaging shit. Going as deep as possible into the blockchain

[Kimchi @0xSwims]

$TPools and $Pools do have the same xVerification.

Digging into launch protocol for each now.

[Kimchi @0xSwims]

Working on a new thesis too as I observe.

[Kimchi @0xSwims]

Going to observe things for a bit and get to dex when the time is right.

The last thing I want to do is pay for one, then get vamped by the other.

Watching.

[Kimchi @0xSwims]

Going to observe things for a bit and get to dex when the time is right.

The last thing I want to do is pay for one, then get vamped by the other.

Watching.

[Kimchi @0xSwims]

@SteveApesBlind Not if it wasn't launched through Pools protocol

[Kimchi @0xSwims]

What I don't understand is how $TPools got the xVerification token first wkthout anything to copy from

[Kimchi @0xSwims]

$TPools and $Pools do have the same xVerification.

Digging into launch protocol for each now.

[Kimchi @0xSwims]

@SteveApesBlind No. I didn't say that.