Change Log: Version 1.82 – Bitfinex blog

[ad_1]

Change Log: Version 1.82

The Bitfinex Change Log is an overview of all performance and UI changes made to the Bitfinex trading platform. For an overview of all previous changes, please refer to blog.bitfinex.com/category/changelogs.

Version 1.82

Features

  • Updated the look and feel of the order book interface settings and a number of pop-ups (order history, info modal, claim position, calculator, Ticker settings, share PNL, alert)
  • Added support for the Vietnamese language
  • Added support for Affiliates on the Turkish domain
  • Added a Notice for UK-based users regarding UK marketing regulationsย 

Improvements

  • Updated the Tether tokens and XAUt deposit notices on Polygon zkEVM and Cosmosย 
  • Updated to make tags (user, hash, cash) clickable in the Bitfinex Leaderboard user profile overlay
  • Optimised the funding-matched trades pop-up when at the minimum widthย 
  • Updated to add the explorer for Tether tokens in the Reports Currency columnย 

Bug Fixes

  • Fixed the balances search function to return results for SAT and BTC correctly
  • Fixed the layout for trading sidebar right-hand side mode layout
  • Fixed the funding amount formatting on copy/pasting or when clicking โ€œOffer allโ€
  • Fixed the TradingView chart time on the time range change
  • Fixed the whitelisted withdrawal tag filed issue for XRP in security settings
  • Fixed the LN-BTC search not appearing in the withdrawal drop-down options
  • Fixed an issue after clicking โ€œrepostโ€ and then closing the editor popup; the reposting link error in Bitfinex Pulse will be automatically cleaned up.
  • Fixed the repost feature not working in the conversation tab for Bitfinex Pulse
  • Fixed the sidebar quick editor issue, so it now opens automatically in all feedsย 
  • Fixed the sidebarโ€™s redirect repost button not functioning correctly to the โ€œAllโ€ tab in Bitfinex Pulse.

[ad_2]

Source link


Posted

in

by

Tags:

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *