Option for logging Starknet state changes

Open
#577 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust

Research direction

The issue names no files or tests. Start by reviewing the existing seven logging modes and related issue #358, then clarify whether the desired output is a transaction trace or execution information. Done should mean the expected state-change output and the appropriate logging-mode scope are agreed.

Written by the indexing model from the issue text.

Description

enhancement

I thought we had an open issue for this, perhaps I confused it with #358.

Perhaps it can just log the tx trace / execution info.

We already have seven logging modes, so let's be wise about this one.

Dominant language
Rust
Stars
131
Forks
79
Avg merge
1d 20h
Merged PRs (30d)
14

Contributor guide

Open the contributing guide

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.

More from starknet-io/starknet-devnet

All issues in starknet-io/starknet-devnet

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.