THE .ENV PLEDGE #5

PatrickAlphaC · 2022-05-13T13:13:47Z

PatrickAlphaC
May 13, 2022

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 Patrick showed (ideally)
Use some better encryption stuff Patrick didn't show
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.

EDIT

Look at all you safe people! I'd like all your comments if I could, but love how you're all being safe!! Keep it up!

hardhat-freecodecamp · 2022-05-13T13:21:20Z

hardhat-freecodecamp
May 13, 2022

I WILL BE SAFE

270 replies

RaccoonHacker Nov 22, 2025

i wll be safe

ReinaKaka Dec 16, 2025

I WILL BE SAFE

hozkareitor Dec 26, 2025

I WILL BE SAFE

ICMelvin May 21, 2026

I WILL BE SAFE!

Anmol-345 Jul 8, 2026

I WILL BE SAFE

DigitalOutbreak · 2022-05-27T20:02:35Z

DigitalOutbreak
May 27, 2022

I accept this pledge

6 replies

Gknan Oct 23, 2022

I WILL BE SAFE. THANK U.

nurdinuzakov Feb 3, 2023

I WILL BE SAFE

Webitect0x May 29, 2023

I WILL BE SAFE

Kolade1024 Apr 16, 2024

I WILL BE SAFE

Cnsackey50 Nov 3, 2025

I will be safe

mitchhs12 · 2022-05-27T21:07:54Z

mitchhs12
May 27, 2022

I WILL BE SAFE

0 replies

f41z37 · 2022-05-28T01:35:21Z

f41z37
May 28, 2022

I WILL BE SAFE

4 replies

stevegee1 Jun 22, 2022

I WILL BE SAFE!

arnold-zhang-jlu Jun 15, 2024

I WILL BE SAFE

Magkingin Sep 17, 2024

I ACCEPT THE PLEDGE

Anmol-345 Jul 8, 2026

I WILL BE SAFE!

danielhumgon · 2022-05-28T03:46:29Z

danielhumgon
May 28, 2022

I accept this pledge

1 reply

meilizhou1999 Aug 14, 2022

I WLL BE SAFE,THANKS

wenhan-zh · 2022-05-29T02:22:03Z

wenhan-zh
May 29, 2022

I WILL BE SAFE 🤞

1 reply

walosha Nov 6, 2022

I WILL BE SAFE

cipher222 · 2022-05-29T02:34:01Z

cipher222
May 29, 2022

I accept this pledge. Also, if I accidentally leaked the private key of one metta mask account would my other ones with actual eth be in jeopardy? Not that I have done so or anything... :|

4 replies

nehal2210 May 30, 2022

your private key of testNet account is the same as your private key of mainNet account. So be careful.

aranyadan Jun 17, 2022

no, different accounts will have different private keys. if you leak the mnemonic, however, consider all accounts compromised

shoaibshebi Jul 11, 2022

2 points:

1- if you leaked your private key associated with your actual meta account with holdings of eth, you are at risk coz. But if you have exposed P.K of some other account it's totally fine.

2-if you exposed your pneumonic at any account, your whole metamask is at risk and all accounts, coz it's same of all accounts and you metamask even.

thurendous Jul 16, 2022

The thing is it is quite sad to use a mnemonic with some accounts being compromised in it. This just doesn't fit. There will be a risk when you forgot that.

pranav3714 · 2022-05-29T14:17:54Z

pranav3714
May 29, 2022

I WILL BE SAFE

0 replies

Shalupanwar06 · 2022-05-30T08:13:30Z

Shalupanwar06
May 30, 2022

I WILL BE SAFE

0 replies

celalaksu · 2022-05-30T08:35:54Z

celalaksu
May 30, 2022

I WILL BE SAFE

0 replies

crypte-1 · 2022-05-30T09:57:52Z

crypte-1
May 30, 2022

I accept this pledge

0 replies

Equious · 2022-05-30T12:10:45Z

Equious
May 30, 2022

I will be safe. Even if all this encryption stuff is confusing as hell. :P

3 replies

br0wnD3v Jul 26, 2022

Felt this.

supaari89 Sep 1, 2022

I'm with you on this

realdezzy Jan 25, 2023

