Commemorative Base FID registry

​

Purpose

Base FID exists solely as a paid, sequential commemorative record on Base. A Base FID records a number and its current custody wallet. It has no application, social-network, governance, reward, identity-verification, financial, or promised future utility beyond the registry’s basic custody and transfer operations. Base FID is not an ERC-20, ERC-721, or ERC-1155 token, and it is not the $FARCASTER memecoin or its 20,000-address airdrop. The separate token is documented on the $FARCASTER ID page.

​

What a Base FID represents

Minting or holding a Base FID does not create a $FARCASTER allocation, change the historical memecoin airdrop snapshot, or establish any relationship with the Farcaster protocol or its operators.

​

Canonical Base contracts

Both the proxy and active implementation source are verified on BaseScan. The registry is upgradeable; only the disclosed Safe owner can authorize an implementation upgrade or withdraw accumulated mint fees.

​

Commemorative issuance model

• Base FIDs 0 through 299 are permanently reserved to the protocol owner and cannot be transferred.
• After migration, public issuance is permissionless and sequential.
• A caller may mint 1 through 100 next-available commemorative Base FIDs to itself.
• The exact price is 0.0015 ETH per Base FID, plus Base network gas.
• The mint function cannot designate an unrelated recipient address.
• Public Base FIDs may be transferred only by their current custody wallet.
• Direct ETH transfers outside the mint function revert.
• Mint fees create no collateral, redemption right, yield, or claim on the registry or its owner.

​

One-time migration

Before public minting opened, the deployment wallet held a narrow migration authority. It could make one bounded call assigning one new sequential Base FID to each current custodian in the superseded Base FID registry. The call did not preserve old identifier numbers and did not map Base FIDs to Farcaster protocol FIDs. The production migration was completed in one transaction: The same successful transaction permanently set migrationCompleted() to true and migrationAuthority() to the zero address. The migration cannot be replayed, extended, or directed to additional wallets.

​

Expected address activity

The observed address activity has two legitimate sources:

1. the completed 15-address migration above; and
2. paid public mint calls, each of which assigns consecutive identifiers only to the transaction sender.

At the August 20, 2026 verification snapshot, live Base state reported:

• latestFid() = 1082 and nextFid() = 1083;
• 300 reserved records, 15 migrated records, and 768 paid public records;
• migrationCompleted() = true;
• migrationAuthority() = the zero address; and
• owner() = the disclosed Safe.

There is no continuing airdrop distributor and no function that allows the former deployment wallet to push Base FIDs to arbitrary third-party wallets. The former wallet 0x1e9F…97F5 created the active proxy in 0xe68cdd312008451a9722e81e66ce9fa222b564bbd39682636adfd5dbe6f90005. Its relationship ended when the one-time migration authority was revoked. The disclosed Safe retains only the documented proxy-upgrade and fee-withdrawal authority.

​

Public verification

Reproducible internal mechanism, source-verification, and test records are available to security reviewers on request. They are not an independent third-party audit or certification. Users should verify live state and the canonical proxy address before interacting. See also the fid.market Terms of Service and the live registry interface.