Best Practices

Follow these guidelines to maximize your privacy and security on KayakNet.

For All Users

1. Keep Software Updated

Always run the latest version:

./kayakd --auto-update

Updates include security patches and improvements.

2. Protect Your Identity Key

Your identity.key is your identity. If compromised, an attacker can impersonate you.

Do:

  • Back up to encrypted storage

  • Use strong device encryption

  • Delete if identity is burned

Don't:

  • Share with anyone

  • Store in cloud unencrypted

  • Use same identity for sensitive and non-sensitive activity

3. Use Strong Device Security

KayakNet can't protect you if your device is compromised:

  • Full disk encryption

  • Strong passwords/biometrics

  • Keep OS and apps updated

  • Don't install untrusted software

4. Separate Identities

Use different nodes/identities for:

  • Personal vs sensitive activity

  • Different personas

  • Testing vs production

5. Be Careful What You Share

Even with encryption:

  • Don't share real names, photos, locations

  • Assume messages may be saved by recipients

  • Be vague about identifying details

For Chat Users

Private Rooms

For sensitive discussions:

  1. Create a private room

  2. Only share name with trusted participants

  3. Use unique room names (not guessable)

Verifying Contacts

Before sensitive conversation:

  1. Verify Node ID through separate channel

  2. Use code words or shared secrets

  3. Be suspicious of identity claims

Message Hygiene

  • Enable auto-delete for sensitive chats

  • Clear history when done

  • Don't quote sensitive messages

For Marketplace Users

For Buyers

  1. Check seller reputation - Read reviews

  2. Start small - Test with small orders first

  3. Use escrow - Never pay outside escrow

  4. Verify addresses - Double-check crypto addresses

  5. Document everything - Save order details

For Sellers

  1. Secure crypto wallets - Hardware wallet recommended

  2. Accurate listings - Prevent disputes

  3. Ship securely - Don't reveal return address

  4. Good communication - Respond to buyers

  5. Separate business wallet - Don't mix with personal

Escrow Safety

  • Never release funds before confirming receipt

  • Open disputes promptly if issues arise

  • Provide evidence in disputes

  • Don't accept payment outside system

For High-Security Users

Additional Layers

Consider adding:

  • VPN (before KayakNet)

  • Tor (as transport)

  • Dedicated hardware

  • Air-gapped devices

Operational Security

  • Use public WiFi (carefully)

  • Vary your patterns

  • Assume you're being watched

  • Have plausible deniability

Compartmentalization

  • Different devices for different activities

  • Don't cross-contaminate identities

  • Separate digital footprints

For Node Operators

Secure Your Server

If running a public node:

  • Minimal installed software

  • Regular security updates

  • Firewall configuration

  • No unnecessary services

Logging Policy

  • Disable all logging

  • Don't retain connection metadata

  • Secure any necessary logs

Physical Security

  • Encrypted drives

  • Secure facility

  • Protection from seizure

Common Mistakes

Don't

❌ Use same identity across networks ❌ Connect to KayakNet without encryption ❌ Trust unverified contacts ❌ Store sensitive data unencrypted ❌ Use weak passwords ❌ Ignore software updates ❌ Share personal information ❌ Use KayakNet on compromised devices

Do

✅ Keep software updated ✅ Use strong device security ✅ Verify contacts ✅ Separate identities ✅ Back up keys securely ✅ Use private rooms for sensitive chats ✅ Always use escrow ✅ Report security issues responsibly

If Compromised

Signs of Compromise

  • Unexpected messages from your identity

  • Account settings changed

  • Unknown transactions

  • Peers report strange behavior

Recovery Steps

  1. Stop using compromised identity

  2. Generate new identity (delete identity.key)

  3. Notify trusted contacts through other channels

  4. Review device security

  5. Consider hardware replacement

Reporting Security Issues

Found a vulnerability?

  1. Don't disclose publicly

  2. Include detailed reproduction steps

  3. Allow 90 days for fix

  4. Coordinate disclosure

We appreciate responsible disclosure!

Last updated