A backend server for the Multichain NFT Bridge Explorer
Explore the docs »
View Explorer (Staging Version)
·
View Bridge (Main Version)
Table of Contents
Multichain NFT Bridge Explorer gives the end client an indication of what is happening with his transaction.
By saving all the transactions data on our mongoDB we are able to serve and display the following information:
- Departure chain name
- Destenation chain name
- Departure hash
- Destenation hash
- Tx-fees
- Tx-value
- Age
- Method
- Status
- Sender address
- Target address
- Nft uri
- Collection name
- Collection contract address
- Token-id
and more....
THIS IS THE SERVER SIDE
On this repo you will find a controller that routs by urls working with a buisness-logic file that connects directly to the DB, you will find A big file named "listenrs" wich is devided to EVM's and non EVM's. Each file holds a document that is manages his relevant socket.
there are 2 main socket listeners on each file : One that is listening to a Freez entry point and another that is listening to a Withdraw, these entry point are defined on the contract itself.
- Express
- Ethers
- Taquito- Tezos
- Socket-Io
- Web3-eth
- Tron Web
- xpnet-web3-contracts
- Mikro Orm
- MongoDB
- Compass
Make sure to go by the following instructions:
This is an example of how to list things you need to use the software and how to install them.
- nodeJs
- yarn
- recommended compass
- .env File
- make sure you have all prerequisites
- Clone the repo
git clone https://github.com/XP-NETWORK/bridge-explorer.git
- Install Yarn packages
yarn install
- Insert the .env file to the root dir.
- on index.ts line 30 change listen to false , and make sure you understand why.
- run tsc && nodemon src/index.ts.