FuelLabs/fuel-core

Have parity between pre confirmation statuses and `Success` and `Failed` statuses

Open

#3160 opened on Dec 5, 2025

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Rust (57,084 stars) (2,861 forks)batch import
good first issue

Description

This issue does not include a description.

Contributor guide

Tech stack
rust
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Basic knowledge of RustUnderstanding of Fuel transaction lifecycle
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Examine the codebase for definitions of pre confirmation statuses (e.g., in the transaction pool or block executor) and compare with Success and Failed statuses. Look at relevant modules like `crates/fuel txpool` or `crates/fuel core/src/executor`. The issue may involve aligning enum variants or status strings. Review comments on the issue for specific examples or maintainer hints.