PUNKERBUNKER

PunkerBunker guide

How it works

PunkerBunker combines two things: checking your bunker wallet for public-key exposure and moving selected NFTs from your current wallet in bulk.

Why move to a bunker wallet?

The concern is a possible future attack that could break the cryptography used by wallets. An exposed public key could be used in such an attack to forge signatures.

On Ethereum and Base, moving NFTs to a new bunker wallet that has never signed and whose public key has not been exposed may reduce exposure to this particular risk. This is a temporary precaution. It does not fix the underlying cryptography or guarantee that the wallet will stay secure.

Bitcoin and other chains need their own checks. This explanation applies to the Ethereum and Base workflow.

Read the original discussion: Justin Drake’s post and Vitalik Buterin’s post.

The transfer steps

  1. Check your bunker wallet first

    Choose the transfer network. Use wallet software or a hardware wallet you trust. Create a new bunker wallet that has never signed a transaction or message. Do not reuse a wallet whose public key has already been exposed. Check the full address in your wallet or on your hardware device.

    PunkerBunker checks for address errors and known signing activity. Blockchain history cannot tell us about every signature made elsewhere. Incomplete or unsupported checks stop the process here. The bunker wallet does not connect to PunkerBunker or sign anything.

  2. Enter your current wallet

    After the bunker wallet passes the first check, enter the current wallet address that holds your NFTs. The two wallet addresses must be different. Entering an address does not require a connection or a signature.

  3. Confirm the address with a small ETH payment

    Send the exact amount shown from your current wallet to your bunker wallet, separately. PunkerBunker checks that payment. You must also confirm that it appears in your own bunker wallet.

    The ETH stays there. It is not the service fee. Do not send it back. This test helps catch a wrong address; it does not prove that you control the private key.

  4. Choose the NFTs to move

    After the address test, scan your current wallet and select individual NFTs or whole collections. Scanning only reads public wallet information. Sort by name or estimated value. Unknown values are marked as unknown.

  5. Review the transfer

    Check the bunker wallet address, selected NFTs, transfer order, number of transactions, and estimated costs. The planned service fee is 0.01 ETH for the entire migration on Ethereum or Base, plus network fees. Nothing is charged in the sample.

  6. Test with one NFT, then transfer the rest in bulk

    You can send a lower-value selected NFT first. Check it in your bunker wallet before continuing. The remaining NFTs are grouped into batches and transferred in the order you approved. A batch may require more than one transaction or wallet confirmation.

    Only your current wallet signs transfer transactions. If you change the address or selected NFTs, review and approve the remaining plan again.

  7. Check the results and save your progress

    Each transfer must be confirmed before it is marked as received. You can pause, save a record, and resume. Completed transfers are excluded from the remaining plan. Restoring a record requires new checks.

What if the bunker wallet has already signed?

You can choose another wallet. Or you can explicitly agree to a standard transfer to the used wallet. That transfer does not provide the public-key precaution described above. The address and delivery checks still apply.

Past signing does not mean the wallet has been hacked.

What can you try now?

The sample includes NFT selection, new and used bunker wallets, an example ETH payment, cost review, an NFT test, batches, pause and resume, and saved records. All results are simulated.

Ethereum and Base are the first networks in the interface. Original CryptoPunks, Bitcoin Ordinals, and Tezos transfers are still being built.