Go multichain today

XP.NETWORK JS API will get your NFT dApp or collection up and running on multiple chains faster than you can say ‘chain-agnostic’.

api api

Partners and integrated chains

Features

6 reasons to try XPJS API

WEB 3.0 JS API
EVM & non-EVM chains

XP.NETWORK supports 15+ blockchains - more than any other NFT bridge.

WEB 3.0 JS API
Support for all wallets

Let users connect and pay with any popular blockchain wallet - and with any cryptocurrency.

WEB 3.0 JS API
Multi-chain minting

Why choose on which chain to launch when you can mint on all of them?

WEB 3.0 JS API
New audiences

Reach out to the NFT crowds on other chains and boost your liquidity and sales.

WEB 3.0 JS API
Increased security

Our multi-layered security system can prevent even the most advanced attacks.

WEB 3.0 JS API
Turn-key solution

The API is supremely easy to integrate and use for any project.

Integration plan

Pick the perfect offer for your
needs

XP.NETWORK has integration plans for all NFT projects: from MVPs
to actively scaling ecosystems. Not sure what’s best for you? Ask us!

Standard

  • Up to 20K tx/annually
  • Dashboard & Analytics
  • Widget App
  • Coding guidelines
  • Unlimited Chains
  • ERC-721/1155 Standard
  • 3 consulting sessions
  • Support by available manager

Professional

  • Up to 100K tx/annually
  • Dashboard & Analytics
  • Widget App
  • Coding guidelines
  • Custom Wrapped NFT
  • Unlimited Chains
  • ERC-721/1155 Standard
  • Unlimited consulting sessions
  • Personal support manager

Custom

  • Unlimited
  • Dashboard & Analytics
  • Widget App
  • Coding guidelines
  • Custom Wrapped NFT
  • Unlimited Chains
  • ERC-721/1155 Standard
  • Unlimited consulting sessions
  • Personalized support
testimonials

Calling all modern-day
pioneers

All testimonials
Blockchain
dApps
View all testimonials

Frequently asked questions

In July 2021, we developed the first testnet bridge between Elrond and HECO. In August 2021, we transformed it into a multichain bridge, followed by several testnets: Ethereum Ropsten, BSC, Polygon Mumbai, Harmony, and Celo. Finally, in October 2021, we launched the bridge mainnet, connecting Ethereum, BSC, Polygon, Elrond, and Fantom. In November, we added Tron, Avalanche, and xDai; in December, Algorand and Fuse; and in January 2022, Velas and Tezos were joined. The latest additions, as of February 2022, are IoTeX and Harmony.

In 2021, interest in NFTs exploded: their sales grew from thousands of USD to hundreds of millions of USD per month. NFTs also expanded from Ethereum to other chains: BSC, Solana, Fantom, Avalanche, etc. However, NFT ecosystems on different blockchains remain insular and isolated. They can’t exchange assets or liquidity.

While there are lots of fungible token bridges (which are straightforward to build), there are very few NFT bridging solutions - and those that do exist connect only EVM chains (such as Ethereum and Polygon), or at most one non-EVM network (such as Solana or Elrond) to an EVM one. XP.NETWORK fills this gap, connecting all the isolated ecosystems both EVM and non-EVM into a global network of interoperable markets.

XP.NETWORK has two target groups of users:
1) Those who don’t code: NFT product owners, traders, investors, collectors, and artists/creators. They can use the simple and friendly interface at https://bridge.xp.network.
2) Developers: they can use the bridge JavaScript library at https://www.npmjs.com/package/xp.network.
The REST API service allows developers working with Python, Java, C#, C++, or any other programming language to use the bridge by calling POST requests with the function call parameters stored in the body of the requests. The service returns valid but unsigned transactions that users can sign and submit via third-party dApps.

What are the main use cases?

1. Cross-chain games: teams of players spread across the blockchains can collect NFT-based artifacts or mine resources and send them from one network to another.
2. Cross-chain marketplaces: platforms can save thousands of dollars and developer-hours by using our library to allow the users to buy NFTs issued on other chains and pay in a currency of their choice.
3. NFT projects wishing to gain global presence and maximize sales volume and liquidity.

The bridge already connects 10 EVM and 4 non-EVM networks.
EVM:

1.Ethereum
2.Binance Smart Chain
3.Polygon
4.Avalanche
5.Fantom
6.Velas
7.xDai
8.Fuse
9.Harmony
10.IoTeX

Non-EVM:

1.Elrond
2.Algorand
3.Tezos
4.Tron

EVM stands for Ethereum Virtual Machine - a major invention that differentiates Ethereum from Bitcoin. EVM allows developers to add and run third-party code on a live blockchain without stopping it. It uses Solidity, the first smart contract language.

All the chains that have adopted EVM support Solidity, the MetaMask wallet, Web3 tools, Ethereum’s JavaScript libraries, etc. The infrastructure built for one such chain can be reused on all the others with minimal changes, and their token standards are very similar.

Non-EVM blockchains use their own virtual machines, token standards, and smart contract language, such as Rust, C++, TEAL, Michelson, ink!, Plutus, etc. Such chains can have technical advantages over EVM networks, but few developers know the necessary languages, so building a non-EVM chain is very hard work.

Because of the complexity involved, there are very few non-EVM NFT bridges. That’s why the creation of such a bridge is a big event for the industry. XP.NETWORK is currently the only NFT bridge for Elrond, Tezos, and Algorand.

We're currently scaling the bridge relay validator network and working on minimizing target chain transaction fees. We've introduced and audited support for ERC-1155 smart contracts, custom collection names on target chains, and - for the first time in the history of the industry - transferring NFTs while retaining the logic of the original smart contracts.

In 2022, we plan to integrate several more important ecosystems, including Solana, EOS, NEAR, Cardano, and Cosmos.

Right now we’re building at breakneck speed; if the validators were already decentralized, they’d have to run upgrades every couple of days to catch up with the code updates. This is impractical and unsafe, since the team would have no guaranteed way to inform all the anonymous validators that they have to install an update - or to make sure they all do it.

Once the development pace slows down a bit, we will outsource bridge validation to third parties, incentivizing community members and industry influencers to further secure the bridge by decentralizing it.