OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Developer Tools

Solidity Metadata Playground

Solidity Metadata Playground is a web-based developer tool that retrieves deployed EVM bytecode by chain ID and contract address, or accepts pasted bytecode, then decodes the Solidity metadata encoded at its end.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Solidity Metadata Playground — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when you have a deployed contract address or bytecode and need to inspect Solidity metadata encoded at the end of that bytecode.

Who it is for

  • Solidity developers investigating metadata embedded in deployed contract bytecode.
  • Researchers tracing CBOR fields and metadata hashes in EVM contracts.

Documented uses

  • Retrieve a contract’s deployed bytecode using its network and address.
  • Inspect and decode the CBOR section appended to bytecode.
  • Identify compiler-version and IPFS or Swarm hash information, and attempt to display an associated IPFS metadata file.
Before you choose

Requirements & limits

  • Address-based lookup requires the chain ID and contract address; direct bytecode input is also supported.
  • The README says network support covers EVM chains listed in ethereum-lists/chains.
  • The tool attempts IPFS metadata retrieval when it finds an IPFS hash, but availability of the file is not assured.
  • The project documents local npm setup and Docker Compose serving at localhost:2346; its repository is MIT-licensed.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Decode metadata from deployed contract bytecode

View the appended CBOR section for a contract retrieved by chain ID and address.

Before you start

  • A supported EVM chain listed in ethereum-lists/chains.
  • A contract address and its chain ID.
  • Network access to retrieve deployed bytecode.

Steps

  1. Choose the network and enter the contract address in the playground.

  2. Inspect the displayed deployed bytecode, which is automatically scrolled to its end.

  3. Read the highlighted CBOR sections and decoded contents; check for compiler-version and IPFS or Swarm hash information.

Expected outcome

A view of the bytecode’s appended CBOR data and its decoded contents.

Guide limitations

  • IPFS metadata retrieval is attempted only when an IPFS hash is present and the file is available.
  • The README documents Infura connections for Ethereum mainnet and testnets; other chain access may require suitable network connectivity.
Documentation 1 ↗
Source-based practical guide

Run the playground locally with Docker Compose

Serve the application in a local Docker container using the repository’s documented configuration.

Before you start

  • The project repository.
  • Docker Compose.

Steps

  1. Obtain the repository.

  2. Run docker-compose up from the project directory.

  3. Open http://localhost:2346.

Expected outcome

The project README specifies the playground served locally at localhost:2346.

Guide limitations

  • The instructions do not establish compatibility with a particular hosting provider.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
14 October 2026
Original website title
sourcifyeth/metadata-playground · Official homepage title · retained in its source language
How we review sourcesSuggest a correction