Change Log: Version 1.59 - Bitfinex blog
20745
post-template-default,single,single-post,postid-20745,single-format-standard,bridge-core-1.0.7,et_bloom,ajax_fade,page_not_loaded,,qode-title-hidden,qode_grid_1300,footer_responsive_adv,qode-content-sidebar-responsive,qode-child-theme-ver-1.0.0,qode-theme-ver-18.2.1,qode-theme-bridge,qode_header_in_grid,cookies-not-set,wpb-js-composer js-comp-ver-6.0.5,vc_responsive

Change Log: Version 1.59

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.59

Features

  • Updated to rename the Limit (order book) order type to Interactive Book
  • Bitfinex Pay Merchants: addition of a link to the Dashboard in the Trading header menu 
  • Addition of TRC-20 support for Tether USDt on Mercuryo payment processor

Improvements

  • Updated the Movements Table “Amount” field USD-equivalent sorting 
  • Updated the Tether withdrawal request pop-up message
  • Updated the Movements table for the “Amount” column to add a settings-based equivalent tooltip
  • Affiliates: updated the dashboard to add the “Refer a friend” section and “What can I earn?” pop-up
  • Updated to enable a view of GIPHY image in lightbox for Bitfinex Pulse

Bug Fixes

  • Fixed Summary Analytics section chart colours to correspond to the user-selected mode
  • Fixed the Over the Counter amount input to round to 8 decimals
  • Fixed Bitfinex Pay Merchant to show a helpful error message on sub-account creation
  • Fixed Summary Russian translation
  • Fixed the verification dialogue missing notification text for withdrawals 
  • Fixed to disable the state payment ID for whitelisted addresses
  • Fixed the generate LNX tipping invoice within the limit for Bitfinex Pulse
  • Change the conversation room icons into coloured token icons in Pulse 

The Bitfinex APIs are designed to allow complete access to the features provided by Bitfinex. Learn more about our API documentation here.