QuantumShieldOpen tools ↗
QUANTUM SHIELD / KNOWLEDGE BASEDownload text

Quantum Shield Operations

Version 1.1 | 4 October 2026 | Cloudflare main-domain deployment

Deployment boundary

The main website is quantumsshield.com, hosted through Cloudflare Workers and static assets. Namecheap is the registrar. The deployment entry point is cloudflare/worker.js and the configuration is cloudflare/wrangler.json. The older private Sites deployment is separate and is not the customer-facing architecture documented here.

The Cloudflare wrapper rejects caller-supplied identity headers and supplies an internal identity only after owner-session validation. Do not deploy src/worker.js directly as a publicly trusted identity boundary. Local Node.js development uses SQLite and is not proof of hosted access-control behavior.

Configuration and secrets

  • ASSETS: static asset binding.
  • DB: D1 workspace and rate-limit storage.
  • AI: Cloudflare Workers AI binding for the bounded source-review adapter.
  • ETHEREUM_RPC_URL and BASE_RPC_URL: configured provider endpoints.
  • OWNER_PASSWORD_HASH and SESSION_SECRET: owner authentication secrets; never put them in public files.
  • OWNER_ID and OWNER_EMAIL: owner identity mapping.
  • MONITORING_ENABLED: currently false; setting it does not itself create a schedule.

No payment keys or active QUS contract are configured. No private keys or seed phrases are required by public analysis. The existing owner password is managed privately and must not appear in published documentation, logs, or screenshots.

Public data flows

Public GET wallet/token/compare routes share a 30-check-per-IP hourly server budget. Domain checks have a separate 30/hour budget. Deep scans have 3/IP/hour and 20 total/day beta limits. Hash-based IP rate-limit keys are operational data, not a claim of anonymity. Review counter retention and cleanup before scaling.

Deep scans fetch public HTTPS text without owner cookies or credentials. URL validation, DNS screening, manual redirects, byte limits, and time budgets are defense in depth. They do not provide IP pinning or a general-purpose network sandbox. Never attach private-network/VPC reachability to this collector. A future dynamic browser collector needs separate isolation and assessment.

Cloudflare Workers AI currently uses GLM-4.7-Flash. Validate output shape and exact source excerpts; keep the model unable to override deterministic warnings. Monitor model retirement, invalid output, timeouts, quota exhaustion, and inference cost. A successful sample inference does not establish detection accuracy.

Image inspection runs locally in the browser. Wallet Activity calls public explorers directly. Browser fallbacks can reach RPC or reputation providers; keep these destinations explicit in page-specific content security policies and product disclosures.

Private workspace

The main-domain workspace is owner-only. Customer invitation and external API-key routes are disabled. The older workspace backend and SDK retain development functionality, but those capabilities are not publicly available merely because their source exists. Never share the owner session to onboard a customer.

Database records include reports, watches, alerts, access metadata, and rate limits. Applied migrations must remain immutable; use forward migrations. Verify backup restoration and access separation before enabling company onboarding. Establish retention, deletion, and incident-response procedures rather than claiming they are already automated.

Monitoring and payments remain disabled

Manual watch checks can create account-state change alerts. These are changes to observed data, not detections of an attack. Automatic jobs and email require explicit configuration, observed delivery, and failure recovery before being advertised as active.

The planned QUS supply is 1,000,000,000 tokens. Token deployment, customer billing, x402 settlement, and XPay integration are not active. Future payments need explicit price/asset/network/recipient validation, expiring quotes, replay resistance, settlement reconciliation, receipts, duplicate-charge prevention, and result recovery after delivery failure. Preserve free access until the actual paid release is ready.

Release and incident checks

Run the application tests, validate representative provider responses, and make live endpoint checks after deployment. Test source-fetch failures and unavailable AI as carefully as successful results. Inspect content and headers on public documentation downloads. Confirm public content never exposes owner secrets or company records.

Before expanding protection claims, complete an independent review, adversarial detection evaluation, recovery exercise, and operational readiness check. Record failed providers and affected capabilities, disable unreliable claims or integrations, and communicate material incidents through an established customer channel. This beta has no published production SLA or independently certified detection rate.

Team Treasury boundary

The public /treasury workspace uses separate wallet-signature sessions and D1 tables introduced in 0001_treasury.sql. The /treasury-owner aggregate dashboard remains protected by the existing owner cookie. Caller-supplied identity headers do not grant treasury access. /treasury?preview=1 contains disabled illustrative sample data, not an authentication bypass.

Email adapters are implemented for Resend and Cloudflare Email Sending but are not configured on this release. Keep the capability unavailable until sender-domain verification and delivery tests complete. Store provider credentials and AUTH_SECRET only as Worker secrets. Email sign-in cannot sign on-chain transactions. Detailed setup is in the repository treasury implementation guide.

Fund custody, on-chain execution and platform fees are disabled. No fee wallet has been supplied. Never activate a placeholder recipient or treat the platform owner as a fund signer. The current dashboard and database are centralized; the intended wallet authority must remain on-chain and independently accessible. See Team Treasury.