Update Readme and ENV Sample

[bh2smith]

PR Type

documentation, configuration changes

---

Description

• Removed ETH_RPC environment variable from .env.sample and README.md.
• Added instruction to provide NEAR_ACCOUNT_PRIVATE_KEY for CLI tool usage in README.md.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	.env.sample Remove `ETH_RPC` from environment sample file                        .env.sample Removed ETH_RPC environment variable. +0/-1
Documentation	README.md Update README to reflect environment variable changes        README.md Removed ETH_RPC from environment variables section. Added instruction to provide NEAR_ACCOUNT_PRIVATE_KEY for CLI tool usage. +5/-4

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[mintbase-codium-pr-agent]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[mintbase-codium-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Security	Mention security practices for handling private keys To improve the security practices, it's advisable to mention that the private key should be kept secret and not be committed to version control systems. README.md [38] +# IMPORTANT: Keep your private key confidential and never commit it to version control. NEAR_ACCOUNT_PRIVATE_KEY= Suggestion importance[1-10]: 9 Why: Highlighting security practices for handling private keys is crucial. It helps prevent accidental exposure of sensitive information, which is a significant security concern.	9
Enhancement	Add a placeholder for NEAR_ACCOUNT_ID to guide users Consider adding a placeholder or default value for NEAR_ACCOUNT_ID to guide users on what value is expected here, enhancing usability. .env.sample [3] -NEAR_ACCOUNT_ID= +NEAR_ACCOUNT_ID=your_account_id_here Suggestion importance[1-10]: 8 Why: Adding a placeholder for NEAR_ACCOUNT_ID guides users on what value is expected, improving usability and reducing potential confusion.	8
	Provide guidance on obtaining a privateKey It's beneficial to add a brief explanation or link to documentation on how to obtain or generate a privateKey for new users. README.md [35] -To use the CLI tool provided here in `examples/*` you will also need to provide a privateKey for your Near account. +To use the CLI tool provided here in `examples/*`, you will need to provide a privateKey for your Near account. See [Near Documentation](https://docs.near.org) on how to generate a privateKey. Suggestion importance[1-10]: 8 Why: Providing a link to documentation on generating a privateKey is beneficial for new users. It enhances the usability of the documentation by offering clear guidance.	8
	Add a comment explaining the purpose of NEAR_ACCOUNT_PRIVATE_KEY It is recommended to add a comment explaining the purpose and usage of NEAR_ACCOUNT_PRIVATE_KEY to enhance clarity for users who may not be familiar with its function. README.md [38] +# This is your Near account's private key, used for signing transactions NEAR_ACCOUNT_PRIVATE_KEY= Suggestion importance[1-10]: 7 Why: Adding a comment explaining the purpose of NEAR_ACCOUNT_PRIVATE_KEY enhances clarity for users, especially those unfamiliar with the variable's function. This improves the documentation quality.	7