Blockscout has a native integration with Noves Translate.

The integration can be enabled by simply changing a couple of ENV vars in the main backend container and in the frontend container. You must be running Blockscout 2.0 or higher.

To enable the integration and have human-friendly transactions displayed on the block explorer UI, follow these steps:

A) Get a Noves API key

B) In the frontend container, set this environment variable to noves:

NEXT_PUBLIC_TRANSACTION_INTERPRETATION_PROVIDER=noves

C) In the backend container, set these two environment variables:

NOVES_FI_CHAIN_NAME=$CHAIN_NAME_IN_NOVES_API
NOVES_FI_API_TOKEN=$NOVES_API_KEY

For the chain name, you can simply check what's the exact name that comes back for your chain when you query the chains endpoint.

As an example, the slug for Polygon Mainnet is simply polygon and for Ethereum Sepolia Testnet it is eth-sepolia.

There's a third variable (NOVES_FI_BASE_API_URL) that you typically won't need to uncomment or change. It defaults to our primary gateway for Translate API requests originating from Blockscout. Don't change this variable unless you've been in communication with Noves and you've been specifically asked to change it.

D) Make sure the new variables are set (in the same way you've configured other environment variables), and restart both the backend and frontend containers. The integration will start working automatically.

If you're using the default docker-compose installation, then you'll typically set these variables under the environment section in the yaml for frontend and backend. And then you can simply run this to make the change effective:

docker compose up -d