๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

Bluwhale
@bluwhaleai
World's #1# Intelligence Layer ๐Ÿ‡บ๐Ÿ‡ธ - The Fastest Growing AI Network Powered By You, Unlocking The Future of Financial Agents & Services With $BLUAI
๊ฐ€์ž… September 2022
121 ํŒ”๋กœ์ž‰ ์ค‘    226.1K ํŒฌ
๐Ÿ” Bluwhale Nodes Security Upgrade We've improved private key security based on community feedback. ๐Ÿ”’ What's Improved? ๐Ÿ”น Private keys are no longer stored in config files ๐Ÿ”น Keys are kept in protected memory ๐Ÿ”น Secure key loading via local Unix socket โš™๏ธ For Node Operators: 1๏ธโƒฃ Upgrade your Docker image from bf4c8e1 to bd5ca77: 2๏ธโƒฃ Remove privateKey from conf/config.yaml (`keySocketPath` is optional) 3๏ธโƒฃ Add ulimits.memlock to docker-compose.yaml 4๏ธโƒฃ Start your node, then load your private key via CLI โš ๏ธ Important: Nodes will only begin sending heartbeats after the private key is loaded. Thank you for helping us improve Bluwhale Nodes! ๐Ÿณ
๋” ๋ณด๊ธฐ