feat: WIP tron swaps

.depcheckrc.yml

@@ -5,6 +5,7 @@ ignores:
   #
 
   - '@lavamoat/snow'
+  - '@lavamoat/webpack'
   - '@lavamoat/allow-scripts'
   - '@babel/runtime'
   - '@fortawesome/fontawesome-free'
@@ -27,6 +28,8 @@ ignores:
   - '@metamask/test-dapp'
   - '@metamask/test-dapp-multichain'
   - '@metamask/test-dapp-solana'
+  - '@metamask/snap-simple-keyring-site'
+  - '@metamask/snap-account-abstraction-keyring-site'
   - '@metamask/design-tokens' # Only imported in index.css
   - '@tsconfig/node22' # required dynamically by TS, used in tsconfig.json
   - '@sentry/cli' # invoked as `sentry-cli`
@@ -81,8 +84,6 @@ ignores:
   - '@babel/plugin-transform-logical-assignment-operators'
   # used in image optimization script
   - 'sharp'
-  - 'imagemin'
-  - 'imagemin-gifsicle'
   # trezor
   - 'ts-mixer'
   - '@testing-library/dom'
@@ -96,6 +97,8 @@ ignores:
   - '@metamask/bitcoin-wallet-snap'
   - '@metamask/solana-wallet-snap'
   - '@metamask/institutional-wallet-snap'
+  - '@metamask/gator-permissions-snap'
+  - '@metamask/permissions-kernel-snap'
 
 # files depcheck should not parse
 ignorePatterns:

.eslintrc.js

