Lesson 9 - Private key in vm.startBroadcast()

[ericywl]

Given that cast now supports wallet imports: foundry-rs/foundry#6034, is it possible to get the wallet private key using forge instead of putting them in the .env file? For example, via some cheatcode that enables us to get the wallet and obtain the private key?

For reference, deploying via forge script already supports something like it via:

$ forge script script/DeploySimpleStorage.s.sol --rpc-url $SEPOLIA_RPC_URL --broadcast --account <some_account>

But forge test does not. Maybe something like the following would be great:

$ forge test --rpc-url $SEPOLIA_RPC_URL --account <some_account>

And then in tests

vm.getAccount().privateKey

[EngrPips]

Interesting, Maybe you can make that suggestion on Foundry official Github.

[Ikpong-Joseph]

Try running with forge test -f $SEPOLIA. Although I had the path to my keystore in my .env. I don't think it was used since I wasn't prompted for a password like when I tried running a Sepolia deploy script.

[EngrPips]

Try running with forge test -f $SEPOLIA. Although I had the path to my keystore in my .env. I don't think it was used since I wasn't prompted for a password like when I tried running a Sepolia deploy script.

Wouldn't this read the private key directly from the environment variable instead of reading it from the path to the keystore?

[Ikpong-Joseph]

The raw private key isn't in the .env. Only the path to its file in the keystore is. Try it.

…

On Sat, 22 Jun 2024, 07:36 EngrPips, ***@***.***> wrote: Try running with forge test -f $SEPOLIA. Although I had the path to my keystore in my .env. I don't think it was used since I wasn't prompted for a password like when I tried running a Sepolia deploy script. Wouldn't this read the private key directly from the environment variable instead of reading it from the path to the keystore? — Reply to this email directly, view it on GitHub <#1733 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BD7GOMB3OLCVKITNGN3EYMLZIULOFAVCNFSM6AAAAABH6JGMPWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQNBVGQYTA> . You are receiving this because you commented.Message ID: <Cyfrin/foundry-full-course-f23/repo-discussions/1733/comments/9845410@ github.com>

[EngrPips]

That is interesting. I will try it and let you know how it goes.

[Ikpong-Joseph]

Great. Let me know your experiences. I'm @Joseph__hpesoJ on X. Let's connect.

…

On Sat, 22 Jun 2024, 20:41 EngrPips, ***@***.***> wrote: That is interesting. I will try it and let you know how it goes. — Reply to this email directly, view it on GitHub <#1733 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BD7GOMHHSQLBA7GRRS72GDLZIXHPRAVCNFSM6AAAAABH6JGMPWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQNBYGY2TK> . You are receiving this because you commented.Message ID: <Cyfrin/foundry-full-course-f23/repo-discussions/1733/comments/9848655@ github.com>