Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Small fix in header height for stable layout in app and menu
…ork model and related components for improved network handling - Updated `package.json` to include `@number-flow/react` as a new dependency and modified script commands to specify port 6969. - Updated `yarn.lock` to reflect the addition of `@number-flow/react` and its dependencies. - Refactored `Network` model to enhance type definitions and added new types for better structure. - Updated various components to utilize the new `slug` property for network identification instead of `name`, improving consistency across the application. - Adjusted transaction explorer links and other references to align with the new network structure.
Implement new contract interactions
- Removed the FeeProvider context and associated logic from the application. - Updated components to directly use the new `useQuoteData` hook for fetching fee quotes. - Adjusted the `SwapForm`, `FeeDetailsComponent`, and related components to accommodate the new fee handling approach. - Enhanced the `DetailedEstimates` component to accept quote data directly, improving data flow and reducing unnecessary context dependencies. - Cleaned up imports and ensured all components are aligned with the new structure.
…s FRONT-876 FRONT-879
…ay logic - Replaced the deprecated FeeDetailsComponent with a new QuoteDetails component that utilizes an accordion for better UI/UX. - Integrated detailed fee calculations and display, including gas fees in USD and formatted fee amounts. - Updated the SwapForm to use the new QuoteDetails component, ensuring seamless integration with existing functionality. - Cleaned up imports and improved overall code structure for maintainability.
…orrect gas payment handling
…ollapsableHeader components to utilize resolveTokenLogoUrl utility for improved consistency and maintainability.
Bring route picker and fee fetching mechanism from layerswap, resolves FRONT-876 FRONT-879
Bring Address class to TRAIN, resolves FRONT-877
…remove duplicates
…s, and Details components to utilize NetworkSettings for improved maintainability and consistency.
Improve login logic, improve ui and handle the custom chain flow in login
…improve structure. Introduce TokenBalanceError type for better error management, update BalanceProvider for improved balance fetching, and streamline WalletProvider with new SelectAccountProps. Remove unused CurrencyFormField and NetworkFormField components for cleaner codebase.
- Removed unnecessary type imports and streamlined the registration of the Solana HTLC client by passing the config object directly. - Updated the wallet signing configuration to use a more straightforward type definition. - Adjusted tests to reflect changes in wallet handling, ensuring error messages are correctly validated. These changes enhance code clarity and maintainability in the Solana implementation.
Enforce type safety in HTLC and wallet sign registries
…is redeemed - Updated the refreshInterval logic to conditionally stop polling based on the lock status. - Integrated LockStatus from the SDK to improve type safety and clarity in the polling mechanism.
hydration sync so that clearing activeHashlock on swap completion is not overridden by a stale Next.js query param.
Fix: prevent stale hashlock from reopening finished swap modal
- Changed nativeTokenAddress and contractAddress to use a specific address for Solana Devnet. - Updated the KnownInternalNames class to reflect the new identifier for Solana Devnet, enhancing clarity and consistency in the codebase.
Update Solana contract
- Split read-only clients (sync useMemo via createHTLCClient) from write clients (async useEffect requiring wallet) in atomicContext; polling hooks now use read-only clients so they never carry a stale client from a previous swap/chain - Fix Solana recoverSwap: use Anchor EventParser for correct program attribution; fix all field accesses to snake_case (Anchor 0.30 preserves field names as-is); add null-guard in getUserLockDetails for non-Base58 contract addresses - Wrap getWalletClient in silent try-catch in useHTLCWriteClient to handle wagmi reconnection race condition (connector not ready yet) - Add Starknet Sepolia to NetworkSettings.KnownSettings with explorer URLs - Add mock quote for Starknet source chains in useFee.ts - RecoverSwap: use all networks (drop hardcoded filter), extract isValidTxHash helper, increase dropdown height, add styled-scroll Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ed data integrity
Record<caip2Id, IHTLCClient> map. Each network's client is managed by its own effect, resolving staleness per-network and naturally sharing one client when source and destination are on the same chain. Also removes the resolveClient wrapper indirection and adds the isProvidersReady guard to prevent creating write clients before wagmi reconnection completes
Implement recoverSwap functions, resolves FRONT-900
…ed on input values
…ackend is unavailable; commented out API client calls and related logic for improved testing.
…g, getters, and atomic operations, to streamline the codebase.
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
3 participants
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.
No description provided.