Cross-Chain NFT Burn and Mint Bridge Tool

WHAT IT DOES

This tool provides complete visibility and execution capabilities for bridging NFTs across different chains using a burn-and-mint mechanism. It reads and displays source NFT collection name and symbol, your owned token IDs with their metadata URIs, total supply and max supply on both chains, destination NFT collection info, bridge contract paused state, relayer operational status, mint status for burned tokens, your bridge history count, and estimated gas costs on both chains. Beyond read-only access, the tool lets you execute the four key actions: approve the bridge to burn your NFTs (setApprovalForAll), burn and bridge individual NFTs, burn and bridge multiple NFTs in a single batch transaction, and claim minted NFTs on the destination chain after the relay completes.

HOW TO USE

Connect your EVM-compatible wallet using the top-right connect button. Select your source and destination networks, then enter the source NFT contract, source bridge contract, destination NFT contract, and destination bridge contract. Enter the token IDs you wish to bridge (comma-separated) and click "Load NFT State" to fetch all current data. Review your owned tokens, their metadata URIs, collection supply, bridge state, and relayer status. If you haven't already approved the bridge, click "Approve Bridge" to grant permission (this is a one-time setApprovalForAll). To bridge a single NFT, enter one token ID and click "Burn & Bridge." To bridge multiple NFTs, enter several token IDs and click "Batch Bridge" — this burns all source NFTs and initiates the cross-chain transfer in one transaction. After the relayer processes the burn, click "Claim on Dest" to mint the equivalent NFTs on the destination chain. Each transaction shows confirmation and gas cost reporting.

TECHNICAL MECHANISM — CHUNKED LOG SCANNING WITH OWNERSHIP VERIFICATION

Most NFT bridging tools either poll a single RPC range or assume the relayer will always complete the mint, both of which break under real conditions. This tool combines direct state reads with chunked history scanning for burn events and bridge history. It fetches collection metadata, supplies, owned token IDs, and metadata URIs via direct contract calls, then retrieves historical bridge events by scanning for NFTBurned and NFTMinted events. The log scanner walks backwards in 10,000-block chunks and, if any chunk fails due to rate limiting or timeout, it halves the chunk size for that specific range and retries — never aborting the entire scan. For owned token verification, the tool iterates through tokenOfOwnerByIndex and confirms ownership against the current ownerOf() state, ensuring the displayed tokens are actually held. After scanning, the tool re-reads the bridge's paused state and relayerActive() flag to confirm the displayed values match the latest on-chain state.

WHAT IT CANNOT SEE

This tool cannot verify that the destination chain's minted NFT accurately reflects the source NFT's metadata, nor that the metadata URI remains accessible or unchanged after bridging. It relies entirely on the bridge contract's verification of relayed burn data and the destination chain's final state. It cannot detect if the metadata URI points to a malicious or offline server, if the creator can alter metadata after minting, if the bridge operator has frozen claims, if the destination NFT contract has been compromised, or if there are hidden royalties or fees not reflected in the bridge parameters. The tool also cannot see if the destination chain's finality has been reorganized after the mint, if the bridge has sufficient liquidity, or if the relayer is executing honestly. It reports what the contracts say, but does not validate the authenticity, security, or trustworthiness of any NFT collection, metadata, or bridge infrastructure.

PLEASE NOTE — EVM CHAINS ONLY

This tool supports all EVM-compatible networks that the BotSurf wallet bridge connects to — Ethereum Mainnet, Polygon, Optimism, Arbitrum, Base, and similar chains. Non-EVM chains like Solana, Cosmos, Sui, or Aptos are not supported. The NFT contracts must implement the standard ERC-721 interface with name(), symbol(), totalSupply(), maxSupply(), balanceOf(), tokenOfOwnerByIndex(), tokenURI(), ownerOf(), approve(), setApprovalForAll(), and isApprovedForAll() — contracts using custom NFT standards (e.g., ERC-1155, non-standard enumeration) will not display correctly. The bridge contract must implement burnAndBridge(), burnAndBridgeBatch(), claim(), claimBatch(), paused(), relayerActive(), estimateGasBurn(), estimateGasClaim(), and userBridges(). The tool is read-write: it signs transactions when you execute approval, burn & bridge, batch bridge, or claim actions. Always verify contract addresses, token IDs, and bridge parameters before submitting any transaction.