This bounty is no longer available
Web3 DAO | vitelabs Logo

ViteBridge Explorer (Vuilder DAO Bounty)

Organization

vitelabs

Deadline

in over 262 years

Status

ENDED

3299.34 USD

INSTRUCTIONS

ViteBridge is the new cross-chain protocol by Vite Labs aiming at connecting every chain in a decentralized trustless manner. ViteBridge v0.1 has been released on the Vite testnet. We would like to have a ViteBridge Explorer built for all users to easily locate all their bridge transactions.

The ideal developer we are looking for is one that is capable of not only meeting all the following requirements but also interested in maintaining and iterating on the ViteBridge explorer in the long term. In addition to the current bounty payout, Vite Labs is interested in potentially some form of SBP sponsorship for the winning submission for their long term engagement with this project.

Bounty Prize

55,000 VITE

Requirements

ViteBridge v0.1 is currently deployed on both testnets of the Vite chain and the Binance Smart Chain (BSC). Therefore, the ViteBridge explorer should be integrated with both chains.

The following functionalities are required:

  • Search function: The ability to key in either VITE address or BSC address to search for ViteBridge records. The addresses can be either the senders' or the recipients'

  • List of ViteBridge Transactions (Exhibit 1). The list includes the following information.

  1. From: Sender’s address - this is clickable and linked to either ViteScan or BSCScan
  2. To: Recipient’s address - this is clickable and linked to either ViteScan or BSCScan
  3. Token: ViteBridge transaction asset
  4. Amount: the amount of the bridged asset, including 4-8 decimals
  5. Status: Includes three statuses: In Progress, Success, Failed. Only when transactions on both chains have completed would the status show as “Success“. The status should be “In Progress“ if the transactions are yet to be completed on either chain.
  6. Age: The time lapsed since the transaction took place
  7. Fees: ViteBridge transaction fee

1 Exhibit 1

  • Transaction Details (Exhibit 2). The details should have its own page and include the following information

Token

  1. Token - The token asset for the specific transaction.
  2. Amount - The transaction amount

From

  1. From - Address of the origin chain. It is clickable and directs the users to the respective explorer on ViteScan (ViteScan Address) or BscScan (BscScan Address)
  2. From chain logo - the logo of the origin chain located right after the address
  3. From Hash - Transaction hash on the origin chain. It is clickable and directs the users to the respective explorer address on ViteScan (ViteScan Hash) or BscScan (BscScan Hash)
  4. Status - Current transaction status on the origin chain. Obtain the transaction status from the block explorer
  5. Age - The time lapsed since the transaction took place
  6. Type - Locked or Unlocked. Locked for the origin chain and unlocked for the receiving chain. The bridged asset from the origin chain will be locked and the same amount of asset on the receiving chain is issued to the user (unlocked)

To

  1. To - Address of the receiving chain. It is clickable and directs the users to the respective explorer address on ViteScan (ViteScan Address) or BscScan (BscScan Address)
  2. To chain logo - the logo of the receiving chain located right after the address
  3. To Hash - Transaction hash on the receiving chain. It is clickable and directs the users to the respective explorer address on ViteScan (ViteScan Hash) or BscScan (BscScan Hash)
  4. Status - Current transaction status on the receiving chain. Obtain the transaction status from the block explorer
  5. Age - The time lapsed since the transaction took place
  6. Type:Locked or Unlocked. Locked for the origin chain and unlocked for the receiving chain. The bridged asset from the origin chain will be locked and the same amount of asset on the receiving chain is issued to the user (unlocked)

2 Exhibit 2

  • Switch network. The ability to support both Testnet and Mainnet.

Note

  • The exhibits are a reference only. Developers can create their own UI but they need to include all the functionalities listed above.
  • This service will require the continuing maintenance by the developer. The dev needs to run their own nodes.