# Bridge NFT

## NFT bridge with HyperLane

The main NFT network is Ethereum chain. User can move his NFT to other chain both on mint and at any time he wants. Bridge is always signed and payed by user.

## Bridge details

HyperLane expects besides main NFT contract `ScaleyValleyCollection` additionaly `HypCollateral721` contract at the same Ethereum chain. On the other chains `Hyp721` contract is enough. The main reason for user to bridge is to gain some boosters of perks:

<table><thead><tr><th width="126">Network</th><th width="126">Valley name</th><th width="218">Contract name</th><th>Feature</th></tr></thead><tbody><tr><td>Ethereum</td><td>EtherValley</td><td>ScaleyValleyCollection</td><td><p>When token is on this chain </p><p>NFT's <strong>level</strong> increases </p></td></tr><tr><td>Polygon</td><td>PolyValley</td><td>Hyp721</td><td><p>When token is on this chain </p><p>NFT's <strong>agility</strong> increases </p></td></tr><tr><td>Optimism</td><td>OptiValley</td><td>Hyp721</td><td><p>When token is on this chain </p><p>NFT's <strong>intellect</strong> increases</p></td></tr></tbody></table>

## Bridge frontend

User can "travel" through the Valleys by bridging it from one Valley-chain to another. This is performed on **Valley travel** panel

## Step 1 - Join the marketplace

This is performed by simple metamask authentication

## Step 2 - Select one of user's tokens

On **Valley travel** panel user sees all his NFTs he can bridge.

## Step 3 - Select destination chain

User selects destination Valley-chain.

## Step 4 - Aprove in Metamask

User approves his intention to bridge using HyperLane technology

## Step 5 - Wait for confirmation

Bridge will confirm user about the end of briding process.