Versions Compared

Old Version 11

changes.mady.by.user Eric Butz

Saved on

compared with

New Version 12

changes.mady.by.user Eric Butz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

The FIO Wrapping Status Page is a publicly hosted landing page(s) which display current activity of tokens and domains being wrapped. It collects information from FIO Chain and Destination Chains (Ethereum, Polygon). The FIO Oracle only monitors events on the FIO and Ethereum chains and takes wrapping actions and does NOT have any retry or historical lookup functionality. So, we need a way to monitor which transactions have failed so manual action may be taken by the oracle block producers. The FIO Wrapping Status Page provides that functionality.

Functional specification

...

Architecture

UI

Development setup

Content

Custodians

Displays currently registered custodians on each destination chains.

...

The Wrapping status application will need to store wrap information so it does not constantly need to be querying the chains for old data.

FIO table

  • action (wrap/unwrap)

  • type (token/domain) (not sure if this is needed?)

  • FIO transaction_id

  • timestamp

  • actor

  • chaincode

  • amount

  • nftname

  • pubaddress

ETH table

  • action (wrap/unwrap)

  • type (token/domain) (not sure if this is needed?)

  • ETH transaction_id

  • From ETH address (the ETH address of the BP doing the approval)

  • Input data:

    • account

    • amount

    • obtid (This is the FIO transaction ID)

...

Wrap

2022/04/27 11:03 fio@faucet Ethereum wraptoken 100.000000000 FIO Pending

Or

2022/04/27 11:03 fio@faucet Polygon wrapnft mydomain Completed

FIO Chain Transaction

e1610cd98fb8695e85e1055327799be4e9ff3c23eb6f5bc60bc4fabcdb62ebe3 (links to bloks.io) Sent

Recipient Address

0x6470204c5741d73f2f0b3a762ad5356436b8b470015159a89414cbf2f3b61b2d (links to etherscan or polyscan)

Destination Chain Approvals

hfdg2qumuvlc (link to ETH transaction) Wrapped

qbxn5zhw2ypw) (link to ETH transaction) Wrapped

wttywsmdmfew) (link to ETH transaction) Wrapped

Header

  • timestamp

  • crypto handle

  • chain

  • Depending on wrap type:

    • Amount: <amount>

    • NFT: <nftname>

  • Status (Completed or Pending)

Examples:

2022/04/27 11:03 fio@faucet Ethereum 100.000000000 FIO Pending
2022/04/27 11:03 fio@faucet Polygon mydomain Completed

FIO Chain Transaction

  • FIO chain transaction ID linked to bloks.io

Recipient Address

  • ETH public_address linked to etherscan

Destination Chain Approvals

For each transaction: (this can all be in one line)

  • BP Crypto Handle

  • Timestamp

  • ETH transaction ID linked to etherscan

  • FIO Chain

    • For Wrapping, the token wraps are submitted to the FIO Chain by the user.

    • The following information is stored in the fio.oracle oracleldgrs table:

...

FIO Domains needed burning

This is a version 2 feature and does not need to be done for the initial release.

  • FIO Domains which have been burned on FIO Chain, but not on Destination Chain

    • Domains which have expired will be burned (deleted) after a certain amount of time. If someone has wrapped a domain and it gets "burned" we want to be able to note that in the Wrapping Status Page, so action can be taken on the Ethereum side.

    • fio_domain

    • date_burned

    • Link to etherescan for ERC-721 token ID