THE .ENV PLEDGE

[PatrickAlphaC]

The Pledge

I solemnly swear, that I will never place a private key or secret phrase or mnemonic in a .env file that is associated with real funds.

I will only place private keys in a .env file that have ONLY testnet ETH, LINK, or other cryptocurrencies.

When I'm testing and developing, I will use a different wallet than the one associated with my real funds.

I am aware that if I forget a .gitignore and push my key/phrase up to GitHub even for a split-second, or show my key/phrase to the internet for a split second, it should be considered compromised and I should move all my funds immediately.

If I am unsure if my account has real funds in it, I will assume it has real funds in it. If I assume it has real funds in it, I will not use it for developing purposes.

I am aware that even if I hit add account on my metamask (or other ETH wallet) I will get a new private key, but it will share the same secret phrase/mnemonic of the other accounts generated in that metamask (or other ETH wallet).

Pledge Additions

For this course, I will only use funds associated with a brand new never-before-used metamask (or other ETH wallet). I am aware that my account associated with my private key is the same on testnets that it is on mainnets.

If I must use a private key associated with real funds in the future, until I am 100% sure what I am doing I will always either:

1. Use the encryption methods of dapptools keystore file
2. NEW Use the foundry's built-in keystore creator
3. Use the command line way to pass private keys, and delete my command line history right after

If I never actually deploy anything to mainnet myself or work with a private key with real funds, I do not need to be concerned.

[hardhat-freecodecamp]

I WILL BE SAFE

[Davebenex]

I MUST BE SAFE

[consigli3r3]

i will be safe

[Maron09]

I will be Safe

[VK024tech]

I will be safe

[umaarr01]

I WILL BE SAFE

[ghost]

I Wil Be Safe

[MaYatKit]

I WILL BE SAFE

[mirmohmmadluqman]

Why are you learning everything ???

[Arokyl]

I will be safe

[mrbiscuitoliva]

I WILL BE SAFE

[gandalf-blockchain]

I WILL BE SAFE

[xcodem]

@PatrickAlphaC thank you for the remarkable amount of effort you put into all you have done so far including this new course.

[humbletolearn]

I will be SAFE

[MajesticMinhaz]

I will be safe as you explain.

[AztecWarlord]

I will be safe.

[Aboudoc]

I WILL BE SAFE

[0xconstructor]

I WILL BE SAFE

[lostintime101]

I WILL BE SAFE

[thurendous]

I WILL BE SAFE! AGAIN!

[tormentr]

lmao , this is a great idea ! , ive done this so many times albeit not keys , but API tokens etc

[dzemojuka]

I WILL BE SAFE!

[Murat-U-Saglam]

I WILL BE SAFE. #SAFU

[ghost]

I WILL BE SAFE >:3333

[karanaroraeth]

I WILL BE SAFE.

[0xNiloy]

IWBS

[heysourin]

I WILL BE SAFE!!

[Nileshsri2022]

i will be safe

[ModatherAli]

The Pledge

I solemnly swear, that I will never place a private key or secret phrase or mnemonic in a .env file that is associated with real funds.

I will only place private keys in a .env file that have ONLY testnet ETH, LINK, or other cryptocurrencies.

When I'm testing and developing, I will use a different wallet than the one associated with my real funds.

I am aware that if I forget a .gitignore and push my key/phrase up to GitHub even for a split-second, or show my key/phrase to the internet for a split second, it should be considered compromised and I should move all my funds immediately.

If I am unsure if my account has real funds in it, I will assume it has real funds in it. If I assume it has real funds in it, I will not use it for developing purposes.

I am aware that even if I hit add account on my metamask (or other ETH wallet) I will get a new private key, but it will share the same secret phrase/mnemonic of the other accounts generated in that metamask (or other ETH wallet).

Pledge Additions

For this course, I will only use funds associated with a brand new never-before-used metamask (or other ETH wallet). I am aware that my account associated with my private key is the same on testnets that it is on mainnets.

If I must use a private key associated with real funds in the future, until I am 100% sure what I am doing I will always either:

