> For the complete documentation index, see [llms.txt](https://docs.sphera.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sphera.world/nft-bridge/faq.md).

# Bridge FAQ

Common questions about the Sphera NFT Bridge.

## General

### Is the bridge safe?

Yes. The bridge uses secure smart contracts:

* On Hedera: Your NFT is **locked** (not burned) in a LockBox contract
* On Avalanche: A **wrapped version** is minted that you control
* You can always bridge back to recover your original NFT

### What happens to my NFT when I bridge?

**Hedera → Avalanche:**

* Your original NFT is locked in a secure contract on Hedera
* A wrapped NFT with identical metadata is minted on Avalanche
* The wrapped NFT is sent to your specified address

**Avalanche → Hedera:**

* Your wrapped NFT is burned on Avalanche
* Your original NFT is unlocked on Hedera
* The original NFT is sent to your specified address

### Can I bridge to a different wallet?

Yes! When bridging, you can specify a different destination address. This is useful for:

* Sending to a friend
* Moving to a different wallet you control
* Consolidating NFTs

## Wallets

### Why do I need two wallets?

* **HashPack** is needed for Hedera transactions (lock/unlock)
* **MetaMask** is needed for Avalanche transactions (mint/burn)

Both wallets must be connected for the bridge to work.

### Can I use wallets other than HashPack?

Currently, HashPack is the recommended wallet for Hedera. We may add support for other Hedera wallets in the future.

### Can I use wallets other than MetaMask?

Yes! Any EVM-compatible wallet works for Avalanche, including:

* MetaMask
* Rabby
* Rainbow
* WalletConnect-compatible wallets

## Fees & Timing

### How much does bridging cost?

| Direction          | Network Fee       |
| ------------------ | ----------------- |
| Hedera → Avalanche | \~1-2 HBAR        |
| Avalanche → Hedera | \~0.005-0.01 AVAX |

Fees may vary based on network congestion.

### How long does bridging take?

Typically 10-30 seconds for either direction. The process includes:

1. Your transaction on the source chain
2. Bridge verification
3. Transaction on the destination chain

### Why is my transaction taking longer?

Possible reasons:

* Network congestion
* Wallet connection issues
* Browser/extension issues

Try refreshing the page or reconnecting your wallet.

## Troubleshooting

### My NFT is stuck / not appearing

1. **Wait a few minutes** - Blockchain indexing can take time
2. **Refresh the page** - The UI may need to reload
3. **Check explorers**:
   * [HashScan](https://hashscan.io) for Hedera
   * [Snowtrace](https://snowtrace.io) for Avalanche
4. **Contact support** if stuck for more than 10 minutes

### I bridged but didn't receive my NFT

This is rare but can happen if:

* Network issues interrupted the bridge
* The mint/unlock transaction failed

Contact support on [Discord](https://discord.gg/ny4uKYPYfx) with your transaction hash and we'll help recover your NFT.

### The bridge says "Transaction failed"

Common causes:

* **Insufficient gas** - Make sure you have enough HBAR/AVAX
* **Wrong network** - Ensure MetaMask is on Avalanche (not Ethereum)
* **Wallet not connected** - Reconnect both wallets

### Can I cancel a bridge in progress?

Once a lock/burn transaction is confirmed, it cannot be cancelled. The bridge will complete the process automatically.

## Technical

### What are the contract addresses?

**Hedera Mainnet (LockBox):**

| Collection     | Address                                      |
| -------------- | -------------------------------------------- |
| Sphera Amateur | `0x1018E39bc165a0c3CeB0001f466344d4139e9c68` |
| Sphera Fan     | `0xe5C5b7ab701573eF0ADBf831C1F95Fb9723A3856` |
| Sphera Ultras  | `0x47A22f1587809A0060Fd64527b489D48B8dfeFB1` |
| Legacy Pass    | `0x71F295437F9A064E5ae65E6890a380f0efC31D02` |
| Annual Pass    | `0x48A8684B279A132F2eCd021db9d63ecdccbC15B9` |

**Avalanche Mainnet (WrappedNFT):**

| Collection     | Address                                      |
| -------------- | -------------------------------------------- |
| Sphera Amateur | `0xeF707625603652520ee77b14cd6C13BBbD6275C0` |
| Sphera Fan     | `0xCFf5A923c5D427F7fc156F672CE08E562D5474C6` |
| Sphera Ultras  | `0xA0Fc7Be4D48Ec8196a57Ab86267A89EDB30237A3` |
| Legacy Pass    | `0x1018E39bc165a0c3CeB0001f466344d4139e9c68` |
| Annual Pass    | `0x47A22f1587809A0060Fd64527b489D48B8dfeFB1` |

### Is the bridge code open source?

The bridge frontend is available at [github.com/Deca4Advisory-Code/sphera-layerzero-nft-bridge](https://github.com/Deca4Advisory-Code/sphera-layerzero-nft-bridge).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sphera.world/nft-bridge/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.