omni / omnibridge-ui Goto Github PK

When the user selects Transfer, open the Confirm Transfer modal #9 to provide the details of the transfer to be approved.

• Check again for approved allowance
• Check again for enough balance

Replace "react-select" with PopOver component from chakra-ui to make the components looking uniform.
This also removes unwanted bulky "react-select"

I'm trying to cross the bridge with 10 STAKE and I'm getting this BigInt Error

This is mainnet, running in brave browser

i have add a custom token to swap but it show an error : 0x969ee7e66bd4f3b4460e957ca583a2e09fa84ddd

any idea why?

Lots of users are struggling with finding bridged tokens in their wallet since the MetaMask does not discover the tokens in sidechains automatically.

Consider to add the button "Add to MetaMask" (https://docs.metamask.io/guide/registering-your-token.html) in the part of the window where the bridged token is displayed and in the history tab.

noticed the popover arrow has a bit of an odd layering of the box shadow compared to the popover box the content lays in.

this:

Unlock the amount set to transfer with the approve() function on the token contract

• Show warning if the amount to transfer is higher than the user's balance

Also need hover effect for the icons.
For this need to convert .svg files to react components using createIcon from chakra-ui so that color can be changed from css.

Consider to use the gas price oralce library (https://github.com/peppersec/gas-price-oracle) instead of the Gas Price Oracle URL since it is more robust in case when the oracle URL is not available.

I’m sorry if this is basic to you all. But I used trust wallet to bridge Erc 20 tokens. Unfortunately I cannot interact with bridged tokens, as I can’t switch to xdai network with trust wallet.

Allow the user to add a custom token by address. Comes from Select Token Modal #7

• Look up the symbol and decimals for the contract
• Remember tokens added locally

Setup BridgeContext in BridgeTokens to share data/methods between different components such as FromToken, UnlockButton, TransferButton.

Consider to add an ability to configure several RPC URLs as part of the UI deployment parameters so they will be used as fallback interfaces if one RPC starts experiencing the issue (e.g. the Infura limit has been hit).

When the transfer completes, update the balance on the From side. Currently it remains the same and is updated when refreshing the page.

There is a request from third party applications to have an ability to specify a particular token and direction for transfer to be set when the OB UI is opened.

For example, if a project operates with a token X, it could have a link in their app like "Bridge X to Mainnet". When a user clicks on the link the OB UI must be opened where the required token on the xDai chain is chosen automatically (in the left side of the main window). The only thing the user must do is to specify the amount and press the transfer/request button.

BTW, the amount to transfer also could be part of the API request.

Tried to transfer MOONs from xDai to Ethereum Mainnet. The OB UI displays that fees will be collected as part of the transfer.

The MOONs tokens were added to the OB UI through the mechanism of overrides when a separate mediators are specified for a specific pair of tokens. The mediators responsible for transferring MOONs are not configured to collect fees.

This is the executed transfer on the Mainnet: eventually 1 MOON was transferred as it has been requested: https://etherscan.io/tx/0xe919c63b5c3482cf4eb523ff4081cb2769608219c11050bbdcdeb70955090f6d.

I'm having trouble getting the bridge to play nicely with the Gnosis Safe via walletconnect.

Connecting the safe to the bridge brings in the right balances and confirms the allowance, but sending the functions returns an error. Happens on both unlock and transfer calls currently.

• Connect via WalletConnect to Gnosis Safe
• switch to token (WETH)
• attempt to unlock max
• if unlocked, attempt to transfer (relay)

"invalid BigNumber value (argument="value", value=undefined, code=INVALID_ARGUMENT, version=bignumber/5.0.12)"

It makes sense to provide an ability to switch off the tokens balances update during the process of loading a token list since it could improve the user experience - the list of tokens will be loaded faster.

When the user confirms the transfer show a count of the necessary block confirmations

• Include a link to the ALM for the transaction
• Close on dismiss or add closer?

When a user selects a token, look up the balance on both networks and provide in the Transfer interface.

Currently system limits are being fetched along with balance on selecting a new token.
Can move this logic to onClick on System Feedback button

Retrieve the user's historical transactions on the current network and show them on the History page.

• Link to block explorer for the current network
• Need separate links for ALM and Etherscan?

Allow users to select a specific token on the "From" network, match the alternate on the corresponding network.

• Token list: https://github.com/raid-guild/default-token-list
• Search filters list down with a fuzzy match
• Add custom token opens custom token modal #8

Even if there's allowance available the current flow requires adding a new allowance with each page load. Instead lookup the allowance and check that against the current amount value.

If I choose a token which was not bridged yet the UI does not displays the limit and fees properly.

Consider to extract default values from the omnibridge contracts for limits and fees for not-yet-bridged tokens.

Consider to extend the "Settings" tab with a parameter which will allow to turn off the notifications about unclaimed transfers. If this parameter is enabled I will still get the request to claim an outstanding transfer but the notification will not appear if I open the app, switch the network, change the account in MM etc.

I just tried to send HNY from xDai to Mainnet in https://omnibridge-staging.web.app/

And when I try to approve, it doesn't do anything and throw an RPC metamask error in console

If a user A transfers a token and specifies an address B in the recipient address field the user B do not see this transfer on the history tab (therefore they cannot claim it).

Consider to implement the logic as so both the user A and the user B will be able to see in the history tab the transfers sent by using the alternative receiver feature. If some transfer is not finilized yet both users will need to have an ability to press the 'Claim' button.

Need to create an xDai tokenlist.org list for universal access

Here's the current default-token-list: https://github.com/raid-guild/default-token-list/blob/master/src/tokens/xdai.json

Need to create the schema here, upload to IPFS and point an ENS at it. Ross did a list for LexDAO here.
https://github.com/Uniswap/token-lists

Figure out if Honeyswap is using a list we should merge into.
http://tokens.honeyswap.org/

When I try to add a new custom token, I'm getting a few errors in the console. It won't let me copy/paste the address.

Errors;

explore if any public apis exist for this
if no comprehensive solution exists then discuss removing the dollar value from UI,
since it is 0 always currently.

Currently different URLs corresponds to different bridges although the same UI is used for all of them:

• Kovan-Sokol: https://sokol-omnibridge.web.app/
• ETH-xDai: http://omni.xdaichain.com/
• BSC-xDai: https://bsc-to-xdai-omnibridge.web.app/

Consider to provide an ability to the users to choose a bridge in the dropdown list near to the wallet information:

There was a conversation about dai bridging to xdai is a little confusing, the reason being that it is bridiging the erc20 token and not the xdai native token.

the solution discussed is to add a warning when DAI is selected.

For all networks: Fetch tokens from subgraph
For mainnet: Combine list fetched from subgraph with list on default-token-list repo
For all networks: (xdai & mainnet) get logo from default-token-list repo

Show the System transfer limits and usages on hover of System Feedback.

This makes it easier for

• fetching transactions based on an address
• pagination on history page

Currently it is hardcoded, this should be pulled from mediator

When users open the UI and the app is experiencing the issue with the RPC URL (e.g. the infura limit has been hit), the users has no ability to configure the alternative RPC since "Loading..." is displaying forever.

If the name of the token is really large, and amount value also is larger than 4-5 digits
then the amount value gets hidden and user has to move cursor over the input field to see the full amount.

possibly need to change design for this

This is so that you can change color on hover

When the user selects Transfer, confirm the details of the transfer in modal #14

• Continue submits the relay transaction to the current blockchain
  • on Ethereum Mainnet, relayTokens() will send the tokens to the mediator contract
  • on xDai, there's no approval necessary, call transferAndCall() to send to the xDai mediator contract.
• If the wrong network is connected, show the change network warning #6.
• On submit, show transaction confirmations #10

Currently we are using InfuraProvider for most read calls and using WalletProvider only for write calls.
In order to reduce the read calls on our InfuraProvider, we must move to using the WalletProvider whenever available.

Need to allow tokens to share a custom mediator and token implementation to be integrated into the bridge. When they share the mediator addresses and token addresses we should update the token list and mediator override.

• Need to look into how this affects the subgraphs

OWL custom mediator

{
    "homeBridge": {
        "homeBridgeMediator": {
            "address": "0xbeD794745e2a0543eE609795ade87A55Bbe935Ba"
        },
        "bridgeableErc677": {
            "address": "0x0905Ab807F8FD040255F0cF8fa14756c1D824931"
        }
    },
    "foreignBridge": {
        "foreignBridgeMediator": {
            "address": "0xed7e6720Ac8525Ac1AEee710f08789D02cD87ecB"
        },
        "bridgeableErc20": {
            "address": "0x1a5f9352af8af974bfc03399e3767df6370d82e4"
        }
    }
}

We need to warn the user when they set a network on the application but their wallet is set to another wallet.

The developer instance implements this when attempting to send the relay.