Migrate NFD to BIC

Choose a wallet

Direction

Holds — · —

NFD 0xDFDb7f72c1F195C5951a234e8DB9806EB0635346 BIC 0xB1cDa04D7cD5584048ab48B42b629aEC34D3b562

Do not send tokens to any of these addresses. Migrating is the two wallet prompts above; a plain transfer does nothing. Anything sent directly to the migration contract 0x78d1A97a9239443070BE0353C68762CCCF64a888 cannot be recovered, by us or by anyone.

Two wallet prompts: an approval, then the migration. The approval should show the spender as 0x78d1…a888 and exactly the amount you typed — if it shows anything else, reject it.

Migrations so far

Reading the log…

How it works · what can be paused · no external audit

What actually happens

  1. Approve. The contract may take exactly the amount you typed, no more.
  2. Migrate. That NFD goes into escrow and the same number of BIC comes back, in one transaction.

Redeeming is the same two steps reversed. One for one, no fee, nothing to slip. The Bureau never holds your tokens.

Who controls what

The owner is the community multisig, 0x8569…cf39. It can pause forward migration and withdraw unused BIC. It cannot pause redeeming, change the rate, or reach the escrow. BIC itself has no owner at all.

No external audit

There is no external audit, and none is planned. The vendored Uniswap v4, Solady and OpenZeppelin code is byte-identical to upstream at pinned commits, and there is a test suite and mainnet-fork exercises. What no third party has reviewed is the escrow logic written for this migration — the part that holds tokens. Waiting and watching the contract first is a reasonable thing to do.

Only the Ethereum mainnet NFD

One token: 0xDFDb7f72c1F195C5951a234e8DB9806EB0635346. The Base and Solana versions of Feisty Doge cannot be migrated here.

Where to read more

DeVamp is at devamp.it.