Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions

Zach pfp
Zach
@zachterrell
I have an API service that needs to write to a smart contract. Where do I store the private key? AWS KMS looks like cancer
10 replies
4 recasts
22 reactions

Zach pfp
Zach
@zachterrell
actually i might just put it in the .env
0 reply
2 recasts
7 reactions

Greg pfp
Greg
@greg
2 replies
0 recast
2 reactions

phil pfp
phil
@phil
In the .env file bro
1 reply
0 recast
0 reaction

Cassie Heart pfp
Cassie Heart
@cassie
Q KMS API preview coming in a few days
0 reply
0 recast
7 reactions

keccers pfp
keccers
@keccers.eth
AWS Kill My Self
0 reply
0 recast
5 reactions

osama pfp
osama
@osama
kms :( didn't turnkey have a product for this too? isn't this what you need? https://www.turnkey.com/product#onchain-automation cc @bryce
2 replies
0 recast
1 reaction

Greg pfp
Greg
@greg
i feel like @gregfromstl would have a take
1 reply
0 recast
1 reaction

‍‍ pfp
‍‍
@git
doppler.com 1password aws kms is good too
0 reply
0 recast
0 reaction

Leeward Bound pfp
Leeward Bound
@leewardbound
sops encrypt secrets in a yaml file and check them into repo
0 reply
0 recast
0 reaction

Degengineering | $DGNGX pfp
Degengineering | $DGNGX
@degengineering.eth
Assuming you want to use AWS services, I would recommend you to use AWS Secrets Manager to store either the private key as a byte encoded string or the seed phrase. I do not believe KMS supports the same kind of key and algorithms as the ones used by most blockchains 😉
0 reply
0 recast
0 reaction

blaynem pfp
blaynem
@drilkmops
Will it be exposed to users from some FE client? If no, just toss it in a .env? lol?
0 reply
0 recast
0 reaction