How to use Kryptex for cloud monitoring? (Mining software)

Understanding Kryptex Architecture

1. Kryptex operates as a Windows-based mining client that integrates with cloud infrastructure through persistent outbound connections to its central coordination servers.

2. It does not expose local ports or require inbound firewall rules, relying instead on HTTPS-based polling to retrieve updated mining configurations and submit share data.

3. The software embeds a lightweight telemetry module that captures GPU utilization, temperature, fan speed, and accepted/rejected share rates at five-second intervals.

4. All collected metrics are encrypted using AES-256-CBC before transmission, with keys rotated every 24 hours via secure key exchange with Kryptex’s authentication gateway.

5. Mining profiles—including algorithm selection, pool endpoints, and overclocking presets—are stored in the cloud and synchronized across devices upon startup or manual refresh.

Setting Up Cloud Monitoring Dashboard Access

1. Users must register an account on the official Kryptex portal using a valid email and two-factor authentication enabled via TOTP or hardware token.

2. After installation, the desktop client automatically registers the host machine using a cryptographically signed hardware fingerprint derived from CPU ID, disk volume serial, and MAC address.

3. The dashboard displays real-time hash rate per GPU, thermal throttling events, uptime percentage, and cumulative earnings denominated in BTC or USDT.

4. Custom alert thresholds can be configured for temperature spikes above 85°C, sustained hash rate drops exceeding 15% over three minutes, or consecutive rejected shares beyond ten.

5. Historical graphs support zoomable time ranges from one hour to ninety days, with export functionality limited to CSV format and restricted to authenticated sessions only.

Data Flow Between Local Miner and Cloud Service

1. Every 30 seconds, the client initiates a POST request to https://api.kryptex.app/v2/metrics/submit, carrying encrypted payload containing sensor readings and mining statistics.

2. The cloud backend validates the signature, decrypts the payload, and stores time-series records in a sharded TimescaleDB cluster segmented by user ID and device hash.

3. Pool communication remains entirely decoupled from Kryptex’s monitoring layer; no stratum traffic is intercepted, logged, or modified during operation.

4. Dashboard visualizations are rendered client-side using pre-fetched JSON blobs, minimizing server-side rendering load and reducing latency for concurrent users.

5. Failed metric submissions trigger exponential backoff with jitter, capped at five-minute intervals, while maintaining local ring-buffer storage of up to six hours of raw telemetry.

Security Controls and Permission Boundaries

1. API tokens issued to each device are scoped exclusively to telemetry ingestion and profile synchronization—no wallet access, no withdrawal capability, no administrative privileges.

2. Device deactivation requires explicit revocation through the web interface or automated suspension after 72 hours of zero metric submission.

3. All dashboard session cookies include HttpOnly, Secure, and SameSite=Strict attributes, preventing cross-site leakage or injection attacks.

4. Audit logs record every login attempt, device registration, token generation, and configuration change—with immutable storage in an append-only S3 bucket.

5. User data residency complies with GDPR Article 28 requirements, with processing confined to AWS Frankfurt and Amsterdam regions unless otherwise specified during onboarding.

Frequently Asked Questions

Q: Can I monitor multiple rigs under a single Kryptex account?A: Yes. Each rig registers as a distinct device with its own identifier and telemetry stream. The dashboard aggregates metrics by default but allows filtering by individual device name or group tag.

Q: Does Kryptex store raw GPU memory dumps or kernel-level process lists?A: No. Kryptex collects only surface-level sensor data and mining-specific counters. It does not access or transmit process memory, registry entries, or filesystem contents.

Q: Is there a way to disable telemetry without breaking mining functionality?A: Yes. Launching the client with the --no-metrics flag disables all outbound metric submissions while preserving full mining operations and pool connectivity.

Q: Are historical metrics retained if my subscription expires?A: Metrics older than 30 days are purged automatically upon subscription lapse. Active subscriptions retain data for up to 90 days regardless of billing status.