Just some type of heads up for new users about the UST situation and a recommendation to swap to Luna before they withdraw their UST to their Terra Keplr address

Assetlist entry: osmosis-labs/assetlists#26

Hi guys,

Would recommend adding a LICENSE file to clarify usage for 3rd parties. Thanks 👍

For example, at https://info.osmosis.zone/token/OSMO, have all the pools with OSMO. Ill try to do this later

Did you realize that we have gone and created a time zone?

Well, a while ago I noticed a glorious synchronization with other participants in the osmosis net work, because of epoch time. Currently, we are expressing time until epoch.

However, given that we will be ascendant, and that we are ambitious, I wish to propose Osmosis Time, or OZT "Osmosis Zone Time" or... (suggestions welcome here.

Ok, so for me, Epoch is midnight, I'm GMT+7.

Osmosis Time:

Days begin at epoch and end at the next epoch.

before epoch, the time is:

23:59:59

Epoch time is:
00:00:00

.... and that is the beginning of a new day.

Expressing this concept clearly, and using OTZ throughout the community may enhance the odd synchronicity benefits of OT.

Due to a lack of murderous stupidity in our community, OT has no concept of daylight savings time.

NB: OT !=GMT+7

it is instead a clean break away from current time-related silliness plaguing the world.

https://github.com/osmosis-labs/osmosis-frontend/blob/develop/localnet/mnemonics.txt#L4
https://github.com/osmosis-labs/osmosis-frontend/blob/develop/localnet/Dockerfile#L53

cosmos1h5rcx73zj474nrkkcyf28tud47k8thy5d6cyuh // 0.913 ATOM
osmo1h5rcx73zj474nrkkcyf28tud47k8thy59pt529 // 9.865 OSMO
cosmos1ymk637a7wljvt4w7q9lnrw95mg9sr37y4s4an9 // 0.593 ATOM

The current one looks scary and poorly designed (oops, had to launch). Let's not scare away users before they have even tried Osmosis.

Currently, the frontend only allows adding liquidity at exactly 50-50 by using the JoinPool msg type. This turns into an issue because if a swap happens in the time since a user made the JoinPool tx, it would fail.

The chain also supports JoinSwaps, which would make it possible to swap to the right ratio and then add liquidity. https://github.com/osmosis-labs/osmosis/blob/main/proto/osmosis/gamm/v1beta1/tx.proto#L126

This is a requested feature, but only low priority imo
https://twitter.com/larry0x/status/1461483020469346311

Assetlist entry: osmosis-labs/assetlists#21

These balances are visible for now:

My Osmosis Assets :
Total Assets
Available Assets
Bonded Assets
+ Staked Assets

There would be a more complete view of the total value of the wallet if the balance of staked Osmos were also exposed.

Problem

Within the Pool Catalyst section of a pool's page (/pool/###), the current colored circles with bubbles in them don't serve much value, and misses an opportunity to make it quicker and easier to visually understand which tokens make up the pool.

Solution

Replacing the generic bubbling liquid with the token logo will vastly improve readability. See image below for an example of current vs proposed.

I'd argue that the current liquidity mining screen is not as intuitive as it could be, doesn't convey enough information--and where it does, it's scattered--and isn't sustainable for potential future scenarios.

For example, let's say Juno network provides 2045 JUNO as bonus rewards. How will users know whether that bonus is being matched by Osmosis? Or let's say someone else offers a few extra JUNO to the bonus. Does that additional offer get matched? (I assume not). Could someone add a totally random token, e.g., SCRT, to an unrelated pool, e.g., JUNO/OSMO? Or how much does my current LP tokens earn of each token, and by dollar amount, each day?

It would be nice to be able to easily see what the extrenal incentives are (daily amount, which token, remaining # of epochs), whether they're matched by Osmosis, and what their APRs from each are.

My suggestion here is to have a section for Osmosis Rewards, Matched Rewards, and Bonus Rewards. This should clear much of the confusion around rewards and will be able to handle all kinds of multiple people offering all kinds of different tokens and bonus rewards for all kinds of durations.
I even added a 'My Rewards' section, as an additional suggestion, to show how much the user has bonded to each gauge, and what the daily rewards look like.

I really think something like this (albeit a tad cluttered when there is many types of external incentives) is much more intuitive. Using tooltips can cut down on the explainer paragraphs (e.g., on what bonus rewards are). I ask that you consider taking inspiration from this:

Problem

The Deposit link on the Assets page includes vested tokens, making IBC transactions fail. It can be difficult for users to troubleshoot since even Keplr extension shows vested tokens as 'Available' and Mintscan will first show the total balance. Only once you manually subtract the vested balance (or look at 'Available' on Mintscan) can you determine what the real available balance is.

I noticed this today with LUM where many users' tokens are vested from the Airdrop.

Solution

Make it easy on users by having the Deposit function subtract vested tokens so transfers user don't get confused and IBC txs stop failing.

Problem

When in the pool detail view, unless you scroll down it's hard to see what coins this pool involves.

Solution

Somewhere in the header we should include the coin composition. (ex. CRO/OSMO)

Ask

Please remove Pool 562 LUNA/UST from being used from the Trade page.

Problem

The Trade page on Osmosis app defaults to using pool 562 to trade between LUNA and UST with a swap fee of 0.535%. The primary issue is that this swap fee is high and discourages trading on Osmosis. For those who don't know that a cheaper routes exist (e.g., through Pool 560 (at 0.2% fee) and then Pool 561 (at 0.2% fee) == 0.4% fee total) are charged extra swap fee and might choose an alternative trading platform (e.g., TerraSwap); while those who do know that a cheaper route exists are inconvenienced by manually having to swap to OSMO first as an intermediate step.

In addition, due the fact that this pool is selected for these types of trades when it is not the cheapest trade option, we have more of the Osmosis incentives being allocated to LPs of this pool--a pool without OSMO--which is Liquidity that is not benefitting Osmosis (yet) because cheaper routes exist.

Solution

The solution in the short term is simple: ensure that trades between on LUNA and UST on the Trade page instead go through pools 560 (UST/OSMO) and 561 (LUNA/OSMO).

I think it might just need to be removed from GAMMSwapManager at osmosis-frontend/src/stores/root.ts, however, more change might be required to ensure the route does a hop through pools 560 and 561 instead of pool 562.

Discussion

There has been discussion on this on Commonwealth and a bit on Osmosis Siberia, which explore further the problem, the possible solutions, and all seem to conclude that removal of Pool 562 as default on the Trade page is the only solution we have right now. (i.e., unless pool sub-governance or optimized trade routing are coming very very soon).

Hello,

I just wanted to start a topic to discuss the mobile compatibility. Is this currently in the backlog, what are the current blockers? I started playing with the Keplr Mobile App and it's looking quite stable. Any additional information is appreciated !

Thanks!

Background / Problem

• The current pools page UI was designed at a time when there were ~8 IBC enabled chains
• The number of assets continue to increase on Osmosis
• Number of incentivized pools grew from under 10 to over 40
• Looking for a pool for a specific token requires multiple 'trial and errors' sifting through pools lists
• Current UI is not space efficient

Solution

• Add 'filter-by-token' system for 'All Pools' section
• Allow sorting by categories (TVL/Volume)
• Redesign the 'Incentivized pools' section to:
  1. Use screen real estate more efficiently
  2. Allow multiple views sorting by various categories such as token, APR, TVL, etc

Potential issues / Things to consider

• The current frontend architecture was intended to only make use of available on-chain information (reduce dependency to proprietary backend/middlelayer infrastructure), additional implementation or use of middle layer solutions may be necessary
• The visual contrast between a 'card format' of incentivized/my pools vs 'list format' of all pools serves the purpose of prioritizing information (albeit somewhat poorly). Find a middle ground where the number of cards are not overwhelming, but still maintains the purpose of providing visual separation
• Don't stray too far from the current visual layout of Osmosis to not add friction for existing users

The Coingecko team has been true champs that integrated Osmosis dex price data to their platform very early.

As stated here, we should add OSMO price to the sidebar alongside a basic Coingecko logo or a 'Powered by Coingecko API' text that links to the Coingecko website as a gesture of appreciation.

There is lots of duplicated callback logic after a tx is confirmed to have been received. This is duplicated across every different msg. It would be great to lower the amount of code re-use, by making common functions for refreshing relevant components as needed in each tx.

The part I am looking at is: https://github.com/osmosis-labs/osmosis-frontend/blob/master/src/stores/osmosis/account/index.ts#L266-L277 in every message

I noticed this recently while browsing the app; any reason the fee primitive should be logged? I'm happy to open a PR removing this unless there's a specific reason to keep this

Since epoch rewards are once a day, I think the 0D should be removed from the time until next epoch rewards. (Not really a high priority thing) E.g. here in /pools

Hello,
Is it possible to remove these scrollbars ? Or replace them with something more modern ?

Thank you

u

Because the number of Pools and Assets are growing it is sometimes difficult to find the Pool or Asset you are searching for.

I think this can be solved by adding a filter (in the top) on the Pools and Assets pages.

Thank you for all the good work in this beautiful project.

Currently, there is a MAX button to select your total balance for swap, other Dex'es like Solana Raydium have a half option as well which is very useful when converting funds for 50/50 pools.

Osmosis would benefit from this to help users swap tokens for liquidity pools, we could go a step further and offer buttons like:
10% 25% 50% 75% MAX which should cover most pool configurations.

If dust is added to external incentives, it appears that it shows up on the pools themselves. I imagine this isn't the ideal behavior; I ended up just adding more SCRT to even it out.

Hello,
I would be nice to replace the "windows"/native scrollbars with modern ones like:
https://www.jqueryscript.net/blog/Best-Custom-Scroll-Bar-jQuery-Plugins.html

Thank you

Due to the fact that Keplr does not support different Ledger apps, it would be nice to be able to specify the withdraw address when withdrawing funds from Osmosis. This way, people that are using addresses generated with different SLIP-44 values can safely withdraw their funds to such addresses without having to perform the following steps:

1. withdraw the funds to the address generate by Keplr
2. send the funds to their real account

Currently the tokens in main page's UI, when you click the "From" button, are sorted by what appears to be the order in the assets page.

Instead, we should change it so that it puts tokens you already have at the top. (So you don't have to scroll as far as to find them)

Tracking tasks

• #349

A space is missing here in the pool description. Seems to be mobile only.

Desktop version for reference

We should automatically pull the Embed-Chain infos from the chain-registry. (If theres missing fields needed, we should add these to the chain-registry)

This will significantly lower the manual overhead involved for replacing IBC denoms with human readable names.

Background / Problem

• LBPs follow a drastic 'start high, end low' dutch-auction-like mechanism for markets demand to be reflected in initial price discovery of tokens
• LBPs are effective when there is demand 'at a certain price', not 'at a certain time'
• Lack of understanding of the LBP mechanism can lead users to 'ape-in' early
• Mechanism between pool weight <> token price can be too difficult to understand

Solution

• Provide a more digestible graph/chart on the LBP pool details page breaking down the simulated price graph over time
• Show that 'buying the token' moves price up vs 'not buying the token' moves price down

Potential issues/ things to consider

• LBP pool on Osmosis, while not insignificant, is relatively smaller in comparison to existing pools. Don't overcomplicate, overengineer, overdesign. Need to be resource efficient with bigger priorities if needed.
• Working with the Imperator historical data may be necessary to provide non-onchain information that may need to be included in chart

Helpful resources

• Copper LBP is a good example
• Stargaze team created a LBP simulator for Cosmos

Goals

• Component standardization
  • Need dependency on design team (cc @victortokaito)
  • Allow reusable components
• Separation of logic-related code and view-related code
  • Currently code related to logic and code related to view are mixed up, causing lots of bugs
  • Adding new features are resource intensive
• Previous refactor was started but wasn't finished
• Standardize frontend styling framework to tailwind
  • Currently using two frameworks for frontend styling (tailwind and emotion)
• Move to NextJS

Commonly requested feature: https://twitter.com/fwoods_xf/status/1448912286542753793

Now that Halloween is past, we should bring back non-spooky Wosmongton!

illogical

Can we increase the size of the hitbox (the interactive area that you can click on) for the 'token select' UI?

Right now, the hitbox is small enough that it's easy to miss and click outside of the drop-down menu. Clicking the token and its icons don't activate the dropdown.

See loom video for example: https://www.loom.com/share/f3efb9a080a045808d8ce5ec83ec78a2

I am trying to bond LP tokens and get the following message when sending transaction type 'osmosis/lockup/lock-tokens' : "out of gas in location: WritePerByte; gasWanted: 1500000, gasUsed: 297259: out of gas"

I manually set the gas to 2500000 and the transaction failed again. Possible this issue is with IBC or Keplr wallet, but I would appreciate help troubleshooting.

map error code to human-readable text.

This issue takes into consideration, implements, and resolves issues #128, #138, #142, #148, #64, #134.

Background / Problem

• Pools are not easy to scan. And the number of assets continues to increase on Osmosis.
• Pools page was designed at a time when there were few IBC-enabled chains
• Searching for a pool for a specific token requires multiple ‘trial and errors’ sifting through pool lists. The current UI is not space efficient.
• Users request breakdown of certain rewards/APR’s

Solution

• Provide more tools for users to filter data.
  • Add ‘filter by symbol’ search system
  • Enable sorting by categories (e.g. TVL, volume, APR, my assets)
• Redesign “Incentivized Pools” to:
  • use screen real estate more efficiently
  • allow multiple sorting categories (e.g. by name, APR, TVL, etc.)
• Improve general information architecture, making pools easier to scan.
• Improve sense of visual hierarchy, highlighting most relevant statistics, add icons for quick visual identification.
• Use info alerts/tool tips/APR breakdowns to keep information hidden until needed. Complexity is obscured for users who don't need this info, but available to those who want to know how things work.

Things to consider

1. New changes to UI should keep original osmosis aesthetic intact to reduce any friction for existing users.
2. Consider visual hierarchy and space inefficiencies of the current pools section to improve readability/scanning

Problem

Currently, token information is included to the osmosis-frontend source build. This means there is a duplicated effort of adding token information for every time a new token needs to be added to Osmosis.

Potential Solution

• There already is osmosis-labs/assetlists which has all the information (including token logos) needed.
• The Osmosis frontend should fetch all the information from assetlists including token denom, decimals, IBC channels, logo, etc.
• One issue could be RPC/REST endpoints do not exist in assetlists, and will need to be added from cosmos/chain-registry. However, because Keplr requires websockets to be enabled there needs to be some checking of the endpoint to ensure that websocket works.

From @jeremyparish https://commonwealth.im/osmosis/proposal/discussion/1547-how-can-we-improve-the-osmosis-frontend-feedback-thread?comment=7905

Essentially it would be cool if we could add a tool tip to every APR on the front-end, showing a decomposition of where the APR is coming from. There would be three sources in Osmosis:

• Osmo Incentive APR
• Fee APR
• {other token} incentives APR

Not sure if we need more work to add the Fee APR at the moment though. It should be possible to derive using API data from imperator https://api-osmosis.imperator.co/swagger/#/

I think the image explains it well. Since begin-partial-unbond is here (or coming soon), we should be able to allow for something like this, where the user can enter a specific amount of LP tokens to unbond:

We may be able to eventually have some kind of combined 'Manage LP tokens' or 'Manage bondings' section/prompt for a cleaner interface (like how Sushi has), but for now you should be able to bascially reuse the 'Bond LP tokens' prompt for allowing to specify for partial unbond. Since LP tokens aren't always in user friendly numbers (in terms of readability), perhaps an option to enter a % of bonded tokens and showing $ value of specified amount could also be nice.

Hi there,

Would love it on the swap page if the currently selected pair was appended to the URL as params. Something along the line of:
https://app.osmosis.zone?from=ATOM&to=OSMO

Would allow users to bookmark a link to directly take them to the swaps they perform daily, i.e. when rewards are paid out.

Let's bring Wosmongton and friends to the app.osmosis.zone mainpage!

I think folks are gonna love these illustrations!

Hello,
Using the up/down button to switch the tokens the USD price of the tokens will not be the same.

1. Use a token pair eg. Luna/Osmo
2. Wait for a USD change (no cents) of one of the token and the press the middle button to switch.

The USD price will be different. I expect to be the same.

So it seems that frontend doesn't correctly update the USD values of both tokens or are you getting the USD values from CoinGecko which it's slow ? Isn't an oracle better like Band ?

Challenge

The documentation for the frontend is work in progress and needs work and step by step guides.

Solution

Create the following guides in order for users to fully understand the process from beginning to end.

Docs pPreview

https://osmosis-labs.github.io/osmosis/overview/

App Documentation breakdown

TODO/Goals

• Update Structure to match the one below Commit
• Finish up all docs for each section
• Add video tutorials to display on the getting started page.

OSMOSIS APP Documentation Structure

• Getting Started
  • Open the App
  • Connect Wallet
  • Deposit Funds
  • Swapping Tokens
  • Create a New Pool
• Adding Liquidity to a Pool
  • Bonding LP Tokens
• Learn More
  • Bonded Liquidity Gauges
  • Allocation Points
  • External Incentives
  • Fees
• Wallet
  • Create Keplr Wallet
  • Import a Keplr account
  • Import a Ledger account

We should clean error messages from the state machine to be far more human readable.

In these lines, https://github.com/osmosis-labs/osmosis-frontend/blob/master/src/tx/tx-tracer.ts#L160-L161 we should clean the error message before creating it into an Error.

We should in the beginning do:

1. Find/Replace ibc denoms strings with human readable denoms from the asset list
2. Run the following regex: Find Regex signature verification failed; please verify account number \([0-9]*\), sequence \(([0-9]*)\) and chain-id \(osmosis-1\): unauthorized Replace Regex You have too many concurrent txs in flight! Try resending after your prior tx lands on chain. (We couldn't send the tx with sequence number $1). You can play with the regex here: https://regex101.com/r/ZkRbXL/1/
   The way you can do this regex substitution before displaying the error in JS per my understanding is string_to_replace.replace(findRegex, replace)

Multi-hops are using non-optimal routes by not using OSMO pools. OSMO pools tend to have 0.2% fees compared to 0.3% fees for ATOM pools as well usually having substantially more Liquidity to minimise slippage due to the OSMO bias on incentives attracting more liquidity before a stable Liquidity is reached.

Example:
Swap from DVPN to HUAHUA via OSMO multi hop: costing 0.4% swap fees and 0.142% slippage

Swap back from HUAHUA to DVPN goes via ATOM pools and costs 0.6% fees and 0.727% slippage

Discussion on this here: Commonwealth

Hello,
Could you please add the relayer status when you try to deposit/withdraw in order to avoid doing that when the relayer is down or has a malfunction ? (or even better disable it the buttons)

Currently i can find this info on Osmosis Discord #ibc-status

Thank you

Problem

It's quite annoying to have to tap away from the menu after making a selection in the menu. It's one extra tap that isn't needed.

Proposed Solution

We should automatically close the menu when someone makes a menu selection on mobile.