wbanano / wban-dapp Goto Github PK

Just requesting a refresh button on the farm page (https://bsc.banano.cc/farms).
I know I could use my browser/F5 but I think a button would be nicer and hopefully take less time and data.
Cheers!
Great work!

add an pending withdrawal balance, and also add a notification to the user don't doing withdraw request multiple times

It's hard to guess that you have to click on the "Connect" link in the toolbar.

The amount of the old withdrawn amount should be seen anymore.

This would solve the bad UX through which the max value can put the form data to be invalid.

Add little info symbols (i) to crypto related vocabulary. Could be a button to click or hover icon. I would place one for example besides the total supply statistic (top left hand info box).
People could hover or click on the "i" to read what those numbers mean. This could help even if most number are selfexplanatory, not everybody knows their way around exchanges and crypto in general ....

Even better: display a notification telling him that his deposit was rejected and sent back.

For displaying info to the user regarding Banano accounts and transactions this can be done directly from a browser in a "dapp" manner without the need for public block explorers.
IE the Linuxserver wallet plugs into any Banano or Nano RPC node:
Account View:
https://wallet.linuxserver.io/#/kaliumapi.appditto.com/address/ban_1bananobh5rat99qfgt1ptpieie5swmoth87thi74qgbfrij7dcgjiij94xr

Direct Link to transaction:
https://wallet.linuxserver.io/#/kaliumapi.appditto.com/block/6008056C9B3742A52E3F2A06D006D885DC85F83710D610DDC9BD3F9FE159B772

The code to grab the data is pretty simple and the wallet allready has Vue based logic for rendering it out:
https://github.com/linuxserver/nano-wallet/blob/master/src/store/app/actions.js#L117-L135

In my wallet I have a very small amount of wBAN remaining, but this small amount appears to cause a UI display issue on the wrap/unwrap screen where it displays the following:

As you can see it's showing "NaN wBAN" instead of something prettier.

Steps to reproduce:

1. Log fully into wBAN app on desktop (make sure to assign a banano address, sign transactions, etc)
2. Log into wBAN app on mobile metamask, choosing the same banano address.
3. Perform a swap on mobile metamask.
4. Desktop will see the success messages destined for the mobile client (BAN address is unique identifier)
5. Mobile metamask will continue to show "swap in progress" unless you refresh the page, but upon refresh the balances are correct.

Screenshot showing wBAN notification on mobile spinning indefinitely:

Screenshot showing notification received on desktop even though the swap was initiated on mobile:

Currently there is something missing in the Vue app and when we reload "/farm" we get a 404 error.

As a user I would I want the ability to change my associated banano address in case I lose access to it or decide to change my address for other reasons. We'd want to make sure the user is not trying to impersonate someone else so the same wallet-association process would need to be performed again.

This would bring focus to that app when a request (deposit/withdrawal/swap) has been processed.

The form does not allow to withdraw 0.6 BAN for example:

It could be interesting to add a waiting screen similar to the swap waiting screen when adding BNBs for fees.

Doing a first-time setup by adding the BSC mainnet with MM brings the message "You're not on the mainnet but !" (which disappears after refreshing)

Swap buttons are confusing, I suggest renaming the app's Banano <-> wBan button with "wrap" and "unwrap", depeding on the direction of the "swap"

It does not really makes sense to keep this besides test sessions because in live situation the pool would run for a very long time.

... based on CoinGecko's API.

This is given Discord is the chosen community for this project.
The app should have a link to the discord community along with README.md.
Badge example for Labs Server:

https://img.shields.io/discord/710222836660437045.svg?color=ffff00&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=Discord&logo=discord

When the user is swapping BAN for wBAN, if they sign in the first step then reject the transaction, user's BAN stays in limbo. This shouldn't be the case since the user rejected the transaction. So the whole process can be cancellable after step 1 and before step 2.

I swap wban back but stuck at the loading screen, the transaction is success but balance does not appear on the website (I use metamask mobile app)

But only after #20 is done!

Please make the history button a lot more prominent and explain the process of claiming the rejected transactions to users in 'Help' section or something like that.

Hi monkes,
I believe the success of this project will rely on every aspect of it. And the user interface is no exception.
I'm a 10+ years front-end / vue.js / react developer and I saw this app was using vue. So I'm willing to give some of my time if you guys need help. Here's what I could do:

• Work on some existing pages and tidy up, add slick animations, give it a smoother general feeling
• Make suggestions on some aspects of the user experience
• Create new pages that you guys still haven't made

Let me know,
Peace

PancakeSwap API (https://api.pancakeswap.info/api/v2/tokens) has not up-to-date prices.

Probably best to fetch all prices from CoinGecko:
https://api.coingecko.com/api/v3/simple/price?ids=banano,busd,binancecoin&vs_currencies=usd

Maybe add a function to send back bnb deposited for fees.

Because of the monkey background, depending on your screen size the history button becomes extremely hard to see:

See https://github.com/yurishkuro/opentracing-tutorial/tree/master/nodejs

This would work in tandem with the backend support for OpenTracing.

The dApp rounded up rather than down when I tried to unwrap wBAN and raised an error "Not enough wBAN available!"

If you click the swap button, then reject the transaction using MetaMask, UI doesn't indicate that the transaction was rejected. Instead it stays in the "waiting" state:

When someone clicks "Connect" then "Web3 wallet", if there is not Web3 compatibility nothing happens.
Some instructions should be displayed to the user.