@@ -533,11 +533,7 @@ module.exports = {
      * `process.exit` to exit).
      */
     {
-      files: [
-        'development/**/*.js',
-        'test/e2e/benchmark.js',
-        'test/helpers/setup-helper.js',
-      ],
+      files: ['development/**/*.js', 'test/helpers/setup-helper.js'],
       rules: {
         'node/no-process-exit': 'off',
         'node/shebang': 'off',

.github/CODEOWNERS

@@ -65,19 +65,16 @@ tailwind.config.js                   @MetaMask/design-system-engineers
 **/pages/notification*/**                           @MetaMask/notifications
 **/utils/notification.util.ts                       @MetaMask/notifications
 
-# Identity team is responsible for authentication and backup and sync inside the Extension.
-# Slack handle: @identity_team | Slack channel: #metamask-identity
-**/identity/**                                          @MetaMask/identity
-
 # Accounts team is responsible for code related with snap management accounts
 # Slack handle: @accounts-team-devs | Slack channel: #metamask-accounts-team
 
 app/scripts/lib/snap-keyring                        @MetaMask/accounts-engineers
 
-# Multichain Accounts
-# This feature is owned by the multichain account tiger team
+# Multichain Accounts, Authentication, Backup and sync
+# Those features are owned by the multichain account tiger team
 # Slack handle: @multichain-accounts-devs | Slack channel: #metamask-bip44-team
 **/multichain-accounts/**                           @MetaMask/accounts-engineers
+**/identity/**                                      @MetaMask/accounts-engineers
 
 # Swaps-Bridge team to own code for the swaps folder
 ui/pages/swaps                                        @MetaMask/swaps-engineers
@@ -99,20 +96,24 @@ app/scripts/constants/snaps.ts       @MetaMask/core-platform
 # Co-owned by Confirmations and Snaps
 ui/components/app/metamask-template-renderer @MetaMask/confirmations @MetaMask/core-platform
 
-# Wallet UX
-ui/components/app/whats-new-popup     @MetaMask/wallet-ux
-ui/css                                @MetaMask/wallet-ux
-ui/pages/home                         @MetaMask/wallet-ux
-ui/components/multichain/             @MetaMask/wallet-ux
-
-# Co-owned by accounts and wallet-ux
-ui/components/multichain/multi-srp/              @MetaMask/accounts-engineers @MetaMask/wallet-ux
-ui/components/multichain/account-picker/         @MetaMask/accounts-engineers @MetaMask/wallet-ux
-ui/components/multichain/account-details/        @MetaMask/accounts-engineers @MetaMask/wallet-ux
-ui/components/multichain/account-overview/       @MetaMask/accounts-engineers @MetaMask/wallet-ux
-ui/components/multichain/account-list-item/      @MetaMask/accounts-engineers @MetaMask/wallet-ux
-ui/components/multichain/account-list-menu/      @MetaMask/accounts-engineers @MetaMask/wallet-ux
-ui/components/multichain/account-list-item-menu/ @MetaMask/accounts-engineers @MetaMask/wallet-ux
+# Core Extension UX
+ui/components/app/whats-new-popup               @MetaMask/core-extension-ux
+ui/css                                          @MetaMask/core-extension-ux
+ui/pages/home                                   @MetaMask/core-extension-ux
+ui/pages/core                                   @MetaMask/core-extension-ux
+ui/components/multichain/                       @MetaMask/core-extension-ux
+ui/components/app/transaction-list              @MetaMask/core-extension-ux
+ui/components/app/transaction-list-item-details @MetaMask/core-extension-ux
+ui/components/app/transaction-list-item         @MetaMask/core-extension-ux
+
+# Co-owned by accounts and core-extension-ux
+ui/components/multichain/multi-srp/              @MetaMask/accounts-engineers @MetaMask/core-extension-ux
+ui/components/multichain/account-picker/         @MetaMask/accounts-engineers @MetaMask/core-extension-ux
+ui/components/multichain/account-details/        @MetaMask/accounts-engineers @MetaMask/core-extension-ux
+ui/components/multichain/account-overview/       @MetaMask/accounts-engineers @MetaMask/core-extension-ux
+ui/components/multichain/account-list-item/      @MetaMask/accounts-engineers @MetaMask/core-extension-ux
+ui/components/multichain/account-list-menu/      @MetaMask/accounts-engineers @MetaMask/core-extension-ux
+ui/components/multichain/account-list-item-menu/ @MetaMask/accounts-engineers @MetaMask/core-extension-ux
 
 # Web3Auth / Onboarding
 ui/pages/onboarding-flow              @MetaMask/web3auth
@@ -141,6 +142,9 @@ ui/components/ui/nft-collection-image                 @MetaMask/metamask-assets
 app/scripts/controller-init/smart-transactions    @MetaMask/transactions
 app/scripts/lib/smart-transaction                 @MetaMask/transactions
 
+# New networks
+shared/lib/multichain/addresses/* @MetaMask/new-networks
+
 # QA Team - E2E Framework
 test/e2e/page-objects/                    @MetaMask/qa
 test/e2e/seeder/                          @MetaMask/qa
@@ -151,6 +155,21 @@ test/e2e/helpers.js                       @MetaMask/qa
 test/e2e/mock-e2e-allowlist.js            @MetaMask/qa
 test/e2e/mock-e2e.js                      @MetaMask/qa
 
-# Wallet API Platform - Page Load Benchmark
-test/e2e/page-objects/benchmark           @MetaMask/wallet-api-platform-engineers
-test/e2e/playwright/benchmark             @MetaMask/wallet-api-platform-engineers
+# Wallet Integrations
+app/scripts/lib/rpc-method-middleware                                 @MetaMask/wallet-integrations
+shared/lib/caip25-caveat-merger.ts                                    @MetaMask/wallet-integrations
+test/e2e/page-objects/benchmark                                       @MetaMask/wallet-integrations
+test/e2e/playwright/benchmark                                         @MetaMask/wallet-integrations
+test/e2e/flask/multichain-api                                         @MetaMask/wallet-integrations
+# TODO CONSOLIDATE THE MIDDLEWARE BELOW INTO THE RPC-METHOD-MIDDLEWARE FOLDER
+app/scripts/lib/createRPCMethodTrackingMiddleware.js                  @MetaMask/wallet-integrations
+app/scripts/lib/createMetamaskMiddleware.js                           @MetaMask/wallet-integrations
+app/scripts/lib/createOnboardingMiddleware.js                         @MetaMask/wallet-integrations
+app/scripts/lib/createMetaRPCHandler.js                               @MetaMask/wallet-integrations
+app/scripts/lib/createEvmMethodsToNonEvmAccountReqFilterMiddleware.ts @MetaMask/wallet-integrations
+app/scripts/lib/createHyperliquidReferralMiddleware.ts                @MetaMask/wallet-integrations
+app/scripts/lib/metaRPCClientFactory.ts                               @MetaMask/wallet-integrations
+app/scripts/lib/middleware/                                           @MetaMask/wallet-integrations
+app/scripts/lib/createOriginThrottlingMiddleware.ts                   @MetaMask/wallet-integrations
+app/scripts/lib/createMainFrameOriginMiddleware.ts                    @MetaMask/wallet-integrations
+app/scripts/lib/createTracingMiddleware.ts                            @MetaMask/wallet-integrations

.github/guidelines/LABELING_GUIDELINES.md

@@ -2,38 +2,41 @@
 
 To maintain a consistent and efficient development workflow, we have set specific label guidelines for all pull requests (PRs). Please ensure you adhere to the following instructions:
 
-### Mandatory team labels:
+## Mandatory team label (automated)
 
 - **Internal Developers**: Every PR raised by an internal developer must include a label prefixed with `team-` (e.g., `team-extension-ux`, `team-extension-platform`, etc.). This indicates the respective internal team responsible for the PR.
 
 - **External Contributors**: PRs submitted by contributors who are not part of the organization will be automatically labeled with `external-contributor`.
 
-It's essential to ensure that PRs have the appropriate labels before they are considered for merging.
+## Mandatory checklog entry or label (manual addition)
 
-### Mandatory release version labels:
+The releases changelog generation is based on PR's changelog entries.
+The check can be bypassed when necessary, either by setting the changelog entry to "null" or by adding following label:
 
-- **release-x.y.z**: This label is automatically added to a PR and its linked issues upon the PR's merge. The `x.y.z` in the label represents the version in which the changes from the PR will be included. This label is auto-generated by a [GitHub action](../workflows/add-release-label.yml), which determines the version by incrementing the minor version number from the most recent release. Manual intervention is only required in specific cases. For instance, if a merged PR is cherry-picked into a release branch, typically done to address Release Candidate (RC) bugs, the label would need to be manually updated to reflect the correct version.
-- **regression-prod-x.y.z**: This label is automatically added to a bug report issue at the time of its creation. The `x.y.z` in the label represents the version in which the bug first appeared. This label is auto-generated by a [GitHub action](../workflows/check-template-and-add-labels.yml), which determines the `x.y.z` value based on the version information provided in the bug report issue form. Manual intervention is only necessary under certain circumstances. For example, if a user submits a bug report and specifies the version they are currently using, but the bug was actually introduced in a prior version, the label would need to be manually updated to accurately reflect the version where the bug originated.
-- **regression-RC-x.y.z**: This label is manually added to a bug report issue by release engineers when a bug is found during release regerssion testing phase. The `x.y.z` in the label represents the release candidate (RC) version in which the bug's been discovered.
+- **no-changelog**: PR's changes do not need to be included in the changelog.
+
+## Optional labels (manual addition)
+
+Any label can be manually added on demand depending on the PR's content. For instance, the label **QA passed** will indicate that a thorough manual testing has been performed and the PR is ready to be merged. In addition, following labels have some specific use cases.
 
-### Optional labels:
+### Bypass Quality Gates
 
-- **regression-main**: This label can manually be added to a bug report issue at the time of its creation if the bug is present on the development branch, i.e., `main`, but is not yet released in production.
-- **feature-branch-bug**: This label can manually be added to a bug report issue at the time of its creation if the bug is present on a feature branch, i.e., before merging to `main`.
-- **needs-qa**: If the PR includes a new features, complex testing steps, or large refactors, this label must be added to indicated PR requires a full manual QA prior being merged and added to a release.
+Using any of these labels should be exceptional in case of CI friction and urgencies. Please use them reasonably and verify new changes and regressions manually.
 
-### Labels prohibited when PR needs to be merged:
+- **skip-e2e-quality-gate**: This label will disable the default test retries for E2E test files modified in the PR. Useful when making large refactors or when changes don't pose flakiness risk.
 
-Any PR that includes one of the following labels can not be merged:
+### Block merge if any is present
 
 - **needs-qa**: The PR requires a full manual QA prior to being merged and added to a release.
-- **QA'd but questions**: The PR has been checked by QA, but there are pending questions or clarifications needed on minor issues that were found.
-- **issues-found**: The PR has been checked by QA or other reviewers, and appeared to include issues that need to be addressed.
 - **need-ux-ds-review**: The PR requires a review from the User Experience or Design System teams.
 - **blocked**: There are unresolved dependencies or other issues blocking the progress of this PR.
 - **stale**: The PR has not had recent activity in the last 90 days. It will be closed in 7 days.
 - **DO-NOT-MERGE**: The PR should not be merged under any circumstances.
 
+## Release version label (automated)
+
+- **release-x.y.z**: This label is automatically added to a PR and its linked issues upon the PR's merge. The `x.y.z` in the label represents the version in which the changes from the PR will be included. This label is auto-generated by a [GitHub action](../workflows/add-release-label.yml), which determines the version by incrementing the minor version number from the most recent release. Manual intervention is only required in specific cases. For instance, if a merged PR is cherry-picked into a release branch, typically done to address Release Candidate (RC) bugs, the label would need to be manually updated to reflect the correct version.
+
 To maintain code quality and project integrity, it's crucial to respect these label guidelines. Please ensure you review and update labels appropriately throughout the PR lifecycle.
 
 Thank you for your cooperation!

.github/scripts/benchmark-stats-commit.sh

@@ -9,13 +9,13 @@ if [[ -z "${EXTENSION_BENCHMARK_STATS_TOKEN:-}" ]]; then
     exit 1
 fi
 
-if [[ -z "${GITHUB_SHA:-}" ]]; then
-    printf '%s\n' 'GITHUB_SHA environment variable must be set'
+if [[ -z "${HEAD_COMMIT_HASH:-}" ]]; then
+    printf '%s\n' 'HEAD_COMMIT_HASH environment variable must be set'
     exit 1
 fi
 
-if [[ -z "${GITHUB_REPOSITORY_OWNER:-}" ]]; then
-    printf '%s\n' 'GITHUB_REPOSITORY_OWNER environment variable must be set'
+if [[ -z "${OWNER:-}" ]]; then
+    printf '%s\n' 'OWNER environment variable must be set'
     exit 1
 fi
 
@@ -33,7 +33,7 @@ git fetch origin main:main
 
 git checkout main
 
-BENCHMARK_FILE="../test-artifacts/benchmarks/benchmark-results.json"
+BENCHMARK_FILE="../test-artifacts/benchmarks/page-load-benchmark-results.json"
 STATS_FILE="stats/page_load_data.json"
 TEMP_FILE="stats/page_load_data.temp.json"
 
@@ -53,13 +53,13 @@ jq . "${BENCHMARK_FILE}" > /dev/null || {
 }
 
 # Check if the SHA already exists in the stats file
-if jq -e "has(\"${GITHUB_SHA}\")" "${STATS_FILE}" > /dev/null; then
-    echo "SHA ${GITHUB_SHA} already exists in stats file. No new commit needed."
+if jq -e "has(\"${HEAD_COMMIT_HASH}\")" "${STATS_FILE}" > /dev/null; then
+    echo "SHA ${HEAD_COMMIT_HASH} already exists in stats file. No new commit needed."
     exit 0
 fi
 
 # Append new benchmark data correctly using jq
-jq --arg sha "${GITHUB_SHA}" --argjson data "$(cat "${BENCHMARK_FILE}")" \
+jq --arg sha "${HEAD_COMMIT_HASH}" --argjson data "$(cat "${BENCHMARK_FILE}")" \
     '. + {($sha): $data}' "${STATS_FILE}" > "${TEMP_FILE}"
 
 # Overwrite the original JSON file with the corrected version
@@ -68,9 +68,9 @@ mv "${TEMP_FILE}" "${STATS_FILE}"
 # Only add the JSON file
 git add stats/page_load_data.json
 
-git commit --message "Adding page load benchmark data at commit: ${GITHUB_SHA}"
+git commit --message "Adding page load benchmark data at commit: ${HEAD_COMMIT_HASH}"
 
-repo_slug="${GITHUB_REPOSITORY_OWNER}/extension_benchmark_stats"
+repo_slug="${OWNER}/extension_benchmark_stats"
 
 git push "https://metamaskbot:${EXTENSION_BENCHMARK_STATS_TOKEN}@github.com/${repo_slug}" main
 

.github/scripts/bundle.sh

@@ -4,6 +4,7 @@
 # * The environment variables used by the `run-build` step in `.github/workflows/run-build.yml`.
 # * The environment variables used by the `publish-release` step in `.github/workflows/publish-release.yml`.
 export APPLE_BETA_CLIENT_ID=""
+export APPLE_EXPERIMENTAL_CLIENT_ID=""
 export APPLE_FLASK_CLIENT_ID=""
 export APPLE_PROD_CLIENT_ID=""
 export CONTENTFUL_ACCESS_SPACE_ID=""
@@ -17,9 +18,11 @@ export FIREBASE_MESSAGING_SENDER_ID=""
 export FIREBASE_PROJECT_ID=""
 export FIREBASE_STORAGE_BUCKET=""
 export GOOGLE_BETA_CLIENT_ID=""
+export GOOGLE_EXPERIMENTAL_CLIENT_ID=""
 export GOOGLE_FLASK_CLIENT_ID=""
 export GOOGLE_PROD_CLIENT_ID=""
 export INFURA_BETA_PROJECT_ID=""
+export INFURA_EXPERIMENTAL_PROJECT_ID=""
 export INFURA_FLASK_PROJECT_ID=""
 export INFURA_PROD_PROJECT_ID=""
 export QUICKNODE_ARBITRUM_URL=""
@@ -30,6 +33,7 @@ export QUICKNODE_MAINNET_URL=""
 export QUICKNODE_OPTIMISM_URL=""
 export QUICKNODE_POLYGON_URL=""
 export SEGMENT_BETA_WRITE_KEY=""
+export SEGMENT_EXPERIMENTAL_WRITE_KEY=""
 export SEGMENT_FLASK_WRITE_KEY=""
 export SEGMENT_PROD_WRITE_KEY=""
 export ANALYTICS_DATA_DELETION_SOURCE_ID=""

.github/scripts/check-pr-has-required-labels.ts

@@ -42,8 +42,6 @@ async function main(): Promise<void> {
 
   const preventMergeLabels = [
     'needs-qa',
-    "QA'd but questions",
-    'issues-found',
     'need-ux-ds-review',
     'blocked',
     'stale',