UI Launch and Deployed on custom domain

Create backend to update token prices daily.

Create backend for URL confirmation notifications.

Create backend to update fiat prices.

Create backend for email notifications.

Integrate deeplinks to wallets on mobile.

Create backend to update order statuses.

Token Selection & Network Validation Improvements

Overview Major improvements to token selection UX and network validation system to prevent payment errors and enhance user experience. Key Features Added Token Selection Modal Replaced dropdown with full-featured modal for better mobile/desktop experience Added search functionali…

Network Configuration Consolidation

Create a Single Source of Truth for Networks

Initial Setup: Voulti Instant Payouts

Initialize the Voulti project as a multi-chain payout dashboard for global merchants to send stablecoin payouts.

Frontend Framework Integration

Set up the frontend using Next.js and ensure CSS bundling works correctly to start building the dashboard UI.

CSV Upload and Payout Modal

Add support for uploading payout lists via CSV to streamline bulk payment creation.

Privy Authentication Integration

Integrate Privy to enable user authentication and wallet creation within the Voulti app.

Documentation and Architecture Cleanup

Refactor codebase and document project structure to improve maintainability and onboarding.

Dashboard Navigation and Activity Module

Implement navigation between multiple pages and display historical payout and transaction data.

Receive Module and Payment Links

Build the “Receive” section where businesses can generate payment links and manage incoming funds.

Implement Receive Section

The application lacked a complete "Receive" section, which is essential for merchants to share payment links, connect recipients, and enable the full payout workflow.

Backend Services Integration

The application lacked backend integration, a commerce registration system, and user account management functionality, making it impossible to actually use the application with real data.

Integrate Payout Service

The frontend had no integration with the backend API, so payout creation, history retrieval, and commerce management were impossible without a working backend connection.

Implement Squid Integration

The application lacked integration with Squid Router for cross-chain token swaps, showed placeholder balance data instead of real blockchain balances, and had disorganized documentation.

Fix: Token Approval & Logging

Token approvals were failing due to incorrect amount units, and Squid-related errors had insufficient logging, making it difficult to debug swap failures and causing payout transactions to fail.

Production PayoutVault

The PayoutVault smart contract lacked production-ready security features and needed enhancements to handle real-world deployment scenarios safely.

Add Blockchain Config System

Vault configurations were scattered throughout the codebase without a clear, centralized management system, making it difficult to add new vaults, maintain existing ones, and ensure consistency across the application.

Implement Squid Post-Hook

After successful cross-chain swaps, tokens needed to be manually deposited into vaults, creating additional steps and potential failure points in the payout flow.

Fix: Squid Post-Hook Pattern

The Squid post-hook implementation was using an incorrect pattern for depositing funds into vaults, potentially causing transaction failures or incorrect fund handling.

Improve Payout Creation UX

The payout creation interface had usability issues and lacked clear visual feedback during the creation process, making it difficult for merchants to understand their progress and complete payouts.

Fix: Redeploy MXNB Vault

The MXNB (Mexican Peso) vault deployment had issues or the contract needed updates, and old deployment files were cluttering the contracts directory, making it difficult to track current deployed contracts.

Complete Recipient Portal

The recipient portal lacked integration with actual blockchain balances and a functional claim flow, showing only placeholder data without the ability to interact with real vault funds.

Complete Recipient Portal

The recipient portal lacked integration with actual blockchain balances and a functional claim flow, showing only placeholder data without the ability to interact with real vault funds.

Improve Recipient UX - Withdraw

Recipients had limited functionality for managing their funds, with no way to easily withdraw or understand their balance details, making the payout claim process incomplete.

Fix: pyUSD Decimals

The pyUSD token configuration had incorrect decimals (18 instead of 6) and possibly incorrect symbol display, causing balance calculation errors and incorrect amount displays throughout the merchant interface.

Improve Recipient UX Terminology

The recipient portal used technical terminology that might confuse end-users who aren't familiar with blockchain concepts, creating a barrier to understanding their available payments.

Fix: Infinite Reload Loops

The frontend was experiencing infinite reload loops due to unstable dependencies in useEffect hooks, particularly in components that fetch commerce data and wallet addresses, causing poor user experience and making the application unusable.

Add BRLA Vault Config

The system was configured to use cREAL token for Brazilian Real payouts, but Squid Router reported low liquidity for this token, preventing successful BRL payouts.

Fix: TypeScript Errors

TypeScript compilation errors were blocking development, and the documentation needed updates to reflect recent changes in the codebase architecture.

Fix: README to Reflect MVP

he README contained references to features not in the MVP (like bulk payouts), incorrect token names (BRL1 instead of BRLA), and incomplete environment variable documentation, making it difficult for developers to set up and understand the project's actual capabilities.

Simplify Privy Login

The Privy authentication setup used multiple login methods including embedded wallets, which added unnecessary complexity to the user onboarding flow and required more configuration.

Refactor: Centralize Network Configs

Network configurations, RPC URLs, and chain IDs were hardcoded throughout multiple frontend files (squid.service.ts, currencies.ts, payouts/page.tsx, page.tsx, use-token-balance.ts), making the codebase difficult to maintain and prone to inconsistencies when adding new networks o…

Fix: UI Issues After Payout

After successful payout creation, the UI had three critical issues: inconsistent date formatting between new and existing payouts, the merchant balance not updating automatically after transactions, and the modal maintaining stale state from previous payout attempts, which confus…

Proof of Ship - Season 6

I am applying to participate in the Proof of Ship - Season 6

Proof of Ship - Season 7

I am applying to participate in the Proof of Ship - Season 7

Proof of Ship - Season 9

I am applying to participate in the Proof of Ship - Season 9