Third-party components and licences

Tempo stores distributed traces. The collector receives traces from the platform over OTLP and forwards them to Tempo, which keeps them for 168 hours, and Grafana reads them back through its Tempo datasource. The chart also references the grafana/tempo-query image from the same project. Set tempo.enabled: false to leave Tempo out. To keep a trace store you already run, repoint the collector's trace endpoint and the Grafana datasource at it, as the observability stack page describes.

Source: github.com/grafana/tempo.

Blockscout#

Blockscout is a block explorer for the ledger network the deployment runs on. The backend indexes the chain through the ledger node's JSON-RPC endpoint into its own blockscout database on the PostgreSQL server you supply, and the frontend serves the explorer pages. The Console builds its links to the explorer from the explorer.url application setting. A network definition can name any other explorer, so Blockscout is one choice among several.

The chart leaves Blockscout off. Set blockscout.enabled: true to deploy it, and blockscout.frontend.enabled: false to run the backend without the frontend. The chart configures the backend and frontend containers through environment variables. Its init containers wait for the database with a small SettleMint-built utility image and do not alter the Blockscout image.

Both pinned versions were published under GPL-3.0: the LICENSE file at backend tag 9.0.2, published on 14 August 2025, and at frontend tag v2.3.5, published on 14 October 2025, holds the GPL-3.0 text. The default branch of both repositories now holds a different licence file, the Blockscout Software Licence, effective 22 April 2026, which states that it does not apply to earlier versions of the software. Read the LICENSE file at the tag you move to before you change blockscout.blockscout.image.tag or blockscout.frontend.image.tag.

Source: github.com/blockscout/blockscout and github.com/blockscout/frontend.

Check what runs in your cluster#

List the distinct images running in the cluster and pick out these projects:

kubectl get pods --all-namespaces -o jsonpath='{range .items[*]}{.spec.containers[*].image}{"\n"}{end}' \
  | tr ' ' '\n' | sort -u | grep -E 'grafana/|blockscout/'

A cluster with the default values lists Grafana and Tempo images and no Blockscout or Loki image.

Contracts#

Every Solidity file in the DALP contract set names its licence in an SPDX-License-Identifier line at the top of the file. SettleMint's contracts are under the SettleMint commercial licence, identified as LicenseRef-SettleMint-Commercial. The exceptions are the GPL-3.0 components below, which come from or build on OnChainID and the eth-infinitism ERC-4337 EntryPoint, and a few files that carry the licence of the work they adapt or implement. DALP deploys every contract through Hardhat Ignition modules. EVM contract set describes the contract layers.

GPL-3.0 components#

Three components carry GPL-3.0:

• Key and claim management. The ERC-734 key management and ERC-735 claim management base contracts are derived from the Identity contract of OnChainID, and each file carries an attribution line to the upstream project.
• Identity implementations. The wallet identity implementation, in three versions, and the contract identity implementation, in two versions, inherit those base contracts.
• Local ERC-4337 EntryPoint. Two wrapper contracts around the eth-infinitism EntryPoint, described below.

OnChainID#

OnChainID is the open standard for on-chain identities that hold keys and claims. DALP's contracts depend on the package @onchain-id/solidity 2.2.1, published under GPL-3.0 by the OnChainID project at github.com/onchain-id/solidity. DALP uses four interfaces from it: IIdentity, IERC734, IERC735 and IClaimIssuer. They define an on-chain identity, its key management, its claim management and the check that a claim issuer runs on a claim. DALP uses nothing else from the package.

The package declares a narrower Solidity pragma than the compiler DALP builds with, so DALP applies a patch to it. The patch makes 18 pragma widenings and changes nothing else. The key and claim management base contracts and the identity implementations are the DALP files derived from or built on that package, and they keep the GPL-3.0 licence. The rest of the identity contracts, among them the identity factories and proxies, are SettleMint code under the commercial licence.

ERC-4337 EntryPoint#

ERC-4337 is the account abstraction standard. Its EntryPoint contract validates and executes user operations for smart accounts. DALP uses the eth-infinitism implementation from the package @account-abstraction/contracts 0.9.0-rc.1, published at github.com/eth-infinitism/account-abstraction. The EntryPoint and EntryPointSimulations source files in that package carry GPL-3.0, and other files in the package carry MIT.

Two DALP contracts wrap these files without changing them. Each is an empty subclass of the upstream contract, and each carries a GPL-3.0 identifier:

• The EntryPoint wrapper exists so that Hardhat produces a deployable artifact for the upstream EntryPoint. Ignition deploys it when the canonical ERC-4337 EntryPoint is absent from the target chain, which Ignition detects by reading the code at the canonical address. That is the usual case on local and private chains.
• The EntryPoint simulations wrapper exists to produce the simulations bytecode. DALP never deploys it. The execution service reads its ABI and calls it through eth_call with a state override that places the simulations code at the EntryPoint address, which is how it estimates gas and validates user operations before submission.

On a chain where the canonical EntryPoint at 0x433709009B8330FDa32311DF1C2AFA402eD8D009 already has code, as on the public networks that carry it, Ignition deploys no EntryPoint. It deploys EntryPointReference instead, a thin forwarder that points DALP at the canonical contract. EntryPointReference is SettleMint code under the commercial licence, and it blocks withdrawTo and the stake management calls addStake, unlockStake and withdrawStake, because the canonical EntryPoint keys deposits and stake by the calling address.

Files under other licences#

A few files carry the licence of the work they adapt or implement:

• MIT. The ERC-7579 validator, executor and multisig modules and the paymaster base contract are adapted from OpenZeppelin Community Contracts. Multicall3 is vendored from the Multicall3 project. A small interface for resolving a paymaster's deposit EntryPoint is SettleMint's own and also carries MIT.
• CC0-1.0. The six ERC-3643 interface files.

The identifier in the first line of each file is the record for that file.