Helix ASIC array
An open accelerator rack. More compute increases potential output, but only if the energy and funding can support it.
- Balanced
- 100 CU / 60 EU
- Eco
- 60 CU / 28 EU
- Boost
- 150 CU / 110 EU
- Full output
- 0.02 sim sats / CU / s
ORBITAL WORKS / FIELD MANUAL 02
A station is a system.
Compute needs energy. Production needs somewhere to go. Build a balanced circuit, inspect its bottlenecks and run an experiment.
Return to your stationThree roles. One circuit.
These are original game modules with deliberately simplified specifications. CU, EU and simulated sats are game units, not real hardware ratings or financial forecasts.
Aurora power core
A solar-fed induction coil distributes energy through the hub. More cores raise the physical ceiling; the energy budget can still limit supply.
- Core capacity
- 150 EU
- Budget allowance
- $1 / EU
- Connection
- Manual link
- When disabled
- 0 EU supplied
Atlas data vault
A three-column buffer catches simulated production. A full vault stops production until you archive a batch or add capacity.
- Buffer capacity
- 2,000 sim sats
- Energy demand
- 10 EU
- Archive action
- Local record only
- No vault online
- Production stops
Every counter has a rule.
The orange packets show simulated production moving from active arrays through the hub to a vault. Cyan packets show energy delivered from cores to arrays. Packet speed and density reflect the circuit’s utilization.
Demo budget = trading volume × fee rate / 100
Compute allowance = compute budget / $2 per CU
Energy supply = min(enabled cores × 150 EU, energy budget / $1 per EU)
Utilization = min(100%, compute allowance / installed CU, supply / energy demand)
Simulated rate = enabled CU × utilization × 0.02 sim sats per simulated second
Compute allowance = compute budget / $2 per CU
Energy supply = min(enabled cores × 150 EU, energy budget / $1 per EU)
Utilization = min(100%, compute allowance / installed CU, supply / energy demand)
Simulated rate = enabled CU × utilization × 0.02 sim sats per simulated second
The $2/CU and $1/EU values are fixed game-balancing assumptions for a funding scenario. The budget is not a real quote and is not debited over time. Storage adds 10 EU of demand per enabled vault.
Find the constraint
- Energy limited: add a core, fund more energy or switch arrays to Eco.
- Compute budget limited: increase the compute allocation or disable unused arrays.
- Vault full: archive the batch or add an enabled vault.
- No link: connect power before production can begin.
Time and persistence
- Choose 1×, 5× or 20× simulated time. Rates use simulated seconds.
- Pause stops both production and movement. Reduced motion keeps camera changes instant and disables decorative motion.
- The simulation suspends while the station is offscreen or the tab is hidden.
- Reload restores counters and configuration, always paused. There are no offline earnings.
Lifetime output includes archived and currently stored simulated sats. Removing a vault keeps the recorded amount, but production remains blocked if available capacity is too small. A new module starts its own contribution counter at zero.
Test a what-if scenario.
A projection of this game’s model using the draft saved on this device. It is not an estimate of Bitcoin mining profitability.
Loading your local draft…
0–1,440 simulated minutes. The station does not run on this page.
Scenario result
Assumes no configuration changes. Storage capacity caps newly collected output. Archiving is a local action, never a payout.
The proposed real-world model.
Project trading fees would fund Bitcoin mining, and mined BTC would be distributed to eligible holders. That future system requires real providers, custody and settlement design, verifiable mining records, and an audited distribution mechanism.
| Approach | What would be funded | What must be verified |
|---|---|---|
| Hashrate rental | Contracted compute capacity pointed at a mining pool | Provider terms, delivered hashrate, pool fees and settlement |
| Hosted equipment | Hardware ownership plus hosting and electricity | Purchase cost, machine availability, maintenance, uptime and energy rates |
Network context
Real outcomes depend on Bitcoin network difficulty, total hashrate, BTC price, fees, uptime and pool luck. This prototype has no live network feed and does not repeat historical screenshot values as current data.
Connection is not authorization
Phantom Connect shares a Solana public address after your click. This demo never requests signatures or transactions, and connection is not server authentication. Native BTC rewards remain a future integration.
No contract address, listed token, provider partnership or payout history is claimed.
Before you press start.
Are simulated sats real Bitcoin?
No. They are local game counters with no monetary value. They cannot be claimed, transferred or withdrawn. The production coefficient is a toy rule, not a Bitcoin network calculation.
Why does Boost sometimes produce less than expected?
Boost raises both nominal compute and energy demand. If supply cannot keep up, the whole circuit is throttled. Eco can improve output per energy unit; compare modes using the module inspector.
What does “Archive batch” do?
It moves the vault’s local simulated counter into the archived counter, clearing room for more output. Lifetime output stays the same. No wallet, server or blockchain is involved.
What happens to my saved project?
Preview and save record a demo configuration and simulation snapshot only in this browser. Editing a saved project loads that snapshot paused. Reset clears the current draft and its counters; saved projects are preserved.
Can I use this as an earnings calculator?
No. There is no live hashrate, difficulty, provider price or real production behind these counters. Use the scenario calculator to understand the game’s constraints, not to evaluate an investment.