Bureau of Internet Culture

NFD to BIC, and back

Feisty Doge is becoming BIC, the Bureau of Internet Culture’s token. One NFD becomes one BIC. One BIC redeems for one NFD. The contract holds every migrated NFD in escrow and nobody — not the multisig, not the deployer — has a path to it except a reverse migration. That escrow is shared and first-come: it holds only NFD that came in through a migration, and any BIC holder can redeem against it, so the figure below is what is actually redeemable right now.

NFD → BIC

Not live yet

This site is not set up to run the migration yet, so nothing here will ask your wallet for anything until it is. The contracts are written and tested but are not yet on Ethereum mainnet. When they are, and this page has checked on chain that the addresses it holds are theirs, the wallet controls appear here and nowhere else.

Until this page shows a wallet control, no page on this site migrates NFD — and nobody from the Bureau will message you a migration link. A site that asks you to approve a contract for NFD before this page does is not this migration.

What is coming

  1. Exact one for one, both directions. No fee, no price impact, no slippage to set.
  2. Migrated NFD sits in escrow. Only a reverse migration can release it; there is no admin function that reaches it.
  3. The reverse direction cannot be paused. That is enforced by the contract, not by policy.
  4. The forward direction can be paused by the community multisig — for example while the Feisty Doge vault is in an auction. This page will say so when it is.
  5. Each transaction is capped by what the contract holds right now: BIC inventory going forward, NFD escrow going back. Both numbers will be shown live here, with advice to split anything larger.

What this page will check before it lets you sign

Before any button here can ask your wallet for anything, the page reads the contracts and confirms all of the following. If one fails, the page says so and stays read-only.

  • Reads come from Ethereum mainnet
  • Contract code at the migration address
  • Contract code at the BIC address
  • The migration contract takes NFD
  • The migration contract pays BIC
  • The migration contract uses the Uniswap v4 PoolManager
  • The migration contract is owned by the community multisig
  • BIC answers as BIC
  • BIC has 18 decimals
  • BIC supply is 100,000,000,000
  • BIC rescues to the community multisig
  • The NFD address answers as NFD
  • NFD has 18 decimals

What actually happens

  1. Approve. You let the migration contract take exactly the amount you typed — no more. This is a transaction of its own, and your wallet will show the number.
  2. Migrate. The contract takes that NFD into escrow and sends the same number of BIC to the same wallet, in one transaction. The rate is fixed in the code; there is no price and nothing to slip.

Redeeming is the same two steps with the tokens reversed. An approval for exactly the amount is used up by the migration, so the next one asks again. The Bureau never holds your tokens. Your wallet signs; the contract swaps.

Who controls what

The contract’s owner is the community multisig, 0x8569…cf39 ↗. It can pause forward migrations — for instance while the Feisty Doge vault is in an auction — and withdraw unused BIC inventory. It cannot change the pair, the rate, or reach the escrow. BIC itself has no owner at all. Anyone can fund the inventory; the treasury does so in tranches, which is why the forward capacity moves.

What was and was not reviewed

There is no external audit, and none is planned. The contracts are built on vetted open source — the Uniswap v4 and Solady code they vendor is byte-identical to upstream at pinned commits, and the BIC token is OpenZeppelin’s ERC-20 — and they are covered by their own test suite and by exercises against a fork of Ethereum mainnet. What no third party has reviewed is the escrow logic written for this migration: the ledger that holds migrated NFD, the settlement path, and the two entry points. That is the part that holds tokens.

The safety net in place of an audit is the pause lever above and the checks this page runs on every read. If you would rather wait and watch the contract before using it, that is a reasonable thing to do; the escrow is first-come but it is not a queue that closes.

Only the Ethereum mainnet NFD

The migration knows one token: NFD at 0xDFDb7f72c1F195C5951a234e8DB9806EB0635346 on Ethereum mainnet. The Base and Solana versions of Feisty Doge are not visible to it and cannot be migrated from here.

Where to read more

  • Source is published at launch.
  • Feisty Doge →The token being migrated, in the Bureau’s own records.
  • Feisty Doge on DeVamp ↗The authenticity review behind it, and the index this page used to live on.

DeVamp is at devamp.it ↗.