BlockScout 1.3.5 Release


#1

Features

  • #1560 - Allow executing smart contract functions in arbitrarily sized batches
  • #1543 - Use trace_replayBlockTransactions API for faster tracing
  • #1558 - Allow searching by token symbol
  • #1551 Exact date and time for Transaction details page
  • #1547 - Verify smart contracts with evm versions
  • #1540 - Fetch ERC721 token balances if sender is ‘0x0…0’
  • #1539 - Add the link to release in the footer
  • #1519 - Create contract methods
  • #1496 - Remove dropped/replaced transactions in pending transactions list
  • #1492 - Disable usd value for an empty exchange rate
  • #1466 - Decoding candidates for unverified contracts

Fixes

  • #1545 - Fix scheduling of latest block polling in Realtime Fetcher
  • #1554 - Encode integer parameters when calling smart contract functions
  • #1537 - Fix test that depended on date
  • #1534 - Render a nicer error when creator cannot be determined
  • #1527 - Add index to value_fetched_at
  • #1518 - Select only distinct failed transactions
  • #1516 - Fix coin balance params reducer for pending transaction
  • #1511 - Set correct log level for production
  • #1510 - Fix test that fails every 1st day of the month
  • #1509 - Add index to blocks’ consensus
  • #1508 - Remove duplicated indexes
  • #1505 - Use https instead of ssh for absinthe libs
  • #1501 - Constructor_arguments must be type text
  • #1498 - Add index for created_contract_address_hash in transactions
  • #1493 - Do not do work in process initialization
  • #1487 - Limit geth sync to 128 blocks
  • #1484 - Allow decoding input as utf-8
  • #1479 - Remove smoothing from coin balance chart

Chore

  • #1532 - Upgrade elixir to 1.8.1
  • #1553 - Dockerfile: remove 1.7.1 version pin FROM bitwalker/alpine-elixir-phoenix
  • #1465 - Resolve lodash security alert

The latest version of changes and the code https://github.com/poanetwork/blockscout/releases/tag/v1.3.5-beta


#2

#3

Is there an ETA when Mainnet will have the USD bug fixed? IMO, this is a critical bug. It just needs a redeploy with the correct assets files.


#4

There is no ETA, but we are working on that. We will release the fix ASAP. Thank you for your patience.


#5

The patch 1.3.7, that fixing the issue, has been released on Mainnet instance. Sorry, for the possible inconvenience due to the issue.