Skip to content

feat: implement token allowances, walletconnect v2, payment retry, and secrets management#279

Open
Dev-sandy1 wants to merge 1 commit intoSmartdevs17:mainfrom
Dev-sandy1:feature/issue-259-261-265-269-implementations
Open

feat: implement token allowances, walletconnect v2, payment retry, and secrets management#279
Dev-sandy1 wants to merge 1 commit intoSmartdevs17:mainfrom
Dev-sandy1:feature/issue-259-261-265-269-implementations

Conversation

@Dev-sandy1
Copy link
Copy Markdown

Summary

This PR implements four major features across the backend and frontend:

1. Token Allowances Management Dashboard (#269)

  • Backend: New /api/v1/allowances endpoint with support for:

    • Fetching token allowances from chain
    • Approval/revocation interface
    • Risk indicators for unlimited allowances
    • Batch revocation
    • Historical approvals log
    • Gas estimation for changes
    • Recommended allowance amounts
  • Frontend: New dashboard page at /dashboard/allowances with:

    • Table view of all allowances with risk indicators
    • Approval and revocation modals
    • Batch selection and revocation
    • Approval history tab
    • Summary cards showing total allowances and risk levels

2. WalletConnect v2 Integration (#265)

  • Frontend: New wallet-connect library with:
    • Web3Modal integration for WalletConnect v2
    • Multi-chain namespace support (eip155)
    • Session persistence
    • QR code generation support
    • Deep link handling
    • Chain switching functionality
    • Session expiry handling

3. Automatic Payment Retry with Exponential Backoff (#261)

  • Backend: New retry service with:

    • Configurable retry configuration per payment type
    • Exponential backoff algorithm
    • Max retry limits
    • Transient error detection
    • Failure notifications
    • Manual retry override
    • Retry analytics
    • Circuit breaker on repeated failures
  • New endpoints:

    • /api/v1/retry/config - Manage retry configurations
    • /api/v1/retry/status - Check payment retry status
    • /api/v1/retry/analytics - View retry statistics

4. Secrets Management with HashiCorp Vault (#259)

  • Backend: New vault service with:

    • Vault integration setup
    • Database credentials in Vault
    • API keys in Vault
    • Automatic rotation
    • Lease management
    • Secrets injection
    • Emergency access procedures
  • New endpoints:

    • /api/v1/secrets - Secret management CRUD
    • /api/v1/secrets/database/credentials/:role - Dynamic database credentials

Test Plan

  • Test allowances API endpoints
  • Test payment retry functionality
  • Verify Vault integration (when Vault is available)
  • Test wallet connection flow

Notes

  • All new features include mock data for development/testing
  • Environment variables can be used as fallback for secrets
  • Circuit breaker prevents retry storms on persistent failures

Closes #269
Closes #265
Closes #261
Closes #259

…d secrets management

- Add Token Allowances Management Dashboard (Smartdevs17#269)
  - Backend: allowances API with approve/revoke/batch-revoke
  - Frontend: dashboard page with risk indicators and history

- Implement WalletConnect v2 Integration (Smartdevs17#265)
  - Frontend: WalletConnect v2 context with multi-chain support
  - Chain switching, session persistence, QR code support

- Implement Automatic Payment Retry with Exponential Backoff (Smartdevs17#261)
  - Backend: retry service with circuit breaker
  - Configurable retry limits and backoff periods
  - Analytics and manual retry override

- Implement Secrets Management with HashiCorp Vault (Smartdevs17#259)
  - Backend: vault service integration
  - Secret storage, lease management, rotation
  - Database credentials and API keys support

Closes Smartdevs17#269
Closes Smartdevs17#265
Closes Smartdevs17#261
Closes Smartdevs17#259
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 23, 2026

@Ebuka321 is attempting to deploy a commit to the smartdevs17's projects Team on Vercel.

A member of the Team first needs to authorize it.

@Smartdevs17
Copy link
Copy Markdown
Owner

⚠️ Merge conflicts detected

Hi @Dev-sandy1,

This PR has merge conflicts that must be resolved before it can be merged.

To fix:

  1. Sync with the latest main branch: git fetch origin && git merge origin/main
  2. Resolve the conflicts in your code
  3. Push the resolved changes

Once resolved, the PR will be automatically merged on the next run.


🤖 Drips Wave Review Agent

2 similar comments
@Smartdevs17
Copy link
Copy Markdown
Owner

⚠️ Merge conflicts detected

Hi @Dev-sandy1,

This PR has merge conflicts that must be resolved before it can be merged.

To fix:

  1. Sync with the latest main branch: git fetch origin && git merge origin/main
  2. Resolve the conflicts in your code
  3. Push the resolved changes

Once resolved, the PR will be automatically merged on the next run.


🤖 Drips Wave Review Agent

@Smartdevs17
Copy link
Copy Markdown
Owner

⚠️ Merge conflicts detected

Hi @Dev-sandy1,

This PR has merge conflicts that must be resolved before it can be merged.

To fix:

  1. Sync with the latest main branch: git fetch origin && git merge origin/main
  2. Resolve the conflicts in your code
  3. Push the resolved changes

Once resolved, the PR will be automatically merged on the next run.


🤖 Drips Wave Review Agent

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

Labels

None yet

Projects

None yet

3 participants