> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vibechain.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Commemorative Base FID registry
> Canonical contract and disclosures for Base FID, a paid commemorative sequential registry record with no Farcaster or product utility
**Base FID is a commemorative mint only.** It is not a Farcaster protocol
FID, does not create or recover a Farcaster account, and is not sponsored,
endorsed, or operated by Farcaster, Neynar, Warpcast, or their respective
owners, affiliates, employees, or contributors.
## 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](/docs/farcaster-id).
## What a Base FID represents
| A Base FID is | A Base FID is not |
| - | - |
| An independent commemorative sequential number recorded on Base | A Farcaster protocol FID, username, account, profile, or verification |
| An onchain association between that number and a custody wallet | Access to a social network, application, service, or community |
| A registry record that its current custodian may transfer | A token, NFT, governance right, reward, investment, or claim on revenue |
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
| Component | Address |
| - | - |
| Active UUPS proxy | [`0x6D95f435EcD65A43E7233649EAb05Ef8e5761Dff`](https://basescan.org/address/0x6D95f435EcD65A43E7233649EAb05Ef8e5761Dff#code) |
| Active implementation (`2.1.0`) | [`0x7b49a8598eAB7E977ed94c0E03a286a1a83c90dF`](https://basescan.org/address/0x7b49a8598eAB7E977ed94c0E03a286a1a83c90dF#code) |
| Owner, upgrade authority, and fee recipient | [`0xa679568586Ab40Ce14B187Bc1993DAc1Ba1372C6`](https://basescan.org/address/0xa679568586Ab40Ce14B187Bc1993DAc1Ba1372C6) |
| Former deployment and migration wallet | [`0x1e9F3C9e936c60d184a7947bb1798809487F97F5`](https://basescan.org/address/0x1e9F3C9e936c60d184a7947bb1798809487F97F5) |
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:
| Field | Value |
| - | - |
| Transaction | [`0x79194ebe25c6bf54ee020859d187a761e72f899c0b20f8f7daad2013ca93973d`](https://basescan.org/tx/0x79194ebe25c6bf54ee020859d187a761e72f899c0b20f8f7daad2013ca93973d) |
| Base block | `50,203,423` |
| Recipients | `15` |
| Assigned Base FIDs | `300` through `314` |
| Migration authority after execution | zero address |
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`](https://basescan.org/tx/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
Inspect the proxy, live state, transactions, and verified interface.
Read the verified `2.1.0` Solidity implementation on BaseScan.
Inspect the completed 15-address migration transaction.
Confirm the former deployment wallet and initialized proxy.
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](https://vibechain.com/terms) and the
[live registry interface](https://fid.market).
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.