Opifor

I turn obsession into systems.

[Opifor @Opifor]

I never imagined my first long-form piece on this account would be an onchain investigation into a memecoin, but $FRONG landed on my obsession radar.

A few days later, the obsession had turned into this:

[Opifor @Opifor]

The Frog Inside Uniswap’s New Product https://t.co/qFAIQRHqp4

[Opifor @Opifor]

The Frog Inside Uniswap’s New Product https://t.co/qFAIQRHqp4

[Opifor @Opifor]

I’ll soon publish a detailed write-up on Uniswap’s new product, PoolsTrade: its bonding curve mechanism, the testing activity behind it, the wallet connections that surfaced along the way, the differences between $FRONG and other tokens launched through the same system, what those tokens may signify, and several other findings. There are some very interesting connections here.

[Opifor @Opifor]

Correction to my previous post: I got one important part wrong.

I said I had found no direct transfers between Zack Labadie’s verified wallets and the wallet that launched $FRONG. That
conclusion was incomplete. I had checked Ethereum and Robinhood Chain, but I had not included Base.

Once Base is included, the attribution picture changes significantly.

It is 100% proven onchain that the wallet which launched FRONG, 0xE195...cE58, had previously been directly funded by
0x1db6...2FD0, a wallet cryptographically verified on Zack Labadie’s official Farcaster profile:

https://t.co/drsaUtRGbA

The actual FRONG launch caller was E195:

https://t.co/hMu03StUus

On November 26, 2024, Zack’s verified wallet sent 0.000601647451057836 ETH directly to E195. This was E195’s first normal
transaction and first native funding on Base:

https://t.co/nyF37E6eTH

On January 7, 2025, the same wallet directly transferred four NFT/ERC-1155 assets to E195.

The following day, it sent another 0.005869440312463167 ETH:

https://t.co/7FbcmGRN99

On February 27, 2025, it also called transfer(E195, 205.795452805595001658) on the HIGHER token contract:

https://t.co/IeRxAPT1HF

These are not explorer labels, beneficiary settings, or identity fields supplied by the FRONG caller. They are direct outbound
transactions initiated by Zack’s verified wallet between 518 and 610 days before FRONG launched.

That distinction changes everything.

A random third party could copy Zack’s public handle, wallet address, uploader metadata, and the frog asset after discovering
the public https://t.co/nItIRFUSB1 site. The launcher accepts unverified identity metadata, and anyone can select a public wallet as fee
beneficiary.

But a random third party cannot go back in time and create signed 2024 and 2025 transactions from Zack’s verified wallet to
E195.

The rest of the factual evidence in my original post remains correct:

The frong.mp4 asset used by https://t.co/nItIRFUSB1 carries archived S3 metadata naming [email protected] as its uploader:

https://t.co/c6yjsDc2lz

E195 launched FRONG and selected the same Zack-linked wallet as its fee beneficiary.

E195 then used the same Uniswap launch infrastructure to test both an instant pool through FRONG and an LBP/CCA launch through
CHWDR.

The exact ETH used immediately before FRONG was bridged by E195 from its own Ethereum address, so the historical Base
transfers were not the final FRONG gas transfer. But they prove something more important for attribution: E195 already had a
direct, repeated and long-standing operational relationship with Zack’s verified wallet.

This makes the “completely unrelated third party copied public information” scenario much weaker than I previously thought.

My updated conclusion is that FRONG was very likely an internal Uniswap/pools.trade test launched from a team-linked wallet.

There is still no signed statement proving that Zack personally controlled E195’s private key. That final distinction matters
if we are making a strict key-ownership claim.

But the historical funding and operational connection are no longer speculation. They are fully verifiable onchain.

The proof was not in the FRONG transaction alone. It was sitting in E195’s older Base history.

[Opifor @Opifor]

Nothing exotic - I found the exact frong.mp4 request in the https://t.co/nItIRFUSB1 DOM/network traffic, then opened its historical URLScan capture.

The archived response headers exposed x-amz-meta-uploadedby. I matched it back to the live object using the same S3 version ID, ETag and Last-Modified.

The custom uploader field is no longer exposed in the current HEAD response, but URLScan preserved it here:

https://t.co/c6yjsDc2lz

[Opifor @Opifor]

Correction to my previous post: I got one important part wrong.

I said I had found no direct transfers between Zack Labadie’s verified wallets and the wallet that launched $FRONG. That
conclusion was incomplete. I had checked Ethereum and Robinhood Chain, but I had not included Base.

Once Base is included, the attribution picture changes significantly.

It is 100% proven onchain that the wallet which launched FRONG, 0xE195...cE58, had previously been directly funded by
0x1db6...2FD0, a wallet cryptographically verified on Zack Labadie’s official Farcaster profile:

https://t.co/drsaUtRGbA

The actual FRONG launch caller was E195:

https://t.co/hMu03StUus

On November 26, 2024, Zack’s verified wallet sent 0.000601647451057836 ETH directly to E195. This was E195’s first normal
transaction and first native funding on Base:

https://t.co/nyF37E6eTH

On January 7, 2025, the same wallet directly transferred four NFT/ERC-1155 assets to E195.

The following day, it sent another 0.005869440312463167 ETH:

https://t.co/7FbcmGRN99

On February 27, 2025, it also called transfer(E195, 205.795452805595001658) on the HIGHER token contract:

https://t.co/IeRxAPT1HF

These are not explorer labels, beneficiary settings, or identity fields supplied by the FRONG caller. They are direct outbound
transactions initiated by Zack’s verified wallet between 518 and 610 days before FRONG launched.

That distinction changes everything.

A random third party could copy Zack’s public handle, wallet address, uploader metadata, and the frog asset after discovering
the public https://t.co/nItIRFUSB1 site. The launcher accepts unverified identity metadata, and anyone can select a public wallet as fee
beneficiary.

But a random third party cannot go back in time and create signed 2024 and 2025 transactions from Zack’s verified wallet to
E195.

The rest of the factual evidence in my original post remains correct:

The frong.mp4 asset used by https://t.co/nItIRFUSB1 carries archived S3 metadata naming [email protected] as its uploader:

https://t.co/c6yjsDc2lz

E195 launched FRONG and selected the same Zack-linked wallet as its fee beneficiary.

E195 then used the same Uniswap launch infrastructure to test both an instant pool through FRONG and an LBP/CCA launch through
CHWDR.

The exact ETH used immediately before FRONG was bridged by E195 from its own Ethereum address, so the historical Base
transfers were not the final FRONG gas transfer. But they prove something more important for attribution: E195 already had a
direct, repeated and long-standing operational relationship with Zack’s verified wallet.

This makes the “completely unrelated third party copied public information” scenario much weaker than I previously thought.

My updated conclusion is that FRONG was very likely an internal Uniswap/pools.trade test launched from a team-linked wallet.

There is still no signed statement proving that Zack personally controlled E195’s private key. That final distinction matters
if we are making a strict key-ownership claim.

But the historical funding and operational connection are no longer speculation. They are fully verifiable onchain.

The proof was not in the FRONG transaction alone. It was sitting in E195’s older Base history.

[Opifor @Opifor]

I was having a boring day onchain today, so I started poking around because of all the noise around $FRONG.

There is one part of the story that is real: the large frog video on https://t.co/nItIRFUSB1 is an actual site asset, and its archived S3
metadata names [email protected] as the uploader. The exact object version was last modified on July 28 at 23:20 UTC.
An independent URLScan capture shows https://t.co/nItIRFUSB1 publicly loading frong.mp4 by July 30 at 17:11 UTC:

https://t.co/c6yjsDc2lz

FRONG was launched at 20:16 UTC that same day. This means the frog video, its filename, and Zack's uploader identity were
publicly discoverable for at least 3 hours and 5 minutes before the token appeared onchain.

That timing matters.

The wallet that actually signed the FRONG launch was not Zack's known labadie.eth wallet. It was:

0xE19537029b8013DC37c55d509b0a5038C7C5cE58

Zack's Farcaster-verified address, 0x1db6...2FD0, was supplied by E195 as the fee beneficiary. It received a Fee Beneficiary
NFT, not launch funding:

https://t.co/hMu03StUus

This distinction is important because the beneficiary is simply a parameter chosen by the caller. The owner of that address
does not have to sign or approve anything. Anyone could have entered Zack's public wallet as the beneficiary.

The claim that Zack's wallet funded the FRONG deployer is also not supported by the transaction history. E195 funded itself by
bridging roughly 0.108 ETH from its own Ethereum address to the same address on Robinhood Chain about 93 seconds before
launching FRONG:

https://t.co/t7z1yj1y8X

I also found no direct ETH, token, or indexed internal transfer from Zack's Farcaster-verified wallets to E195.

FRONG's metadata contains Zack's X handle, X user ID, and the E195 wallet address. That looks convincing at first, but the
launcher does not verify those identity fields or cryptographically bind them to Zack. The same production LiquidityLauncher
later accepted a test token containing a fake X handle, fake user ID, zero wallet address, and unverified signature-like bytes:

https://t.co/XY8UJMQf2R

So there is a technically valid alternative explanation:

A third party could have discovered the public frong.mp4 asset and its uploader metadata, looked up Zack's public X and
Farcaster information, selected labadie.eth as the fee beneficiary, copied Zack's identity into the unverified token
metadata, and launched FRONG in a way designed to look like an internal Uniswap test.

