The demo architecture
How the sandbox models a GPU-compute product — deterministically, and without touching a real network.
Simulated clusters
Nine demo tiers with fixed price, daily rate and term. Positions accrue on a schedule — no hardware, no billing.
Deterministic accrual
A cron-style engine credits daily yield, idempotent by date. Same inputs, same outputs, every run.
Mock acquiring
A sandbox acquirer emulates crypto-invoice creation and IPN callbacks with deterministic rates and demo addresses.
No real money path
There is deliberately no route to a real payment processor, blockchain or custody system. Invoices resolve against a mock rate table, addresses are synthetic, and settlement is simulated by a test trigger. The point is to study the flow, not to move value.
Two origins
Like the original, the demo separates a marketing origin from the application origin. This page lives on the marketing side; the cabinet and API live behind the app origin, and calls to action route across to it.
Polling, not sockets
Realtime surfaces — chat, notifications and invoice status — are modelled with periodic polling, mirroring the transport the original actually uses.
Idempotency as a habit
The state-changing steps — crediting daily yield, settling an invoice, claiming a balance — are written to be safe to repeat. Ledger entries are keyed so a job can run twice with no double-count, and settlement keys off a unique reference so a replayed callback is a no-op. It means the demo behaves correctly even when a trigger fires late, twice, or after a restart, which is exactly the property you want from the real thing.
One bundle, feature-detected
The whole marketing front is a static multi-page site driven by a single JavaScript bundle. Each widget — the ticker, the calculator, the journal, the FAQ accordion — activates only when it finds its own hook in the page, so the same code drives the home page and every sub-page without any per-page scripting. Rendered content is data-driven from typed source files, which keeps the copy in one place and the markup thin.