Repository navigation
UI-FE-014 — Build Claim Review and Authorization Composition #584
Description
Problem context
The final claim step must distinguish review, simulation, signature, submission, confirmation, finality, and indexing.
Technical scope
- Implement exact review summary and authorization boundary.
- Reuse the canonical transaction-state authority.
- Show chain, contract, method, parameters, costs, and recoverable transaction reference.
Architecture and security constraints
- Follow the approved Frontend Implementation Matrix and linked boards exactly.
- Optimism/EVM only. UI context, wallet connection, API data, or fixtures never establish protocol authority.
- Contract state is canonical for mutations; API data is a freshness-labelled projection.
- Storybook fixtures remain isolated from production adapters. Unpinned actions render unavailable.
Required tests
- Unit/component and Storybook interaction tests for the scoped states.
- Keyboard, focus, accessible-name, contrast, reduced-motion, and 200% zoom checks.
- Responsive visual regression at approved desktop, tablet, and mobile widths.
- Lint, typecheck, tests, Storybook build, and production build.
Acceptance criteria
- No success appears at click, signature, or hash receipt.
- Rejected, replaced, reverted, finalized, projection-lag, and reorged states remain distinct.
- Unpinned release or simulation failure disables authorization.
Dependencies
- EPIC V2-FE-150 — Public and Claimant Compositions #554
- STAB-FE-005 — Replace Placeholder Release Data with Verifiable Contract Provenance #560
- STAB-FE-005 — Converge Transaction Status Rendering on One State Authority #565
- UI-FE-013
Do not assign until required dependencies are satisfied.
Non-goals
- Live contract/API integration beyond an existing pinned adapter issue.
- Changing the approved design authority or route contract.
- Applying
Stellar Wave.
Deliverables
- Review/authorize composition.
- Transaction integration contract and tests.
Complexity and points
- Complexity: High
- Points: 200
Approved visual authority
This is a candidate issue only. Do not apply Stellar Wave until maintainers explicitly authorize activation.
Candidate points
- High — 200 points
Candidate only; activation remains maintainer-controlled.
Activity
Folashade6788 commentedon Oct 15, 2026
@Folashade6788 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Folashade6788 to this issue.
drips-wave commentedon Oct 15, 2026
Congratulations, @Folashade6788! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Folashade6788: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
security: UI-FE-014 — Build Claim Review and Authorization Composition (
drips-wave commentedon Oct 21, 2026
This issue has been completed by @Folashade6788 as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Folashade6788: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.