matter-labs / matter-labs/block-explorer
Tx status ZKsync Chain > Gateway > Ethereum
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 139
- Forks
- 145
- Avg merge
- 8h 3m
- Merged PRs (30d)
- 3
Description
🌟 Feature Request
📝 Description
In the tx status, provide information for the tx life cycle so users know it's status on each chain. Would say ZKsync Chain status > Gateway Status > Ethereum Status
🤔 Rationale
Then the user doesn't have to go to the Gateway explorer to see what the status is of the tx being executed on L1.
📋 Additional Context
Add any other context or information about the feature request here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Begin by locating the existing transaction-status view and how it receives status data, then determine how ZKsync Chain, Gateway, and Ethereum statuses can be represented; done means users can see the lifecycle status for each chain without opening the Gateway explorer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100