Missing non happy path message statuses
- Dominant language
- TypeScript
- Stars
- 371
- Forks
- 248
- PR merge metrics
- No merged PRs in 30d
Description
Op viem has ways of determining if a cross chain message is ready to prove, finalized etc. It does not have a way of determining if a message has not succeeded
Below is a list of the message statuses available. Note: failed l2 to l1 is missing from this list because the op sdk currently treats that as a ready to prove status since if using the sdk you can always try again.
Contributor guide
Research direction
Start by reviewing the existing cross-chain message status handling and the statuses listed in the issue. Confirm the intended non-success behavior, including the note about failed L2-to-L1 messages, and define done as providing a way to determine when a message has not succeeded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100