Skip to content

Conversation

douglance
Copy link
Contributor

Implements client-side browser notifications to alert users of transaction status changes throughout the bridge lifecycle. Notifications trigger on:

  • Transaction signing and broadcast
  • L1/L2 status transitions
  • Withdrawal confirmation and execution
  • Transaction failures

Uses service worker and browser Notification API with no external dependencies. Users opt-in via Settings dialog. Notifications persist in OS notification center.

Copy link

vercel bot commented Oct 1, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
arbitrum-portal Ready Ready Preview Oct 7, 2025 1:23pm

Implements client-side browser notifications to alert users of transaction
status changes throughout the bridge lifecycle. Notifications trigger on:
- Transaction signing and broadcast
- L1/L2 status transitions
- Withdrawal confirmation and execution
- Transaction failures

Uses service worker and browser Notification API with no external dependencies.
Users opt-in via Settings dialog. Notifications persist in OS notification center.
@douglance douglance changed the title feat: add browser notifications for transaction status updates feat: add browser notifications for tx updates Oct 1, 2025
@douglance douglance marked this pull request as ready for review October 1, 2025 19:51
@douglance douglance marked this pull request as draft October 2, 2025 13:41
const withdrawalStatusMessages = {
'Unconfirmed': 'Withdrawal Initiated',
'Confirmed': 'Withdrawal Confirmed - Ready to Claim',
'Executed': 'Withdrawal Claimed Successfully',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

notification is not showing when claiming old transaction


const updateCachedTransaction = useCallback(
(newTx: MergedTransaction) => {
// Find the old transaction from cache to detect status changes
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

notification code probably should move out of updateCachedTransaction?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants