Skip to content

fix: add security warning for raw PRIVATE_KEY usage in launch-token guide #1374

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
schoolkamsergj wants to merge 1 commit into
base: master
Choose a base branch
from
+4 −0
Open

fix: add security warning for raw PRIVATE_KEY usage in launch-token guide #1374

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/get-started/launch-token.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -245,6 +245,10 @@ contract DeployToken is Script {

### Environment Configuration

<Warning>
Never commit your `.env` file or share your `PRIVATE_KEY`. The raw private key approach shown below is intended for **local development and testing only**. For production deployments, use the more secure keystore method with `cast wallet import deployer --interactive` as described in the [Deploy Smart Contracts guide](https://docs.base.org/get-started/deploy-smart-contracts).
</Warning>

Create a `.env` file with your configuration:

```bash .env
Expand Down