Best Practices

Good security posture is not just about architecture. It is also about how testers and users approach the product in practice.

API Key Hygiene

Use dedicated keys for this product, not all-purpose exchange keys
Avoid withdrawal permissions whenever possible
Never paste secrets into public bug reports or chat logs
Treat screenshots and exported logs as potentially sensitive artifacts

Testnet First

The safest way to evaluate CryptoDesk AI is:

start with onboarding
use simulation mode
validate exchange-related behavior on testnet
keep expectations aligned with the current alpha scope

Alpha guidance

The current release is not positioned as a production live-trading environment. That limitation is intentional and should be respected during testing.

Backup and Recovery

While the product is local-first, testers should still operate with discipline:

keep a clean copy of release notes and checksums
record environment details when reporting bugs
retain backup plans for local machine failures
rotate exchange keys if anything ever feels suspicious