cryptography takes time to grasp, but it's the backbone of the internet's security

nehal2210 · 2022-05-30T12:20:44Z

nehal2210
May 30, 2022

I WILL BE SAFE

0 replies

patrick-pc · 2022-05-30T18:18:48Z

patrick-pc
May 30, 2022

I WILL BE SAFE

0 replies

02b2 · 2022-05-30T23:09:16Z

02b2
May 30, 2022

I WILL BE SAFE :)

1 reply

viveksharma1101980 Feb 13, 2023

i will be safe

0503xqy · 2025-07-30T10:14:04Z

0503xqy
Jul 30, 2025

I will be safe

0 replies

IKMC · 2025-07-30T21:42:22Z

IKMC
Jul 30, 2025

Yesser, i will try to be... You coming from Patrick's freecodecamp vid ryt.. also a fellow blockchain developer. Nice to meet you

…

On Wed, Jul 30, 2025 at 11:15 AM Ray Xu ***@***.***> wrote: I will be safe — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZ4P53CLHDP2NPXAOI3IC2L3LCLK5AVCNFSM5V3LFKSKU5DIOJSWCZC7NNSXTOSENFZWG5LTONUW63SDN5WW2ZLOOQ5TCMZZGMZDQOBX> . You are receiving this because you commented.Message ID: <smartcontractkit/full-blockchain-solidity-course-js/repo-discussions/5/comments/13932887 @github.com>

1 reply

JoshBolu Sep 25, 2025

nice to meet you too

Maverickililee · 2025-08-28T11:54:57Z

Maverickililee
Aug 28, 2025

I WILL BE SAFE

0 replies

ebrahimstb · 2025-08-28T14:44:40Z

ebrahimstb
Aug 28, 2025

Yk this course have outdated info a lot and would say you check Patrick’s x account he advised to go learn from updraft a place he working now and have the up to date course

…

On Thu, 28 Aug 2025 at 12:55, Maverick ***@***.***> wrote: I WILL BE SAFE — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AT4VGMM6CKZQB5XEYOV7CU33P3U4RAVCNFSM5V3LFKSKU5DIOJSWCZC7NNSXTOSENFZWG5LTONUW63SDN5WW2ZLOOQ5TCNBSGQ2DMOBX> . You are receiving this because you commented.Message ID: <smartcontractkit/full-blockchain-solidity-course-js/repo-discussions/5/comments/14244687 @github.com>

0 replies

jvcByte · 2025-09-12T20:00:13Z

jvcByte
Sep 12, 2025

i will be safe 😭😭😭

0 replies

CodeEnthusiast09 · 2025-09-18T16:02:22Z

CodeEnthusiast09
Sep 18, 2025

I WILL BE SAFE

0 replies

wls503pl · 2025-10-17T01:59:27Z

wls503pl
Oct 17, 2025

I will be safe.

0 replies

ghost · 2025-10-22T11:12:31Z

ghost
Oct 22, 2025

I WILL BE SAFE.

0 replies

ChrisforCrystal · 2025-10-23T15:59:11Z

ChrisforCrystal
Oct 23, 2025

I WILL BE SAFE.

0 replies

browngres · 2025-10-29T15:40:27Z

browngres
Oct 29, 2025

I WILL BE SAFE.

0 replies

wilanzai · 2025-11-28T06:46:07Z

wilanzai
Nov 28, 2025

I WILL BE SAFE.

0 replies

sx1124746 · 2025-12-21T20:49:36Z

sx1124746
Dec 21, 2025

I WILL BE SAFE

0 replies

mouhinU · 2026-01-08T04:09:49Z

mouhinU
Jan 8, 2026

i wll be safe

0 replies

SilenceWuJ · 2026-01-09T13:27:14Z

SilenceWuJ
Jan 9, 2026

I will be safe

0 replies

ranjbar-dev · 2026-01-23T13:39:34Z

ranjbar-dev
Jan 23, 2026

I ACCEPT THE PLEDGE

0 replies

THE .ENV PLEDGE #5

Uh oh!

Uh oh!

The Pledge

Pledge Additions

EDIT

Replies: 830 comments · 318 replies

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Replies: 830 comments 318 replies