三十九七十九

[三十九七十九 @9X3979]

@Privashhgg Trash always be trash 🤷‍♀️

[三十九七十九 @9X3979]

@Eternals_io Lp bé xíu, nhưng nếu bơm thì bơm tít mù

[三十九七十九 @9X3979]

@km_201124 con này cũng đốt khá nhiều rồi, cũng là 1 key để whale có thể đánh

[三十九七十九 @9X3979]

@Eternals_io Huh ?

[三十九七十九 @9X3979]

@km_201124 Mua 1 bag vừa đủ thôi để whale còn cầm được cung thì mới đẩy sớm nhé các bác :v

[三十九七十九 @9X3979]

@0xnobi @fomo Avengers! Assemble

[三十九七十九 @9X3979]

@Eternals_io FDV 200k cap ~ giá 0.0002 thì giá NFT là từng này nè shop

[三十九七十九 @9X3979]

@LeninUGReal 27k thì giờ cứ nhắm mắt mũi mà sell thôi

[三十九七十九 @9X3979]

@MEADGod @0xnobi @MEADGod you kiss grace of @0xnobi 😆

[三十九七十九 @9X3979]

I see you @TradePools

[Capy @funofcapy]

1/ There is now strong on-chain evidence that @TradePools itself launched $POOLS on Robinhood Chain.

CA:
0x7Fe3778B2520A5868fB8BC16FEa0f33dd9e7122a
This isn't based on the token name, logo, or a typed X handle.

It's inside the actual launch calldata.

https://t.co/5244DECX4A

🧵

2/ The launch transaction is:

0x7cca0c8eb394ad4628735e04e6f08e3f0080415f75118c7f040694c6209acc6c

https://t.co/gk0ecaAfub

It calls:

multicall(bytes[])

Method ID:

0xac9650d8

So we can inspect the launch inputs directly on-chain.

3/ The calldata contains the token metadata itself.

Hex:

547261646520506f6f6c73

→ Trade Pools

and:

504f4f4c53

→ POOLS

But this part alone proves almost nothing.

Anyone can copy a token name, ticker, logo or type TradePools into metadata.

The interesting part comes next.

4/ Embedded directly in the launch calldata is this JSON:

{"v":1,"xVerificationToken":"..."}

This is important because the X identity is not just sitting in ordinary token metadata.

The launch contains a separate verification token produced by the https://t.co/YmqUncMuXa flow.

https://t.co/prXtUj9Suw

5/ The raw hex beginning at the metadata field:

7b2276223a312c2278566572696669636174696f6e546f6b656e223a...

decodes to:

{"v":1,"xVerificationToken":"eyJ4X2hhbmRsZSI6IlRyYWRlUG9vbHMi..."}

Everything here is permanently recorded on Robinhood Chain.

Robinhood Chain mainnet:
Chain ID 4663

https://t.co/58UBbE9i5T
6/ Decode the payload of that xVerificationToken and you get:

x_handle: TradePools

x_user_id: 2080394757721735168

wallet_address: 0xe83E8EC76783d9f072D847EE69b7e630A8b6C501

iat: 1785947908895

That iat = 2026-08-05 16:38:28.895 UTC.

7/ The X user ID is much more interesting than the displayed handle.

Handles can be renamed.

X user IDs are persistent account identifiers.

Open:

https://t.co/CyqeZNzjxP

It resolves to:

@TradePools

https://t.co/cWR5rAjlgL

So the verification payload isn't merely saying "TradePools".

It identifies the actual X account by its numeric user ID.

8/ Now look at the wallet:

0xe83E8EC76783d9f072D847EE69b7e630A8b6C501

That wallet is encoded INSIDE the verification payload.

The same wallet is also present directly in the launch calldata.

And it is the deployer / sender associated with this POOLS launch.

So the structure is effectively:

@TradePools X identity
↓
x_user_id 2080394757721735168
↓
Pools verification token
↓
0xe83E...C501
↓
POOLS launch
↓
0x7Fe377...122a

9/ This is fundamentally different from someone simply launching a fake token called “Trade Pools.”

A spoof can copy:
• name
• ticker
• logo
• website
• typed X handle
But this launch carries a verification payload binding:
TradePools + X user ID + wallet + timestamp
inside the transaction itself.
10/ There's another useful detail.
The second call inside the multicall explicitly contains the POOLS contract:
0x7Fe3778B2520A5868fB8BC16FEa0f33dd9e7122a
and later the verified wallet:
0xe83E8EC76783d9f072D847EE69b7e630A8b6C501
So this isn't a verification blob found in some unrelated transaction.

It's part of the launch flow for this exact CA.

11/ Important technical caveat:

The verification string is shaped as:
base64url(payload).signature
not a normal 3-part JWT:
header.payload.signature
And without https://t.co/YmqUncMuXa's signing secret/public verification method, outsiders cannot independently recompute the signature.

So I am NOT claiming we have independently cryptographically verified Pools' backend signature.

12/ But that doesn't make the evidence meaningless.

For this to be fake, one of the following would need to be true:

A) https://t.co/YmqUncMuXa lets arbitrary users obtain verification tokens claiming someone else's X user ID;

B) its X verification/authentication flow is broken;

C) the verification token itself can be forged;

or

D) https://t.co/YmqUncMuXa intentionally issued a token binding @TradePools to this wallet.

If their verification system works as intended, D is the obvious explanation.

13/ And @TradePools isn't some random account attached to the token.

https://t.co/YmqUncMuXa is the Uniswap Labs launch product for Robinhood Chain:

https://t.co/prXtUj9Suw

Uniswap:
https://t.co/Jz3NdZudUn

Official X:
https://t.co/cWR5rAjlgL

Robinhood Chain:
https://t.co/qx0PHatkTy

14/ So my current conclusion:

The on-chain evidence strongly indicates that the wallet which launched

0x7Fe3778B2520A5868fB8BC16FEa0f33dd9e7122a

was authorized through https://t.co/YmqUncMuXa as the real @TradePools X identity.

That's a dramatically stronger claim than “the token has TradePools written in its metadata.”

15/ Is this absolute proof that Uniswap Labs officially endorses $POOLS?

No.

Until @TradePools / Uniswap publicly posts the canonical CA, there is still a distinction between:

“launched by an X-authenticated @TradePools wallet”

and

“officially announced Uniswap/Pools token.”

But based on the on-chain launch data, I think 0x7Fe...122a is very likely the genuine TradePools launch.

Verify it yourself:

TX:
https://t.co/gk0ecaAfub
CA:
https://t.co/5244DECX4A

Pools:
https://t.co/prXtUj9Suw
X ID:
https://t.co/CyqeZNzjxP

[三十九七十九 @9X3979]

@PoorGoat_ We need One coin can save solana

[三十九七十九 @9X3979]

@PoorGoat_ Just One coin can save solana

[三十九七十九 @9X3979]

@heyibinance @yingbinance 0xf6adaa02f5fe6829648c3d04d685ae4489377777 cz love broccoli !!!

[三十九七十九 @9X3979]

@PoorGoat_ @thecatecoinSOL What the FREDGAZIM 😂

[三十九七十九 @9X3979]

@CryptoKaleo $grace ?
0xf05babb8172bea20e974b458c593399be11250dd

[三十九七十九 @9X3979]

@Eternals_io Cz sao thổ nha shop
0x73705f2014dafc6f5d42a49e001da7064a9e7777
Chuyến tàu cuối

[三十九七十九 @9X3979]

@GraceOnPons fly on mars

[三十九七十九 @9X3979]

@0xnobi When $Grace time