massalabs/docs

FAQ - When can a transaction be considered failed?

Open

#291 opened on Mar 11, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (66 forks)auto 404
good first issue

Repository metrics

Stars
 (18 stars)
PR merge metrics
 (PR metrics pending)

Description

Add to the documentation an explanation of when a transaction can be definitively considered as failed. This includes the nominal case, where a transaction is included in a final block as failed, but also more exotic cases such as:

  • The transaction is not included in any block
  • The transaction is only included in a block that is stale
  • Other scenarios?

Contributor guide

Research direction
Review the existing documentation on transaction lifecycle and failure conditions. Add clear definitions for each scenario: transaction included in a final block as failed, not included in any block, included only in a stale block, and any other cases. Provide examples and references to the Massa protocol specifications.
Tech stack
None
Domain
documentationblockchain
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90