fix: configure helius endpoint credentials through env variables

Author: elribonazo

playground/multichain-react/.env.example

@@ -0,0 +1,5 @@
+# Helius RPC API Configuration
+# Optional: Helius RPC API key for enhanced Solana RPC performance
+# If not provided, the app will fall back to public Solana RPC endpoints
+# Get your API key from: https://www.helius.dev/
+HELIUS_API_KEY=your_helius_api_key_here

playground/multichain-react/README.md

@@ -6,65 +6,37 @@ A test dapp for the MetaMask Multichain API.
 
 `yarn`
 
-## Usage
-
-To start the development server:
-
-`yarn start`
-
-This will launch the test dapp, allowing you to interact with the MetaMask Multichain API.
-
-## Contributing
-
-#### This project uses the [MetaMask Module Template](https://github.com/MetaMask/metamask-module-template)
-
-### Setup
-
-- Install the current LTS version of [Node.js](https://nodejs.org)
-  - If you are using [nvm](https://github.com/creationix/nvm#installation) (recommended) running `nvm install` will install the latest version and running `nvm use` will automatically choose the right node version for you.
-- Install [Yarn](https://yarnpkg.com) v4 via [Corepack](https://github.com/nodejs/corepack?tab=readme-ov-file#how-to-install)
-- Run `yarn install` to install dependencies and run any required post-install scripts
+## Configuration
 
-### Testing and Linting
+### Environment Variables
 
-Run `yarn test` to run the tests once. To run tests on file changes, run `yarn test:watch`.
+This project supports optional environment variables for enhanced functionality:
 
-Run `yarn lint` to run the linter, or run `yarn lint:fix` to run the linter and fix any automatically fixable issues.
+#### Helius RPC API Key (Optional)
+For improved Solana RPC performance, you can configure a Helius API key:
 
-### Release & Publishing
+1. Copy the example environment file:
+   ```bash
+   cp .env.example .env.local
+   ```
 
-The project follows the same release process as the other libraries in the MetaMask organization. The GitHub Actions [`action-create-release-pr`](https://github.com/MetaMask/action-create-release-pr) and [`action-publish-release`](https://github.com/MetaMask/action-publish-release) are used to automate the release process; see those repositories for more information about how they work.
+2. Get a free API key from [Helius](https://www.helius.dev/)
 
-1. Choose a release version.
+3. Add your API key to `.env.local`:
+   ```
+   HELIUS_API_KEY=your_actual_api_key_here
+   ```
 
-   - The release version should be chosen according to SemVer. Analyze the changes to see whether they include any breaking changes, new features, or deprecations, then choose the appropriate SemVer version. See [the SemVer specification](https://semver.org/) for more information.
+**Note:** If no Helius API key is provided, the app will automatically fall back to public Solana RPC endpoints.
 
-2. If this release is backporting changes onto a previous release, then ensure there is a major version branch for that version (e.g. `1.x` for a `v1` backport release).
-
-   - The major version branch should be set to the most recent release with that major version. For example, when backporting a `v1.0.2` release, you'd want to ensure there was a `1.x` branch that was set to the `v1.0.1` tag.
-
-3. Trigger the [`workflow_dispatch`](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_dispatch) event [manually](https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow) for the `Create Release Pull Request` action to create the release PR.
-
-   - For a backport release, the base branch should be the major version branch that you ensured existed in step 2. For a normal release, the base branch should be the main branch for that repository (which should be the default value).
-   - This should trigger the [`action-create-release-pr`](https://github.com/MetaMask/action-create-release-pr) workflow to create the release PR.
-
-4. Update the changelog to move each change entry into the appropriate change category ([See here](https://keepachangelog.com/en/1.0.0/#types) for the full list of change categories, and the correct ordering), and edit them to be more easily understood by users of the package.
-
-   - Generally any changes that don't affect consumers of the package (e.g. lockfile changes or development environment changes) are omitted. Exceptions may be made for changes that might be of interest despite not having an effect upon the published package (e.g. major test improvements, security improvements, improved documentation, etc.).
-   - Try to explain each change in terms that users of the package would understand (e.g. avoid referencing internal variables/concepts).
-   - Consolidate related changes into one change entry if it makes it easier to explain.
-   - Run `yarn auto-changelog validate --rc` to check that the changelog is correctly formatted.
-
-5. Review and QA the release.
+## Usage
 
-   - If changes are made to the base branch, the release branch will need to be updated with these changes and review/QA will need to restart again. As such, it's probably best to avoid merging other PRs into the base branch while review is underway.
+To start the development server:
 
-6. Squash & Merge the release.
+`yarn start`
 
-   - This should trigger the [`action-publish-release`](https://github.com/MetaMask/action-publish-release) workflow to tag the final release commit and publish the release on GitHub.
+This will launch the test dapp, allowing you to interact with the MetaMask Multichain API.
 
-7. Publish the release on npm.
+## Contributing
 
-   - Wait for the `publish-release` GitHub Action workflow to finish. This should trigger a second job (`publish-npm`), which will wait for a run approval by the [`npm publishers`](https://github.com/orgs/MetaMask/teams/npm-publishers) team.
-   - Approve the `publish-npm` job (or ask somebody on the npm publishers team to approve it for you).
-   - Once the `publish-npm` job has finished, check npm to verify that it has been published.
+#### This project uses the [MetaMask Module Template](https://github.com/MetaMask/metamask-module-template)

playground/multichain-react/src/helpers/solana-method-signatures.ts

@@ -8,7 +8,14 @@ import { FEATURED_NETWORKS } from "../constants/networks";
 window.Buffer = Buffer;
 
 const SOLANA_RPC_CONFIG = {
-	endpoints: ["https://api.helius-rpc.com/?api-key=15319146-89d5-4685-a3c4-811991e5212f", "https://api.devnet.solana.com", "https://api.mainnet-beta.solana.com"],
+	endpoints: [
+		...(process.env.HELIUS_API_KEY
+			? [`https://api.helius-rpc.com/?api-key=${process.env.HELIUS_API_KEY}`]
+			: []
+		),
+		"https://api.devnet.solana.com",
+		"https://api.mainnet-beta.solana.com"
+	],
 	commitment: "confirmed" as Commitment,
 	fallbackBlockhash: "EETubP5AKHgjPAhzPAFcb8BAY1hMH639CWCFTqi3hq1k",
 };