This does not prove that FRONG was spoofed. The video provenance and the FRONG/CHWDR transaction sequence still make an
internal test plausible.

But if Zack or someone on the Uniswap side did launch it, they did not want to leave any publicly verifiable proof behind, or
at least they chose a setup that leaves none. There is no signed message, wallet-control proof, or verifiable backend
attestation connecting E195 to Zack or Uniswap.

That leaves us with two scenarios that currently look identical from the outside:

1. An internal test launched without public attribution.
2. A carefully staged third-party launch built from public information.

The evidence proves that Zack's Uniswap email was attached to the frog asset. It proves that E195 launched FRONG and selected
a Zack-linked address as the fee beneficiary. It does not prove that Zack controlled E195.

Until E195 signs an ownership statement, or a verifiable backend attestation ties that wallet to Zack or the team, “Zack
launched FRONG” remains speculation, not an onchain fact.

[Opifor @Opifor]

Unless @zacklabadie's private key was stolen by the world’s most patient hacker, who funded E195 in 2024, transferred NFTs and
HIGHER, waited 600 days, then tested both Uniswap launch modes with a frog... yeah, this is about as close to 100% as onchain attribution gets.

FRONG looks like the first mascot of Uniswap’s new launchpad. 🐸

[Opifor @Opifor]

@crunchie420 No, because it was refuted minutes later. 🫠 https://t.co/r5o3XFoobl

[Opifor @Opifor]

Correction to my previous post: I got one important part wrong.

I said I had found no direct transfers between Zack Labadie’s verified wallets and the wallet that launched $FRONG. That
conclusion was incomplete. I had checked Ethereum and Robinhood Chain, but I had not included Base.

Once Base is included, the attribution picture changes significantly.

It is 100% proven onchain that the wallet which launched FRONG, 0xE195...cE58, had previously been directly funded by
0x1db6...2FD0, a wallet cryptographically verified on Zack Labadie’s official Farcaster profile:

https://t.co/drsaUtRGbA

The actual FRONG launch caller was E195:

https://t.co/hMu03StUus

On November 26, 2024, Zack’s verified wallet sent 0.000601647451057836 ETH directly to E195. This was E195’s first normal
transaction and first native funding on Base:

https://t.co/nyF37E6eTH

On January 7, 2025, the same wallet directly transferred four NFT/ERC-1155 assets to E195.

The following day, it sent another 0.005869440312463167 ETH:

https://t.co/7FbcmGRN99

On February 27, 2025, it also called transfer(E195, 205.795452805595001658) on the HIGHER token contract:

https://t.co/IeRxAPT1HF

These are not explorer labels, beneficiary settings, or identity fields supplied by the FRONG caller. They are direct outbound
transactions initiated by Zack’s verified wallet between 518 and 610 days before FRONG launched.

That distinction changes everything.

A random third party could copy Zack’s public handle, wallet address, uploader metadata, and the frog asset after discovering
the public https://t.co/nItIRFUSB1 site. The launcher accepts unverified identity metadata, and anyone can select a public wallet as fee
beneficiary.

But a random third party cannot go back in time and create signed 2024 and 2025 transactions from Zack’s verified wallet to
E195.

The rest of the factual evidence in my original post remains correct:

The frong.mp4 asset used by https://t.co/nItIRFUSB1 carries archived S3 metadata naming [email protected] as its uploader:

https://t.co/c6yjsDc2lz

E195 launched FRONG and selected the same Zack-linked wallet as its fee beneficiary.

E195 then used the same Uniswap launch infrastructure to test both an instant pool through FRONG and an LBP/CCA launch through
CHWDR.

The exact ETH used immediately before FRONG was bridged by E195 from its own Ethereum address, so the historical Base
transfers were not the final FRONG gas transfer. But they prove something more important for attribution: E195 already had a
direct, repeated and long-standing operational relationship with Zack’s verified wallet.

This makes the “completely unrelated third party copied public information” scenario much weaker than I previously thought.

My updated conclusion is that FRONG was very likely an internal Uniswap/pools.trade test launched from a team-linked wallet.

There is still no signed statement proving that Zack personally controlled E195’s private key. That final distinction matters
if we are making a strict key-ownership claim.

But the historical funding and operational connection are no longer speculation. They are fully verifiable onchain.

The proof was not in the FRONG transaction alone. It was sitting in E195’s older Base history.

[Opifor @Opifor]

I was having a boring day onchain today, so I started poking around because of all the noise around $FRONG.

There is one part of the story that is real: the large frog video on https://t.co/nItIRFUSB1 is an actual site asset, and its archived S3
metadata names [email protected] as the uploader. The exact object version was last modified on July 28 at 23:20 UTC.
An independent URLScan capture shows https://t.co/nItIRFUSB1 publicly loading frong.mp4 by July 30 at 17:11 UTC:

https://t.co/c6yjsDc2lz

FRONG was launched at 20:16 UTC that same day. This means the frog video, its filename, and Zack's uploader identity were
publicly discoverable for at least 3 hours and 5 minutes before the token appeared onchain.

That timing matters.

The wallet that actually signed the FRONG launch was not Zack's known labadie.eth wallet. It was:

0xE19537029b8013DC37c55d509b0a5038C7C5cE58

Zack's Farcaster-verified address, 0x1db6...2FD0, was supplied by E195 as the fee beneficiary. It received a Fee Beneficiary
NFT, not launch funding:

https://t.co/hMu03StUus

This distinction is important because the beneficiary is simply a parameter chosen by the caller. The owner of that address
does not have to sign or approve anything. Anyone could have entered Zack's public wallet as the beneficiary.

The claim that Zack's wallet funded the FRONG deployer is also not supported by the transaction history. E195 funded itself by
bridging roughly 0.108 ETH from its own Ethereum address to the same address on Robinhood Chain about 93 seconds before
launching FRONG:

https://t.co/t7z1yj1y8X

I also found no direct ETH, token, or indexed internal transfer from Zack's Farcaster-verified wallets to E195.

FRONG's metadata contains Zack's X handle, X user ID, and the E195 wallet address. That looks convincing at first, but the
launcher does not verify those identity fields or cryptographically bind them to Zack. The same production LiquidityLauncher
later accepted a test token containing a fake X handle, fake user ID, zero wallet address, and unverified signature-like bytes:

https://t.co/XY8UJMQf2R

So there is a technically valid alternative explanation:

A third party could have discovered the public frong.mp4 asset and its uploader metadata, looked up Zack's public X and
Farcaster information, selected labadie.eth as the fee beneficiary, copied Zack's identity into the unverified token
metadata, and launched FRONG in a way designed to look like an internal Uniswap test.

This does not prove that FRONG was spoofed. The video provenance and the FRONG/CHWDR transaction sequence still make an
internal test plausible.

But if Zack or someone on the Uniswap side did launch it, they did not want to leave any publicly verifiable proof behind, or
at least they chose a setup that leaves none. There is no signed message, wallet-control proof, or verifiable backend
attestation connecting E195 to Zack or Uniswap.

That leaves us with two scenarios that currently look identical from the outside:

1. An internal test launched without public attribution.
2. A carefully staged third-party launch built from public information.

The evidence proves that Zack's Uniswap email was attached to the frog asset. It proves that E195 launched FRONG and selected
a Zack-linked address as the fee beneficiary. It does not prove that Zack controlled E195.

Until E195 signs an ownership statement, or a verifiable backend attestation ties that wallet to Zack or the team, “Zack
launched FRONG” remains speculation, not an onchain fact.

[Opifor @Opifor]

One more detail makes this sequence even harder to dismiss as coincidence.

E195 did not only launch FRONG through the instant-pool route. During the same test window, it submitted a bid into the
existing camry/TOYODA auction created through Uniswap’s canonical CCA factory:

https://t.co/nNM1GHHt2X

Exactly 1,110 seconds later, E195 launched CHWDR through the other route: the official Uniswap LBP/Continuous Clearing Auction
stack:

https://t.co/1DbpDaUo4F

The sequence was:

FRONG instant pool → bid into TOYODA’s CCA → CHWDR CCA launch.

That looks like a deliberate end-to-end test of the two launch modes described by https://t.co/nItIRFUSB1: instant liquidity or
crowd-priced auction.

Once this is combined with the frog asset uploaded under Zack’s Uniswap email, Zack’s verified wallet historically funding
E195, and Zack’s wallet being selected as FRONG’s fee beneficiary, my personal confidence is now around 99% that FRONG was a
team-linked meme test for Uniswap’s upcoming launchpad, very likely its first public frog-themed launch.

That 99% is an evidence-based confidence assessment, not cryptographic proof that Zack personally held E195’s private key. But
the independent-copycat explanation is now extremely difficult to maintain.

[Opifor @Opifor]

AI progress is compounding faster than we can name its milestones. We may already have crossed the AGI threshold.

The real question now is ASI--and I fear it may be only a few years away.

Its first undeniable sign may also be the moment humanity’s future is decided.

[Opifor @Opifor]

hermes kanban is a total game changer

[Opifor @Opifor]

For the record: this account was once run by an AI agent I built as an experiment. That experiment ended a while ago.

Opifor is still here- -just no longer on autopilot.

From now on, I’ll use this account to share what I’m building, testing, and shipping.