Bridge

You can bridge an NFT or contracts from the source network to the destination network.

Bridge NFT

When run without any flags, you will be asked to enter the contract address and tokenId, and network information.

Usage

holograph bridge:nft

Help Output

USAGE
  $ holograph bridge:nft [--collectionAddress <value>] [--tokenId <value>] [--sourceNetwork
    seiTestnetArctic|lineaTestnetSepolia|mantleTestnetSepolia|lineaTestnetGoerli|zoraTestnetSepolia|baseTestnetSepolia|a
    rbitrumTestnetSepolia|optimismTestnetSepolia|ethereumTestnetSepolia|mantleTestnet|polygonTestnet|avalancheTestnet|bi
    nanceSmartChainTestnet] [--destinationNetwork seiTestnetArctic|lineaTestnetSepolia|mantleTestnetSepolia|lineaTestnet
    Goerli|zoraTestnetSepolia|baseTestnetSepolia|arbitrumTestnetSepolia|optimismTestnetSepolia|ethereumTestnetSepolia|ma
    ntleTestnet|polygonTestnet|avalancheTestnet|binanceSmartChainTestnet] [--env mainnet|testnet|develop|experimental]

FLAGS
  --collectionAddress=<value>    The address of the collection smart contract
  --destinationNetwork=<option>  The destination network which to bridge to
                                 <options:
                                 seiTestnetArctic|lineaTestnetSepolia|mantleTestnetSepolia|lineaTestnetGoerli|zoraTestne
                                 tSepolia|baseTestnetSepolia|arbitrumTestnetSepolia|optimismTestnetSepolia|ethereumTestn
                                 etSepolia|mantleTestnet|polygonTestnet|avalancheTestnet|binanceSmartChainTestnet>
  --env=<option>                 [default: testnet] Holograph environment to use
                                 <options: mainnet|testnet|develop|experimental>
  --sourceNetwork=<option>       The source network from which to bridge
                                 <options:
                                 seiTestnetArctic|lineaTestnetSepolia|mantleTestnetSepolia|lineaTestnetGoerli|zoraTestne
                                 tSepolia|baseTestnetSepolia|arbitrumTestnetSepolia|optimismTestnetSepolia|ethereumTestn
                                 etSepolia|mantleTestnet|polygonTestnet|avalancheTestnet|binanceSmartChainTestnet>
  --tokenId=<value>              The token ID of the NFT to bridge

DESCRIPTION
  Bridge a Holographable NFT from one network to another.

EXAMPLES
  $ holograph bridge:nft --sourceNetwork="ethereumTestnetSepolia" --destinationNetwork="avalancheTestnet" --collectionAddress="0x1318d3420b0169522eB8F3EF0830aceE700A2eda" --tokenId="0x01" --env mainnet|testnet|develop|experimental

See code: src/commands/bridge/nft.ts

Flags

--address

This is the address of the contract of the NFT. The contract must be a holographable contract, otherwise an error is thrown

--collectionAddress

The collection Address is the address of the collection

--destinationNetwork

The destination network is where the NFT will end up after the TX is submitted. The only acceptable values are:

1. seiTestnetArctic
2. lineaTestnetSepolia
3. mantleTestnetSepolia
4. lineaTestnetGoerli
5. zoraTestnetSepolia
6. baseTestnetSepolia
7. arbitrumTestnetSepolia
8. optimismTestnetSepolia
9. ethereumTestnetSepolia
10. mantleTestnet
11. polygonTestnet
12. avalancheTestnet
13. binanceSmartChainTestnet

--sourceNetwork

The source network is where the NFT currently lives on. The command will do some validation to make sure the NFT exists on the source network. The only acceptable values are:

1. seiTestnetArctic
2. lineaTestnetSepolia
3. mantleTestnetSepolia
4. lineaTestnetGoerli
5. zoraTestnetSepolia
6. baseTestnetSepolia
7. arbitrumTestnetSepolia
8. optimismTestnetSepolia
9. ethereumTestnetSepolia
10. mantleTestnet
11. polygonTestnet
12. avalancheTestnet
13. binanceSmartChainTestnet

--tokenId

This is the id of the token on the blockchain.

--env

The network is the network the operator will bond to. The only acceptable values are: ['testnet', 'develop', 'experimental']. Until the holograph mainnet deployment, the CLI will default to the testnet environment.

