Real work.
Checked results.

What comes next.

Checking available work…

Checking chemistry campaign…

Finished chemistry inputs are not repeatedly rewarded. Exclusive leases prevent two Nodes from claiming the same assignment; unfinished work returns when a lease expires. When no eligible medicine task is available, mining continues with game layouts.

What a verified block means.

The server recomputes the assigned deterministic calculation and checks the submitted result before recording the result. Eligible calculations and original sound files can qualify after automatic full server checks. Production 3D assets still need their complete acceptance checks. Invalid and replayed results earn none. A successfully computed research result may still be a negative finding; computational correctness alone does not establish medical safety or efficacy.

Current medicine work compares rounded descriptors from public PubChem reference compounds. The next prepared campaign contains 36 one-time batches covering 7,864,320 unique cross-group comparisons. Cancer remains the first requested targeted area, awaiting a reviewed biological target and model.

These comparisons are reference analysis. They do not simulate cancer treatment, toxicity, all possible tests or new medicine discovery. Detailed private research stays in the owner lab.

Automatic results. Complete checks.

Checking the active reward acceptance rule…

Checking verified results…

Reviewed paired comparisons report whether the best candidate exceeds that model’s benchmark. Valid negative findings remain evidence. Public chemistry descriptor jobs have no medical acceptance criterion, so they are reported as completed analysis.

Sign in for your result reports and reuse choices ↗

Reuse does not issue Points. A separate successfully verified game-layout block earns its ordinary block reward; importing or reviewing that layout earns none.

From layouts to a test world.

Loading the executed Unreal build evidence…

The local importer checks source-block hashes, recomputes each layout, validates building dimensions and walking gaps, then creates a separate Unreal review map. Materials are checked, a real GPU render is captured and the scene must load successfully before it passes the local build gate.

This is an exterior prototype, with reused original PBR materials and trees. It is not the finished AAA game. Unreal runs in the local desktop development tools; the website game uses its browser renderer. Importing an already rewarded layout does not issue another reward.

A native simulator you can test locally.

Loading executed simulation checks…

The new local Windows prototype uses Unreal physics, a chase camera and flight controls. Its top and bottom openings and landing gear move independently. A classical approximation records externally collected working mass, intake drag, power and heat limits. In space, sparse particles limit thrust; internal recirculation alone does not accelerate the craft.

Private owner research is excluded. The hull collision and assumed power source need further review; this does not validate real propulsion. The local simulator has passed its implementation checks, with production and independent asset acceptance still pending. Public native game downloads are not enabled yet.

Use the right worker.

Compatible desktop Nodes can use native CPU and DirectX 12 GPU calculations. An RX 9070 XT has passed exact chemistry-result checks on both CPU and GPU. Blender GPU rendering and local AI need their installed tools and your opt-in. Browsers use their supported CPU or WebGPU backend.

More demanding assets and models can use more hardware. There is no promise of 99% utilisation on every device, and extra activity without a verified purpose earns no Points. Local generated assets and training outputs remain pending independent verification.

Photorealism is the destination.

Windows PC is the first native release target, with Linux, macOS, PlayStation, Xbox and Nintendo releases planned. The native Unreal game will receive reviewed updates as development continues. The browser game is playable today.

Release assets need verified PBR materials, intact UVs and textures, cinematic lighting review, and measured performance on their target device. The campus above is an exterior geometry prototype; it has not passed final photorealistic art review.

Console versions require approved platform access, authorized SDKs, suitable Unreal builds, hardware testing and store certification. No console download or release date is available yet.

Six designs to start your collection.

The mine’s car campaign starts with Auvryxis Aster S, Veyra R, Meridian GT and Orison, followed by Norzavique Summit and Forge. Car jobs alternate with Earth coastline tiles and continue through the existing sixteen vehicle families.

Orison and Forge use electric game powertrains; Aster S, Veyra R, Meridian GT and Summit use combustion engines. Electric motor, inverter, battery and regenerative-braking options sit alongside combustion tuning. Checked public materials calculations can inform an experimental brace study; new alloy or propulsion claims still need their appropriate evidence. These are original exterior prototypes with curved glazing, fitted lights, emblems and PBR materials. The game garage adds paint, liveries, wheels, body kits and local engine, turbo, transmission and chassis tuning. Complete interiors, rigging and final production art acceptance remain in development.

Develop until the game and simulator pass.

There is no fixed completion deadline. A verified layout enters development; it does not become a production asset automatically. Failed quality checks keep an asset in development for repair. The current native and browser games are playable prototypes.

• Provenance, licensing, geometry, collision, UVs and PBR materials
• Actual render and scene-load checks, physics stability and reviewed simulator accuracy
• Missions, save compatibility, multiplayer integrity and security
• Accessibility, controller support and measured performance on each target device
• Release testing, trusted signing and platform certification where required

These gates remain incomplete for the full game. Nodes cannot certify medical safety or a AAA release just by finishing a calculation.

AI science and game references

