Nex Vault

This package appears to implement the described local vault, but packaging inconsistencies mean you should verify before installing: 1) Confirm which environment variables the code actually reads — search for NEX_VAULT_TELEGRAM_BOT_TOKEN and NEX_VAULT_TELEGRAM_CHAT_ID (these are used by the code). Do not assume VAULT_TELEGRAM_* vars will be picked up. 2) Run setup.sh only in a controlled environment (a disposable VM, container, or dedicated user account) so the installer (venv, DB, symlink) cannot affect unrelated data. 3) Limit the Telegram bot token's scope and rotate it after testing; the tool sends messages to api.telegram.org only. 4) Inspect the included setup.sh and Python files yourself (they are plain text) — they do not contain obfuscated or network-exfiltration code beyond Telegram calls. 5) If you will store sensitive contracts, ensure filesystem backups and permissions are appropriate (the tool creates ~/.nex-vault and sets 700 on it on Unix). 6) If you need the skill to integrate with your environment, update your environment variable names to match the code (NEX_VAULT_...) or modify lib/config.py to read the env vars you prefer. If you cannot verify these points, avoid installing in production until the packaging (metadata vs. code) is corrected.