Bug Description
The Web CLI provides no immediate visual confirmation that a transaction has been successfully submitted or confirmed onchain. Users can spam the "Send" button (or any action that triggers a tx) with no feedback, leading to uncertainty and fear of duplicate transactions.
Transactions do succeed onchain (visible in txn history and balance changes on devnet.octrascan.io), but the dashboard UI shows no success state, loading indicator, or tx hash for a very long time (often upto 20-30 minutes). This is especially noticeable for regular "Send OCT" transactions and even worse for encryption-related actions.
Steps to Reproduce
- Open the Web CLI
- navigate to the transaction / send section.
- Fill in recipient, amount, and any other required fields.
- Click Send multiple times quickly (easy to do because nothing prevents it).
- Observe: UI remains unchanged (no success message, no tx hash, no spinner that completes, no refresh).
- Wait 1+ hour → still no update on the dashboard.
- Manually check:
- Txn history in the same UI (may show tx very late)
- External explorer (devnet.octrascan.io)
- Balance change
Expected Behavior
- After clicking Send, immediately show:
- Clear "Transaction submitted" message with the tx hash
- Loading spinner until confirmation
- Success / failure toast or status update once the tx is mined
- Prevent multiple submissions (disable button or show "pending" state)
- Real-time or near-real-time dashboard refresh for balance and recent txs
Actual Behavior
- No proof of submission
- Button remains active → easy to spam
- UI only updates after extremely long delay (or never in-session)
- Users have to leave the page and manually check history/explorer to know if it worked
- Encryption actions appear to fail completely in UI even when they succeed
Environment
- Browser: [Chrome]
- Device: Desktop
- Network: Devnet
- Time observed: February 2026 (12pm - to date)
Additional Context
This creates a very poor UX and risk of accidental double-spends during testnet activity. A simple tx receipt / pending state would completely solve the issue.
screenshot attached above.
Thanks for building the Web CLI — this is the only major issue I'm hitting.
Bug Description
The Web CLI provides no immediate visual confirmation that a transaction has been successfully submitted or confirmed onchain. Users can spam the "Send" button (or any action that triggers a tx) with no feedback, leading to uncertainty and fear of duplicate transactions.
Transactions do succeed onchain (visible in txn history and balance changes on devnet.octrascan.io), but the dashboard UI shows no success state, loading indicator, or tx hash for a very long time (often upto 20-30 minutes). This is especially noticeable for regular "Send OCT" transactions and even worse for encryption-related actions.
Steps to Reproduce
Expected Behavior
Actual Behavior
Environment
Additional Context
This creates a very poor UX and risk of accidental double-spends during testnet activity. A simple tx receipt / pending state would completely solve the issue.
screenshot attached above.
Thanks for building the Web CLI — this is the only major issue I'm hitting.