Twenty fixed public workload families are prepared: the original mathematics, mechanics, spacecraft, materials, safe dilution, software and game budget references, plus circuits, optics, ideal gas and radiation, aerodynamics, orbital speed, robotics, acoustics, ocean pressure, Earth heat flow, solar energy, synthetic ecology and statistics. There are 1,280 distinct finite input variants. Local AI proposes numeric answers; the server recomputes acceptance. These are finite reference checks, not a general autonomous discovery engine. Toxicity, target efficacy and full medicine safety remain subject to applicable reviewed scientific models.

The Windows app batches up to 32 distinct references, limited by your context and memory choices. The large-PC profile prepares 8,192 context tokens and up to 16 references per model call. Each candidate retains its own lease, model digest, inputs, constraints, answer and independent outcome. Shared inference tokens are counted once per batch. The original single-job protocol remains supported. Inference telemetry is not independently attested and cannot earn Points. When numerical reference rewards are enabled, a complete passing answer earns eligible credit after server recalculation; when work weights are enabled, sixteen such answers complete one ordinary reward block; this rewards the calculation, not a claim that an AI model executed. Game assets use a separate stored-file, UV, material, render and production acceptance process. Only your pinned owner account can open detailed network AI results in the private lab.

Temporary on your device. Stored in your account.

Connected desktop mining uploads new AI reports and selector snapshots privately, checks each part and the whole downloaded copy, then removes the managed temporary report. Assigned game assets use their cloud upload and acceptance workflow; private owner chemistry stays in the encrypted lab. Small receipts and working models stay available locally.

Reading your private generated files…

Cloud storage is evidence staging. Only accepted assets can be integrated into game releases. Installed models, tools, settings and existing personal files are preserved. Interrupted uploads keep their local copy and pause new generation if the queue fills.

Build the files. Verify the result.

Open my private asset review ↗ · Private chemistry vault ↗

Cloud-first mode uploads a complete assigned asset and reads back every stored part and complete file hash before releasing its newly managed local source copies. Existing files are preserved. Technical passes remain separate from game production acceptance.

The existing 8K basalt asset has now executed its Unreal 5.8.3 import, material and visible-render checks. The saved render evidence remains local; it still needs visual quality and displacement work before production acceptance.

Both approved game runtime packs and complete medicine assessments still require their missing evidence. Uploading source files alone does not place an unaccepted asset into the playable game.

New native 8K material masters and original asset recipes are being tested in Unreal. A complete ordinary asset earns the live annual reward after a separate trusted verifier checks stored files, UVs, material channels, engine import, render, memory, licensing and visual quality. Failed assets require repair. The whole Saucer keeps its separate 50-Point acceptance rule.

Live asset rewards are not activated yet. Local renders, individual textures and miners’ self-reports earn no Points. Medicine and reviewed science remain first.

Render. Check. Use.

The same mine can create finite original procedural sound files for steps, sports, impacts, shots, scoring and engines. Medicine jobs retain priority. Sound acceptance automatically checks exact WAV content, non-silence, bounded amplitude and the original recipe. No owner approval is needed for this fixed pipeline.

Reading the sound job queue…

Each unique accepted file contributes eligible work credit when sound rewards are enabled; under the weight policy, smaller sound results combine toward a full ordinary reward block. Duplicates and rejected files earn zero. These sounds are procedural synthesis, not a trained audio model or final cinematic sound design.

WORLD DEVELOPMENT TARGET

Nottingham. Build outwards.

The next large open-world region is Nottingham with fictionalised surrounding districts. The scale target is comparable to a major open-world game; an exact GTA 6 map area is not asserted. This is a development target, not an available finished map.

New supported asset jobs create exact-manifest staging plans for the Nottingham region. These suggest local preview positions and catalogue roles, expanding from a central tile. The geographic planner also supports metre-scale WGS84 positions from bounded, attributed OpenStreetMap data and fictional road/building labels. No Nottingham street dataset or photo survey has yet been imported into the released game. Vehicle catalogues, environment libraries and globe references retain separate roles.

The mine runs supported geometry, UV, material, visible-render and Windows-cook checks automatically. Technical evidence rankings show actual passes, failures and missing checks. A prepared automatic release evaluator requires authenticated, exact-asset evidence for geometry, collision/navigation, LOD/streaming, runtime performance, photo comparisons, visual defects and licence provenance. Full game builds additionally require menu/input, saves, missions, audio/accessibility, multiplayer reconnect, stability, updates and map-placement evidence. Missing or failed checks block experimental release. These are technical experiment criteria, not a guarantee of AAA quality.

Menu targets cover free roam, story missions, garages, races, sports, science, multiplayer and settings. The current playable prototype remains available while the native world develops. There is no automatic release date based on mining time alone.

Four-year target: 25 October 2030

Loading committed game production measurements…

Reading accepted game-production measurements…

This is the owner’s planning target from 24 October 2026, not a guaranteed AAA release. The adjusted workload estimate becomes available after the production scope and sustained accepted-game throughput are measured. More accepted parallel work can bring it forward; fewer resources or more required work can move it back. Device count alone cannot set the date. Art, gameplay, integration, rights and platform checks still determine readiness.