duneanalytics / duneanalytics/evm.codes

Improve EVM Playground Memory formatting for better readability

Open
#416 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
827
Forks
199
Avg merge
15m
Merged PRs (30d)
1

Description

Problem

Currently, the "Memory" section in the EVM Playground displays the data as a single, continuous string of hex bytes. This continuous format makes it very difficult to read, track specific offsets, and effectively debug memory states.

Image
Proposed Fix

We are proposing an update to display the memory in a more structured format. By breaking down the memory into 32-byte (word) chunks and displaying the corresponding hex offset at the start of each line, it becomes significantly easier for developers to parse and understand the memory layout at a glance.

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the EVM Playground's Memory section and trace the current rendering of its continuous hex-byte string. Done means memory is displayed in 32-byte word chunks, with the corresponding hexadecimal offset at the start of each line, matching the readability shown in the proposed example.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
blockchain, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.