<!-- start pr-codex -->
## PR-Codex overview
This PR updates ZkCandy addresses for the Sepolia Testnet and ZKSync Era Mainnet.
### Detailed summary
- Added new addresses for various contracts on the Sepolia Testnet for ZkCandy.
- Updated addresses for DropERC721 on the ZKSync Era Mainnet.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
<!-- start pr-codex -->
## PR-Codex overview
This PR updates transaction options and serialization to use EIP712 instead of EIP721.
### Detailed summary
- Renamed `EIP721TransactionOptions` to `EIP712TransactionOptions`
- Renamed `EIP721SerializedTransaction` to `EIP712SerializedTransaction`
- Updated function parameters and return types accordingly
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
### TL;DR
Update PayEmbed and PayEmbed-disconnected tests to include conditional running based on TW_SECRET_KEY.
### What changed?
- Added conditional checks for TW_SECRET_KEY in PayEmbed-disconnected.test.tsx and PayEmbed.test.tsx
- Ensured tests run only if TW_SECRET_KEY is defined
### How to test?
1. Ensure TW_SECRET_KEY is set in your environment
2. Run the updated tests
3. Verify that the tests only execute if TW_SECRET_KEY is present
### Why make this change?
To add more robust control over test execution based on the presence of secret keys.
---
<!-- start pr-codex -->
---
## PR-Codex overview
The focus of this PR is to refactor test files for `PayEmbed` component by using `describe.runIf` to conditionally run tests based on the environment secret key.
### Detailed summary
- Refactored test files for `PayEmbed` component to conditionally run tests based on the secret key environment variable using `describe.runIf`.
- Updated test cases to improve readability and maintainability.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
### TL;DR
Added a warning that gets triggered once when the EOA signature verification fails and neither the chain nor the client parameter is provided in the verifySignature function. This is crucial to guide users on setting up smart accounts properly.
### What changed?
- Introduced a `warningTriggered` flag to ensure the warning is only logged once.
- Added a warning message to notify about missing chain and client parameters when EOA signature verification fails.
- Updated `isVerifyContractWalletSignatureParams` to explicitly check for undefined values in chain and client parameters.
### How to test?
1. Call the `verifySignature` function without providing the `chain` and `client` parameters.
2. Observe the console for the warning message.
3. Ensure the warning triggers only once even with multiple calls to `verifySignature` without the required parameters.
### Why make this change?
This change improves the developer experience by providing clear guidance when critical parameters are missing for using smart accounts with the Auth module. This helps in debugging and ensures proper setup for smart accounts.
---
<!-- start pr-codex -->
---
## PR-Codex overview
The focus of this PR is to add a warning message when verifying a signature without a chain or client provided.
### Detailed summary
- Added a warning message when verifying a signature without a chain or client
- Updated the `isVerifyContractWalletSignatureParams` function to check for `options.chain` and `options.client` values
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
<!-- start pr-codex -->
## PR-Codex overview
This PR focuses on exporting `getClaimConditionById` for Drop1155 in the `erc1155.ts` file.
### Detailed summary
- Export `getClaimConditionById` for Drop1155
- Import `GetClaimConditionByIdParams` from generated file
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
This pull request updates multiple test cases to use the `sendAndConfirmTransaction` method instead of the `sendTransaction` method. The tests affected include those for airdropERC1155WithSignature, airdropERC20WithSignature, airdropERC721WithSignature, claimERC1155, claimERC20, and claimERC721. The main goal is to ensure transactions are confirmed within the tests for improved reliability and accuracy.
### TL;DR
Replaced `sendTransaction` with `sendAndConfirmTransaction` in multiple test cases to ensure transactions are confirmed.
### What changed?
- Updated `airdropERC1155WithSignature.test.ts` to use `sendAndConfirmTransaction`
- Updated `airdropERC20WithSignature.test.ts` to use `sendAndConfirmTransaction`
- Updated `airdropERC721WithSignature.test.ts` to use `sendAndConfirmTransaction`
- Updated `claimERC1155.test.ts` to use `sendAndConfirmTransaction`
- Updated `claimERC20.test.ts` to use `sendAndConfirmTransaction`
- Updated `claimERC721.test.ts` to use `sendAndConfirmTransaction`
### How to test?
Run the test suite to ensure all tests pass with the updated method.
### Why make this change?
This change improves the reliability and accuracy of the test cases by ensuring that transactions are confirmed within the tests.
---
<!-- start pr-codex -->
---
## PR-Codex overview
This PR updates transaction handling in airdrop ERC contracts tests to use `sendAndConfirmTransaction` instead of `sendTransaction`.
### Detailed summary
- Replaced `sendTransaction` with `sendAndConfirmTransaction` in airdrop ERC contracts tests for better transaction handling.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
<!-- start pr-codex -->
## PR-Codex overview
The focus of this PR is to skip a flaky test for `eth_getLogs` and add a timeout to a test for rendering a connect wallet button.
### Detailed summary
- Skipped flaky test for `eth_getLogs`
- Added a timeout to the test for rendering a connect wallet button
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
## Problem solved
Short description of the bug fixed or feature added
## Changes made
- [ ] Public API changes: list the public API changes made if any
- [ ] Internal API changes: explain the internal logic changes
## How to test
- [ ] Automated tests: link to unit test file
- [ ] Manual tests: step by step instructions on how to test
## Contributor NFT
Paste in your wallet address below and we will airdrop you a special NFT when your pull request is merged.
```Address: ```
<!-- start pr-codex -->
---
## PR-Codex overview
The focus of this PR is to enhance the dashboard page by adding new product sections with updated styling and icons.
### Detailed summary
- Added `fontWeight` and `letterSpacing` styling to dashboard section titles
- Updated product sections with new names, labels, descriptions, and icons
- Included a new "Pay" product section for easy fiat onramps integration
- Improved the "Connect UI" section to "Sign in" with updated description
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
## Problem solved
Short description of the bug fixed or feature added
## Changes made
- [ ] Public API changes: list the public API changes made if any
- [ ] Internal API changes: explain the internal logic changes
## How to test
- [ ] Automated tests: link to unit test file
- [ ] Manual tests: step by step instructions on how to test
## Contributor NFT
Paste in your wallet address below and we will airdrop you a special NFT when your pull request is merged.
```Address: ```
<!-- start pr-codex -->
---
## PR-Codex overview
The focus of this PR is to update error handling messages and add loading overlays in the PayAnalytics components.
### Detailed summary
- Renamed `NoDataAvailable` function to `FailedToLoad` in `common.tsx`.
- Added `NoDataOverlay` function in `common.tsx`.
- Updated error handling and loading messages in `PayCustomersTable.tsx`.
- Updated error handling and loading messages in `PaymentHistory.tsx`.
- Updated error handling in `PaymentsSuccessRate.tsx`.
> The following files were skipped due to too many changes: `apps/dashboard/src/components/pay/PayAnalytics/components/PaymentsSuccessRate.tsx`, `apps/dashboard/src/components/pay/PayAnalytics/components/TotalVolumePieChart.tsx`, `apps/dashboard/src/components/pay/PayAnalytics/components/TotalPayVolume.tsx`, `apps/dashboard/src/components/pay/PayAnalytics/components/PayNewCustomers.tsx`, `apps/dashboard/src/components/pay/PayAnalytics/components/Payouts.tsx`
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
### TL;DR
This PR refactors the SponsorshipPolicies component to include an 'enabled' boolean field within the serverVerifier object, and updates the related logic to enable conditional rendering based on this field.
### What changed?
- Added 'enabled' field in the serverVerifier validation schema
- Updated initial state and form submission logic to handle the 'enabled' field
- Modified conditional rendering logic in the GatedSwitch component to use the 'enabled' field
### How to test?
1. Go to the SponsorshipPolicies component
2. Toggle the GatedSwitch to enable/disable the serverVerifier settings
3. Ensure the form behaves as expected based on the enabled state
### Why make this change?
This refactor aims to simplify the management and conditional rendering of the serverVerifier settings by introducing an 'enabled' field. This makes the logic more intuitive and easier to maintain.
---
### TL;DR
Refactored the `ApplyForOpCreditsModal` component to simplify its usage and improve code maintainability. Updated related components to match this change.
### What changed?
- Removed `Modal` and related sub-components from `ApplyForOpCreditsForm.tsx` and adjusted the structure to use `Flex`.
- Simplified `ApplyForOpCreditsModal` by removing unnecessary props and state management, and updated its contents to directly return the form and additional modals.
- Updated references and affected components to use the new simplified `ApplyForOpCreditsModal`.
- Refactored `CreditsItem` component to use `useModalContext` for handling modals.
- Updated navigation link in `OnboardingSteps` to point to the new location of the form.
- Modified `SettingsGasCreditsPage` to directly include the updated `ApplyForOpCreditsModal` and added a link to the accelerator program's blog post.
### How to test?
1. Navigate to the gas credits application section in the dashboard settings.
2. Verify that the form for applying to the Optimism Superchain App Accelerator is displayed correctly and functions as expected.
3. Test the new navigation flow to ensure all links and modals work correctly after the refactor.
### Why make this change?
This refactor aims to simplify the modal implementation for applying for gas credits, reduce code complexity, and improve maintainability by removing unnecessary state management and props from the `ApplyForOpCreditsModal` component.
---
<!-- start pr-codex -->
---
## PR-Codex overview
The focus of this PR is to update the UI content related to gas credits and sponsorship applications in the dashboard settings.
### Detailed summary
- Updated UI content for applying to the Optimism Superchain App Accelerator.
- Refactored ApplyForOpCreditsForm UI structure.
- Enhanced ApplyForOpCreditsModal functionality.
- Modified CreditsItem UI for applying to gas credits.
- Removed ApplyForOpCreditsModal from OnboardingSteps component.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
<!-- start pr-codex -->
## PR-Codex overview
This PR fixes an error related to buying with Crypto transactions using InApp wallet.
### Detailed summary
- Fixed error in `ConfirmationScreen.tsx` related to Crypto transactions
- Added `walletIds` import from `@thirdweb-dev/wallets`
- Modified transaction request based on wallet type before sending
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
<!-- start pr-codex -->
## PR-Codex overview
This PR focuses on removing unused code related to payments, contracts, and webhooks in the dashboard app.
### Detailed summary
- Removed multiple GraphQL files, components, hooks, and pages related to payments, contracts, and webhooks
- Updated page IDs and routes
- Updated redirects for payments settings and contracts
- Updated usage interfaces and route configurations
- Updated dependencies and package.json
- Updated cache keys for payments and contracts
- Updated solutions pages and products, removed NFT-checkout references
> The following files were skipped due to too many changes: `apps/dashboard/src/pages/solutions/gaming.tsx`, `apps/dashboard/src/components/app-layouts/app.tsx`, `apps/dashboard/src/pages/dashboard/connect/pay.tsx`, `pnpm-lock.yaml`
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
## Problem solved
- update usage tracker schema with pay fields
- - chainName: String
- - tokenSymbol: String
- - dstChainId: UInt64
- - dstTokenAddress: String
- - dstChainName: String
- - dstTokenSymbol: String
- - msLatency: UInt64
- - toAmountUSDCents: UInt64
- - secondaryProvider: String
- - onRampId: String
## Changes made
- [x] service-utils: Update usage tracker schema
## How to test
## Contributor NFT
Paste in your wallet address below and we will airdrop you a special NFT when your pull request is merged.
```Address: ```
<!-- start pr-codex -->
---
## PR-Codex overview
This PR adds new fields to the `UsageEvent` schema in the `usage.ts` file of the `service-utils` package for Cloudflare worker usage tracking.
### Detailed summary
- Added `chainName`, `tokenSymbol`, `dstChainId`, `dstTokenAddress`, `dstChainName`, `dstTokenSymbol`, `msLatency`, `toAmountUSDCents`, `secondaryProvider`, and `onRampId` fields to `UsageEvent` schema.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
<!-- start pr-codex -->
## PR-Codex overview
The focus of this PR is to add a file type validation feature to the IPFS upload dropzone component.
### Detailed summary
- Added `useToast` for error notifications.
- Implemented file type validation to restrict uploading of certain file types.
- Display error toast for restricted file types.
- Updated file handling logic in the dropzone component.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
### TL;DR
This PR adds a section for testing changes in the React Native SDK to the contributing guidelines and updates the formatting of type versions in the `package.json` file.
### What changed?
1. **Contributing Guidelines**: Added detailed instructions for testing React Native changes by creating a local React Native project, linking local changes, and using tools like wml and watchman.
2. **Formatting in `package.json`**: Updated the formatting of type versions to a more compact and readable style.
### How to test?
1. Follow the newly added instructions in the contributing guidelines to create a local React Native project and test changes using wml and watchman.
2. Verify that the `package.json` file's type versions formatting is correct and does not affect the build process.
### Why make this change?
This change aims to provide clearer guidance for contributors who need to test React Native SDK changes and improve the readability of the `package.json` file.
---
<!-- start pr-codex -->
---
## PR-Codex overview
The focus of this PR is to update the `package.json` file in the `thirdweb` package and provide detailed instructions for testing React Native changes.
### Detailed summary
- Updated the `typesVersions` configuration in `package.json`
- Added instructions for testing React Native changes locally
- Provided steps for setting up `wml` and `watchman` for monitoring changes
- Included guidance on linking the local SDK to a React Native project
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->