You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Frontend] Transaction state machine + error-code surfacing in the UI #44
When a Soroban transaction fails or stalls, the UI gives little feedback and doesn't surface the
contract's typed error. Users don't know whether to retry, wait, or that they're unauthorized.
A transaction state machine (idle → building → signing → pending → success / failed) surfaced
via toasts/inline status, with retry on transient RPC failures
React error boundaries so a render error in one panel doesn't blank the app
Handle the "stuck/pending" case (timeout → check status → allow safe retry without double-spend)
Acceptance criteria
A reverted tx shows the specific reason (e.g. "Not authorized", "Milestone already approved")
Transient failures are retryable; the app never silently hangs on a spinner
An error in one component doesn't crash the whole page
changed the title [-]Transaction state machine + error-code surfacing in the UI[/-][+][Frontend] Transaction state machine + error-code surfacing in the UI[/+]on Jun 17, 2026
Audit requirements and target files cleanly without introducing regressions to existing interfaces.
Enforce explicit error boundaries, input sanitization, and deterministic lifecycle handling.
Quality & Standard Compliance:
Fully satisfy all acceptance criteria for [Frontend] Transaction state machine + error-code surfacing in the UI following the repository's established conventions.
Clean linting, strict typing, and zero compiler/clippy warnings.
Verification & Testing:
Dedicated unit and integration tests covering the happy path, boundary conditions, and failure recovery.
Zero-regression guarantee across existing test suites.
Production Track Record
Verified Stellar & Soroban Track Record: Merged PRs in cybermax4200/stellar-did-credit #898 & #900 (+400 points Wave 9), approved review in documenso/documenso #3275, active deliveries in Vero-protocol/vero-core-contracts, Sorobill/*, and Bitcoindefi/OpenAO.
Ready to implement and deliver as soon as officially assigned! Looking forward to contributing.
Activity
[-]Transaction state machine + error-code surfacing in the UI[/-][+][Frontend] Transaction state machine + error-code surfacing in the UI[/+]Ranjeet2063 commentedon Oct 5, 2026
Hello team,
I looked into
[Frontend] Transaction state machine + error-code surfacing in the UIand have an implementation approach ready.Proposed steps:
Please assign this to me if the plan looks good. Thanks!
Rodrigoue9 commentedon Oct 6, 2026
Hi maintainers! 👋 I would love to take on issue #44 (
[Frontend] Transaction state machine + error-code surfacing in the UI).Technical Analysis & Implementation Approach (TypeScript / Web3)
[Frontend] Transaction state machine + error-code surfacing in the UIfollowing the repository's established conventions.Production Track Record
cybermax4200/stellar-did-credit #898΄(+400 points Wave 9), approved review indocumenso/documenso #3275, active deliveries inVero-protocol/vero-core-contracts,Sorobill/*, andBitcoindefi/OpenAO.Ready to implement and deliver as soon as officially assigned! Looking forward to contributing.
woahwhattheheck commentedon Oct 6, 2026
/claim #44
Update README.md
wrote a thorough e2e test for freelancer withdrawal from escrow