2026-07-19 · Hyperliquid · 3 条相关讨论
great! I will keep following your update. I have another question on your Outrive telegram bot, how do you ensure the wallet created by your bot is safe without any backdoor to steal users' private key? it's a serious concern
great! I will keep following your update. I have another question on your Outrive telegram bot, how do you ensure the wallet created by your bot is safe without any backdoor to steal users' private key? it's a serious concern
yea true. so here are technical details on how priv keys are managed. the main wallet private key uses envelope encryption: aws kms generates a 256-bit data key, the plaintext data key encrypts the wallet private key with Aes-256-GCM, then i store the encrypted private key, encrypted data key & other necessary details. same lifecycle for agent wallet After encryption, plaintext private key bytes and plaintext data key bytes are cleared from in memory. the private is also never use in trading, its only used when you need to withdraw & shown to you for export. there’s an extra layer of security which is vault, when vault is setup, sensitive actions such as key export & withdrawal isn’t done on tg anymore, they’re authorized on web with your passkey used during vault setup. - does this clarify your thinking? outrive docs also explains the key storage. also, my server-side secrets are not hardcoded or kept in plain .env files on the server; they’re managed through a dedicated secrets manager and injected securely into the services at runtime.
yea true. so here are technical details on how priv keys are managed. the main wallet private key uses envelope encryption: aws kms generates a 256-bit data key, the plaintext data key encrypts the wallet private key with Aes-256-GCM, then i store the encrypted private key, encrypted data key & other necessary details. same lifecycle for agent wallet After encryption, plaintext private key bytes and plaintext data key bytes are cleared from in memory. the private is also never use in trading, its only used when you need to withdraw & shown to you for export. there’s an extra layer of security which is vault, when vault is setup, sensitive actions such as key export & withdrawal isn’t done on tg anymore, they’re authorized on web with your passkey used during vault setup. - does this clarify your thinking? outrive docs also explains the key storage. also, my server-side secrets are not hardcoded or kept in plain .env files on the server; they’re managed through a dedicated secrets manager and injected securely into the services at runtime.
yeah, this is clear! it resolves my biggest concern on wallet safety, thanks for your detailed explanation
yeah, this is clear! it resolves my biggest concern on wallet safety, thanks for your detailed explanation