All tx key pairs held in one location? | Mina Protocol | Page 1

surreal basalt Oct 23, 2023, 7:47 PM

#

Hi all, I just want to confirm that when I go to my .cache/zkapp-cli/keys folder I should expect to see listed ALL zkApp key pairs that have ever been created (no matter how many projects I've built). Does that sound correct?

split coral Oct 23, 2023, 10:26 PM

#

Hi! Yeah that's normal I have the exact same

surreal basalt Oct 23, 2023, 10:27 PM

#

split coral Hi! Yeah that's normal I have the exact same

Ok cool. Wasn't sure about that

split coral Oct 23, 2023, 10:27 PM

#

Just lists all your fee paying key pairs, which can even be used across multiple projects as well

#

no worries

surreal basalt Oct 23, 2023, 10:29 PM

#

maybe you also know the answer to another q that's been bugging me -- when I make a request for tMina via the Testnet faucet, the CLI will prepopulate the Mina address. I can't figure out what that address is.

#

and when I check out the explorer, it has that address as the payer key. weird to me

#

and yet, I'm left wondering, how can that be the fee payer key when it's not the key that's generated by CLI

split coral Oct 23, 2023, 10:31 PM

#

hmm so i'm not exactly sure what you mean

#

but essentially when you create a zkapp you will have two key pairs: a zkapp key pair and a fee payer key apir

#

The one in keys/ is your zkapp key pair, and is the main one you would reference in code

#

then like you said before the one in .cache is the fee payer to pay for zkapp deployments etc.

surreal basalt Oct 23, 2023, 10:35 PM

#

AH! It's the CLI-generated "zkApp" tx public key!

#

Thanks George!👍

#All tx key pairs held in one location?