Conversation
…ents (#200) - Updated QuestPage layout for better responsiveness with max-width and padding adjustments. - Changed BatchTransactions and TransactionSummary components to use flexbox for improved item alignment and responsiveness. - Enhanced QuestCard to allow for flexible width. - Added titles for new routes in the Title component.
* refactor: adjust z-index values across various components for improved UI layering * feat: add timing constants for HTTP timeouts, cache TTL, and retry delays - Introduced new timing constants in `timing.ts` for backend and nextjs packages. - Updated index files to export the new timing constants for better accessibility. refactor: replace hardcoded values with timing constants for retries and timeouts - Updated various services and modules to utilize new timing constants for retries and timeouts, improving maintainability and consistency across the codebase. - Adjusted `waitForReceiptWithRetry`, `PriceService`, `ZenTransferService`, `TransactionService`, and `ZkVerifyService` to use centralized timing configurations. refactor: replace hardcoded values with timing constants across components and hooks - Updated various components and hooks to utilize new timing constants for polling intervals, refetch intervals, and timeouts, enhancing maintainability and consistency throughout the codebase. - Adjusted `NotificationItem`, `ClaimSection`, `EditAccountModal`, and several hooks to reference centralized timing configurations. refactor: standardize formatting and improve component styles - Refactored various components to enhance code readability by standardizing formatting, including consistent indentation and spacing. - Updated styles across components to utilize new shadow and height constants for improved UI consistency. - Adjusted text sizes in multiple components to ensure uniformity in typography.
… sections (#206) - Updated ChooseNetwork component to include wallet connection checks and commitment validation, enhancing user experience with appropriate notifications. - Adjusted StatusContainer to allow copying of commitment addresses to clipboard for better usability. - Enhanced Sidebar component to incorporate wallet connection status in navigation logic.
* Refactor test * feat: enhance transaction E2E tests to support multi-asset transfers - Added support for ETH, ZEN, and USDC in transaction flow tests. - Introduced utility functions for ERC20 token transfers and balance checks. - Refactored account funding logic to accommodate multiple asset scenarios. - Updated test descriptions for clarity and consistency. * Add batch to e2e flow * Refactor test local * Change log for human read * clean up unused code * Test for staging * Change address ZEN token of horizen testnet * Refactor for DRY
* Improve UX of Transfer page * Improve UX of Batch page * Improve UX of EditAccountModal * Enhance transaction loading feedback in Dashboard and modals - Updated TransactionRow component to display detailed loading steps during transaction approval. - Integrated step loading functionality in useTransactionVote hook for improved user experience during transaction processes. * Changed button label from Transfer now to Submit Transfer to enhance user understanding during the transfer process.
* Payroll: Create batch for group * Change global css
- Enhanced readability by reformatting import statements and function parameters in `mixer.controller.ts`, `mixer.indexer.ts`, and `mixer.service.ts`. - Added new components for the Mixer UI: `DepositTab`, `WithdrawTab`, `MixerContainer`, and `PoolStats`. - Implemented hooks for managing deposits and withdrawals in `useMixerDeposit` and `useMixerWithdraw`. - Updated DTOs in the shared package to improve type validation. - Introduced new API methods in `mixerApi` for handling deposits and withdrawals.
- Added state management for cached commitments in `WithdrawTab` to optimize withdrawal processes. - Updated `getWithdrawableSlots` in `useMixerWithdraw` to return commitments alongside slots, reducing redundant API calls. - Refactored `useMixerKeys` to utilize refs for base secret management, improving performance during concurrent calls. - Adjusted `useMixerWithdraw` to accept commitments as parameters, streamlining the withdrawal flow.
Huygon764
force-pushed
the
feat/private-transfer
branch
from
4b64cc4 to
0f80cd2
Compare
Huygon764
force-pushed
the
develop
branch
4 times, most recently
from
a479f9a to
cc77d2a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Types of change
Comments (optional)
Allows users to deposit funds into a shared pool and withdraw to a different address with no on-chain link between deposit and withdrawal.
Flow:
Deposit: User → choose token & amount → confirm tx → funds enter Mixer pool (Poseidon commitment stored in on-chain Merkle tree)
Withdraw:
The user's wallet never appears in the withdrawal transaction — a relayer executes it on-chain.
Testing: deposit a fixed amount on Horizen/Base testnet → load deposits on Withdraw tab → select recipient → withdraw → verify funds arrive from the relayer address, not the user's wallet.