1. Use the encryption methods of dapptools keystore file
2. NEW Use the foundry's built-in keystore creator
3. Use the command line way to pass private keys, and delete my command line history right after

If I never actually deploy anything to mainnet myself or work with a private key with real funds, I do not need to be concerned.

I WILL BE SAF

[didier-building]

I WILLL BE SAFE

[rukyy]

The Pledge

I solemnly swear, that I will never place a private key or secret phrase or mnemonic in a .env file that is associated with real funds.

I will only place private keys in a .env file that have ONLY testnet ETH, LINK, or other cryptocurrencies.

When I'm testing and developing, I will use a different wallet than the one associated with my real funds.

I am aware that if I forget a .gitignore and push my key/phrase up to GitHub even for a split-second, or show my key/phrase to the internet for a split second, it should be considered compromised and I should move all my funds immediately.

If I am unsure if my account has real funds in it, I will assume it has real funds in it. If I assume it has real funds in it, I will not use it for developing purposes.

I am aware that even if I hit add account on my metamask (or other ETH wallet) I will get a new private key, but it will share the same secret phrase/mnemonic of the other accounts generated in that metamask (or other ETH wallet).

Pledge Additions

For this course, I will only use funds associated with a brand new never-before-used metamask (or other ETH wallet). I am aware that my account associated with my private key is the same on testnets that it is on mainnets.

If I must use a private key associated with real funds in the future, until I am 100% sure what I am doing I will always either:

1. Use the encryption methods of dapptools keystore file
2. NEW Use the foundry's built-in keystore creator
3. Use the command line way to pass private keys, and delete my command line history right after

If I never actually deploy anything to mainnet myself or work with a private key with real funds, I do not need to be concerned.

I WILL BE SAFE

[aniketsahu115]

The Pledge

I solemnly swear, that I will never place a private key or secret phrase or mnemonic in a .env file that is associated with real funds.

I will only place private keys in a .env file that have ONLY testnet ETH, LINK, or other cryptocurrencies.

When I'm testing and developing, I will use a different wallet than the one associated with my real funds.

I am aware that if I forget a .gitignore and push my key/phrase up to GitHub even for a split-second, or show my key/phrase to the internet for a split second, it should be considered compromised and I should move all my funds immediately.

If I am unsure if my account has real funds in it, I will assume it has real funds in it. If I assume it has real funds in it, I will not use it for developing purposes.

I am aware that even if I hit add account on my metamask (or other ETH wallet) I will get a new private key, but it will share the same secret phrase/mnemonic of the other accounts generated in that metamask (or other ETH wallet).

Pledge Additions

For this course, I will only use funds associated with a brand new never-before-used metamask (or other ETH wallet). I am aware that my account associated with my private key is the same on testnets that it is on mainnets.

If I must use a private key associated with real funds in the future, until I am 100% sure what I am doing I will always either:

1. Use the encryption methods of dapptools keystore file
2. NEW Use the foundry's built-in keystore creator
3. Use the command line way to pass private keys, and delete my command line history right after

If I never actually deploy anything to mainnet myself or work with a private key with real funds, I do not need to be concerned.

i read the Pledge when one of my wallet got drained coz i pushed my .env file with private-key to github

[patricleehua]

I WILL BE SAFE!

[ilusif]

The Pledge
I solemnly swear, that I will never place a private key or secret phrase or mnemonic in a .env file that is associated with real funds.

I will only place private keys in a .env file that have ONLY testnet ETH, LINK, or other cryptocurrencies.

When I'm testing and developing, I will use a different wallet than the one associated with my real funds.

I am aware that if I forget a .gitignore and push my key/phrase up to GitHub even for a split-second, or show my key/phrase to the internet for a split second, it should be considered compromised and I should move all my funds immediately.

If I am unsure if my account has real funds in it, I will assume it has real funds in it. If I assume it has real funds in it, I will not use it for developing purposes.

I am aware that even if I hit add account on my metamask (or other ETH wallet) I will get a new private key, but it will share the same secret phrase/mnemonic of the other accounts generated in that metamask (or other ETH wallet).

