1. Operator Overview
This document provides technical and operational details for entities operating within or integrating with the Helios Digital Gold infrastructure. It covers custody operations, smart contract interactions, compliance integration, and platform API surfaces.
This document contains confidential operational details. Distribution is limited to approved institutional participants, platform partners, and authorized personnel. Unauthorized distribution is prohibited.
2. Infrastructure Architecture
2.1 System Topology
| Layer | Service | Provider | SLA |
|---|
| Edge / CDN | Cloudflare Pages + Workers | Cloudflare | 99.99% |
| Application | Next.js 16 static export | Self-hosted | 99.9% |
| Blockchain | Polygon PoS mainnet | Polygon Labs | 99.95% |
| Identity | .helios Namespace Registry | Helios Internal | 99.9% |
| Communications | Telnyx SMS / Voice API | Telnyx | 99.95% |
| AI Services | OpenAI GPT-4 + ElevenLabs | OpenAI / ElevenLabs | 99.9% |
| Custody | Regulated vault partners | TBD — Pre-launch | — |
2.2 Deployment Pipeline
- Source: GitHub main branch → CI/CD on push
- Build: Next.js static export → Cloudflare Pages deployment
- Smart Contracts: Hardhat → Polygon mainnet via secured deployer wallet
- Environment: .env.local for API keys (Telnyx, OpenAI, ElevenLabs)
- Monitoring: Cloudflare Analytics + custom event tracking
3. Smart Contract Specifications
3.1 Contract Suite
| Contract | Standard | Function |
|---|
| HeliosCertificate | ERC-721 | Individual gold certificate NFTs |
| HeliosBatchCert | ERC-1155 | Batch and multi-denomination certificates |
| HeliosVault | Custom | Vault management, staking, reserve tracking |
| HeliosNamespace | Custom | On-chain .helios identity registry |
| HeliosGovernance | Custom | Role-based access, minting authority |
3.2 Deployer Wallet
All smart contracts are deployed from a dedicated deployer wallet on Polygon. The deployer wallet is funded with MATIC for gas and operates under multi-signature authorization for production deployments. Private keys are stored in hardware security modules (HSM) with backup seed phrases in geographically distributed secure storage.
3.3 Upgrade Strategy
- Transparent proxy pattern (OpenZeppelin) for all upgradeable contracts
- Timelock controller with 48-hour delay for production upgrades
- Multi-sig approval required (2-of-3 minimum) for proxy upgrades
- Emergency pause function available to authorized operators
- Full audit trail of all contract upgrades stored on-chain and off-chain
4. Wallet & Vault Architecture
4.1 Wallet Types
| Wallet | Purpose | Provisioning |
|---|
| Primary Smart Wallet | Main member wallet for certificates and transactions | Auto-provisioned at onboarding |
| Vault Wallet | Long-term storage, staking, and reserve-linked certificates | Auto-provisioned at onboarding |
| Operating Wallet | Day-to-day platform interactions, gas, micro-transactions | Auto-provisioned at onboarding |
| Family Vault | Shared family-level gold storage | A la carte activation |
| Business Vault | Business entity gold management | A la carte activation |
| Strategic Vault | Institutional-scale reserve management | Premium tier activation |
5. Compliance Integration
5.1 KYC / AML Pipeline
- Identity verification at membership sign-up (document + biometric)
- Sanctions screening against OFAC, EU, and UN consolidated lists
- Enhanced due diligence for premium tiers ($25K+)
- Ongoing transaction monitoring with risk scoring
- Suspicious activity reporting workflow with case management
5.2 Trust Scoring
Every member carries a Helios Trust Score — a composite metric derived from verification status, transaction history, network participation, and compliance record. Trust scores influence access to advanced features, Gold Desk priority, and premium upgrade eligibility.
6. API Surface
Full API documentation will be published at platform launch (June 1, 2026). Pre-launch API access is available to approved institutional partners by request.
| Endpoint Category | Methods | Auth |
|---|
| Member Profile | GET, PATCH | Bearer JWT |
| Wallet Operations | GET, POST | Bearer JWT + 2FA |
| Certificate Issuance | POST | Bearer JWT + 2FA + Trust Score |
| Reserve Status | GET | Public (read-only) |
| Namespace Registry | GET, POST | Bearer JWT |
| Webhooks | POST | Signed HMAC |
7. Incident Response
7.1 Severity Levels
| Level | Description | Response Time |
|---|
| P0 — Critical | Platform-wide outage, security breach, reserve integrity | < 15 minutes |
| P1 — High | Major feature degradation, compliance system failure | < 1 hour |
| P2 — Medium | Non-critical feature issues, performance degradation | < 4 hours |
| P3 — Low | Minor UI issues, documentation errors | Next business day |
8. Contact
For operational inquiries, integration requests, or incident escalation, contact the Helios operations team through the platform's secure communication channel or via the institutional contact form at heliosdigital.xyz/contact.
