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.
* feat: migrate proving system from UltraPlonk to UltraHonk * refactor: extract shared account formatter and replace magic numbers with constant * fix: resolve PR review issues for UltraHonk migration
* Instruct agent with 2 file * refactor(backend): rewrite llms.txt as agent playbook with verified ZK recipes Drop the auto-generated /llms-full.txt and replace the Swagger-dump /llms.txt with a single hand-written playbook covering the five flows agents actually need end to end: login, create account, single transfer, batch transfer, and gasless x402 deposit. The ZK proof section now ships complete TypeScript with every load-bearing constant pinned (BN254 modulus, circomlibjs Poseidon, UltraHonk with keccak transcript) because partial pseudocode silently produces proofs that fail on-chain verification. Every snippet was cross-checked against the live contract, the shared crypto utils, and the e2e test util to keep them in lockstep.
…254) Contract addresses derive from CREATE = keccak256(rlp(sender, nonce)) and do not include chainId, so the same relayer wallet produces identical addresses on Horizen and Base when nonces align. The previous `accounts.address @unique` global constraint blocked legitimate multi-chain deployments and also let guards mismatch members across chains. Schema: drop the global address unique, add composite (address, chainId) on accounts; add chain_id to transactions and reserved_nonces and replace the foreign key, unique, and indexes with composite versions. Migration backfills chain_id from the parent account row before promoting NOT NULL and refuses to run if any orphan transaction is found. Code: route every account lookup through (address, chainId) — guards require a chainId query param, services use the composite key, x402 keeps a findFirst since it is chain-scoped to Base. Frontend hooks and api services pass the current account's chainId everywhere they previously sent only the address.
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.
No description provided.