Friend.tech Cofounder Offered $200,000 for a Path Off Base

Friend.tech co-founder Racer put a $200,000 system-design bounty on a way to move the social-crypto application off Base on May 26, 2024, provided a proposed migration avoided major user problems and worked well enough for the team to adopt. The condition matters: the post signaled a desire to explore an exit, not an executed migration or a final protocol decision.

The episode was consequential because Friend.tech was one of Base’s best-known consumer applications. Base, an Ethereum layer-2 network incubated by Coinbase, supplied the transaction environment in which Friend.tech’s token-gated social product operated. A public break between a prominent application and its host chain therefore tested a central promise of modular crypto infrastructure: applications may be portable in theory, but user state, assets, liquidity and expectations make moving them difficult in practice.

A conditional bounty, not a completed move

Racer, a pseudonymous co-founder, attributed the strained relationship to the way parts of the Base and Ethereum communities had treated Friend.tech after launch. That explanation was a contemporaneous claim by Racer, not an independently established finding. The important verifiable action was narrower: a public offer of $200,000 for a migration design that met the team’s conditions.

The central posts later became inaccessible. Their exact URLs survive, and The Block reproduced the bounty language in a report timestamped 4:35 p.m. EDT on May 26. Because the underlying account was intermittently unavailable even during that day, the surviving record does not show formal bounty rules, a funding address, a deadline or an acceptance process. It should not be described as a binding open-source grant without those details.

Base lead Jesse Pollak responded publicly on May 26. He acknowledged that the Friend.tech team felt isolated from parts of the Base and Ethereum ecosystems, said he would be disappointed if the team left, and said he would respect and support its chosen path. Pollak’s response corroborated that the migration discussion was real while stopping short of saying Base had expelled Friend.tech or that a departure had been agreed.

The token made platform risk visible

FRIEND had begun trading on May 3 alongside Friend.tech’s version-two rollout. That upgrade introduced Clubs, community spaces whose keys were transacted in FRIEND. The token therefore connected the application’s product design, its users and Base-based liquidity more tightly than a conventional Web2 service would be connected to a cloud provider.

The market reaction was immediate but the surviving measurement is imprecise. The Block reported at 4:35 p.m. EDT that FRIEND had fallen about 20% following Racer’s post, using its own price page. The report did not state the trading venue, precise start and end timestamps, or endpoint prices. Coinburn therefore treats “about 20%” as a contemporaneous directional observation for the FRIEND instrument, not a reproducible close-to-close return or proof that the post alone caused every trade.

The selloff nevertheless reflected a coherent risk: a migration could require technical work, liquidity relocation and new user actions, while remaining on Base could leave unresolved ecosystem tensions. Neither path was settled on May 26.

What was knowable on May 26

By the end of May 26, the verified record supported three conclusions. Racer had solicited a conditional migration design; Base’s lead had publicly answered; and FRIEND had repriced sharply in contemporaneous reporting. It did not establish that Friend.tech had selected another chain, that user assets would move, or that the $200,000 would ever be paid. Those boundaries are essential to preserving the event-day record.