Pledge Additions
For this course, I will only use funds associated with a brand new never-before-used metamask (or other ETH wallet). I am aware that my account associated with my private key is the same on testnets that it is on mainnets.

If I must use a private key associated with real funds in the future, until I am 100% sure what I am doing I will always either:

Use the encryption methods of dapptools keystore file
NEW Use the foundry's built-in keystore creator
Use the command line way to pass private keys, and delete my command line history right after
If I never actually deploy anything to mainnet myself or work with a private key with real funds, I do not need to be concerned.

[alejoevilches]

I WILL BE SAFE

[Angineerss]

The Pledge

I solemnly swear, that I will never place a private key or secret phrase or mnemonic in a .env file that is associated with real funds.

I will only place private keys in a .env file that have ONLY testnet ETH, LINK, or other cryptocurrencies.

When I'm testing and developing, I will use a different wallet than the one associated with my real funds.

I am aware that if I forget a .gitignore and push my key/phrase up to GitHub even for a split-second, or show my key/phrase to the internet for a split second, it should be considered compromised and I should move all my funds immediately.

If I am unsure if my account has real funds in it, I will assume it has real funds in it. If I assume it has real funds in it, I will not use it for developing purposes.

I am aware that even if I hit add account on my metamask (or other ETH wallet) I will get a new private key, but it will share the same secret phrase/mnemonic of the other accounts generated in that metamask (or other ETH wallet).

Pledge Additions

For this course, I will only use funds associated with a brand new never-before-used metamask (or other ETH wallet). I am aware that my account associated with my private key is the same on testnets that it is on mainnets.

If I must use a private key associated with real funds in the future, until I am 100% sure what I am doing I will always either:

1. Use the encryption methods of dapptools keystore file
2. NEW Use the foundry's built-in keystore creator
3. Use the command line way to pass private keys, and delete my command line history right after

If I never actually deploy anything to mainnet myself or work with a private key with real funds, I do not need to be concerned.

I WILL BE SAFE

[TheWoodenPuppet]

I WILL BE SAFE

[jofizim]

I will be safe

…

On Sat, Dec 20, 2025, 7:19 PM Bilal ***@***.***> wrote: I WILL BE SAFE — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQYTP6SFM4ZVFMMM7SBU6JT4CUWEJAVCNFSM6AAAAAAXYOGKOSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMZQGQ4DSMA> . You are receiving this because you commented.Message ID: ***@***.*** .com>

[jadwint]

I WILL BE SAFE!!!

[Firespiko]

The Pledge

I solemnly swear, that I will never place a private key or secret phrase or mnemonic in a .env file that is associated with real funds.

I will only place private keys in a .env file that have ONLY testnet ETH, LINK, or other cryptocurrencies.

When I'm testing and developing, I will use a different wallet than the one associated with my real funds.

I am aware that if I forget a .gitignore and push my key/phrase up to GitHub even for a split-second, or show my key/phrase to the internet for a split second, it should be considered compromised and I should move all my funds immediately.

If I am unsure if my account has real funds in it, I will assume it has real funds in it. If I assume it has real funds in it, I will not use it for developing purposes.

I am aware that even if I hit add account on my metamask (or other ETH wallet) I will get a new private key, but it will share the same secret phrase/mnemonic of the other accounts generated in that metamask (or other ETH wallet).

Pledge Additions

For this course, I will only use funds associated with a brand new never-before-used metamask (or other ETH wallet). I am aware that my account associated with my private key is the same on testnets that it is on mainnets.

If I must use a private key associated with real funds in the future, until I am 100% sure what I am doing I will always either:

1. Use the encryption methods of dapptools keystore file
2. NEW Use the foundry's built-in keystore creator
3. Use the command line way to pass private keys, and delete my command line history right after

If I never actually deploy anything to mainnet myself or work with a private key with real funds, I do not need to be concerned.

I will be safe! Thank you for your wonderful course Patrick!

[elitecoder88]

I WILL BE SAFE!

[didier-building]

I WILLL BE SAFE

[urbaba92]

I will try to be safe

[chikwesi]

I WILL BE SAFE