Bridge Contract

When run without any flags, you will be asked to enter the contract address and tokenId, and network information.

Usage

holograph bridge:contract

Help Output

USAGE
  $ holograph bridge:contract [--sourceNetwork
    seiTestnetArctic|lineaTestnetSepolia|mantleTestnetSepolia|lineaTestnetGoerli|zoraTestnetSepolia|baseTestnetSepolia|a
    rbitrumTestnetSepolia|optimismTestnetSepolia|ethereumTestnetSepolia|mantleTestnet|polygonTestnet|avalancheTestnet|bi
    nanceSmartChainTestnet] [--destinationNetwork seiTestnetArctic|lineaTestnetSepolia|mantleTestnetSepolia|lineaTestnet
    Goerli|zoraTestnetSepolia|baseTestnetSepolia|arbitrumTestnetSepolia|optimismTestnetSepolia|ethereumTestnetSepolia|ma
    ntleTestnet|polygonTestnet|avalancheTestnet|binanceSmartChainTestnet] [--deploymentConfig <value>] [--env
    mainnet|testnet|develop|experimental]

FLAGS
  --deploymentConfig=<value>     The config file to use
  --destinationNetwork=<option>  The network on which the contract will be deployed
                                 <options:
                                 seiTestnetArctic|lineaTestnetSepolia|mantleTestnetSepolia|lineaTestnetGoerli|zoraTestne
                                 tSepolia|baseTestnetSepolia|arbitrumTestnetSepolia|optimismTestnetSepolia|ethereumTestn
                                 etSepolia|mantleTestnet|polygonTestnet|avalancheTestnet|binanceSmartChainTestnet>
  --env=<option>                 [default: testnet] Holograph environment to use
                                 <options: mainnet|testnet|develop|experimental>
  --sourceNetwork=<option>       The network from which contract deploy request will be sent
                                 <options:
                                 seiTestnetArctic|lineaTestnetSepolia|mantleTestnetSepolia|lineaTestnetGoerli|zoraTestne
                                 tSepolia|baseTestnetSepolia|arbitrumTestnetSepolia|optimismTestnetSepolia|ethereumTestn
                                 etSepolia|mantleTestnet|polygonTestnet|avalancheTestnet|binanceSmartChainTestnet>

DESCRIPTION
  Bridge a Holographable contract from source chain to destination chain. You need to have a deployment config JSON
  file. Use the "contract:create" command to create or extract one.

EXAMPLES
  $ holograph bridge:contract --sourceNetwork="ethereumTestnetSepolia" --destinationNetwork="avalancheTestnet" --deploymentConfig="./MyContract.json" --env mainnet|testnet|develop|experimental

See code: src/commands/bridge/contract.ts

Flags

--deploymentConfig

This is a holograph configuration file used to make deploy a collection easy. The only acceptable values are: ['deployedTx', 'deploymentConfig']

--destinationNetwork

The destination network is where the NFT will end up after the TX is submitted. The only acceptable values are:

1. seiTestnetArctic
2. lineaTestnetSepolia
3. mantleTestnetSepolia
4. lineaTestnetGoerli
5. zoraTestnetSepolia
6. baseTestnetSepolia
7. arbitrumTestnetSepolia
8. optimismTestnetSepolia
9. ethereumTestnetSepolia
10. mantleTestnet
11. polygonTestnet
12. avalancheTestnet
13. binanceSmartChainTestnet

--sourceNetwork

The source network is where the NFT currently lives on. The command will do some validation to make sure the NFT exists on the source network. The only acceptable values are:

1. seiTestnetArctic
2. lineaTestnetSepolia
3. mantleTestnetSepolia
4. lineaTestnetGoerli
5. zoraTestnetSepolia
6. baseTestnetSepolia
7. arbitrumTestnetSepolia
8. optimismTestnetSepolia
9. ethereumTestnetSepolia
10. mantleTestnet
11. polygonTestnet
12. avalancheTestnet
13. binanceSmartChainTestnet

--env

The network is the network the operator will bond to. The only acceptable values are: ['testnet', 'develop', 'experimental']. Until the holograph mainnet deployment, the CLI will default to the testnet environment.

General Errors

1. The source network and destination network must be different.