[ RESEARCH / 01 ]THE POTENTIAL OF EXISTING HARDWARE
Another world
of possible nodes.
Consoles, computers and mobile devices. Explore the size of the pool, what we know about its distribution and what it takes to turn it into a network.
Devices shipped ≠ active devices ≠ compatible devices ≠ NodeLift nodes.
NO CROSS-CATEGORY TOTALLoading the evidence…
01 / OBSERVATORY
One platform, all the evidence.
The source does not document a regional breakdown. We do not assign devices to countries or cities.
What do the readiness labels mean?
- External demonstration
- Another project reports running a model. This does not establish a NodeLift worker, integration or benchmark.
- Existing NodeLift path
- A specific implementation path exists. Its scope and physical qualification still need to match the intended task.
- Inventory pilot
- The platform can be inventoried in the pilot. Inventory is not proof of LLM execution.
- Research / unsupported
- No qualified NodeLift execution path is claimed. Raw specifications remain documentary references only.
02 / HYPOTHETICAL SCENARIO
What if a fraction participated?
Set explicit assumptions for one reference population. This plans a hypothetical device cohort; it does not count available or compatible NodeLift nodes.
Initial values are editable assumptions, not observed rates. The result does not demonstrate inference, pooled memory, speed or energy savings. Assumptions are not projected onto the map.
The source says “more than”: the scenario uses the published threshold as a numerical reference. The result is not a lower bound on today’s fleet.
REFERENCE HARDWARE / PLANNING ONLY
From a device count to a raw resource envelope.
Choose one sourced hardware profile. Applying it to a whole population is an explicit scenario assumption, not a claim that every device has that specification.
Profiles are filtered to the selected platform family.
Browse all reference hardware ↓The last three steps require workload-specific qualification. GPU peak figures, accelerator TOPS, power ratings and gaming-mode measurements cannot be substituted for an LLM benchmark. Unknown values remain unknown.
03 / REFERENCE HARDWARE
A wider hardware lens.
Phones, computers, accelerators and edge boards. Search the complete reference library, then inspect a profile to select its platform and resource assumptions.
Profiles describe exact configurations or power modes. Listing a device does not establish NodeLift compatibility; unknown specifications remain unknown.
Compare with your nodes in Hive · operator sign-in ↗
| Reference hardware | Type & architecture | Compute & memory | Power evidence | Sources & inspect |
|---|
No reference profiles match. Try a different model, vendor or hardware category.
04 / PLATFORM CATALOGUE
The pool, category by category.
| Platform | Reference population | Metric and date | Source geography | Hardware / energy evidence | NodeLift readiness | Open |
|---|
No platforms match these filters.
05 / PROVENANCE AND LIMITS
From sources to possibilities.
- Documented population
Cumulative sales, active base and ecosystem counts are different metrics, dated to their sources.
- Compatibility to demonstrate
Available hardware and an external project do not establish that NodeLift executes that workload.
- Participation and availability
Owner consent and actual availability must be observed on enrolled nodes.
Active is not concurrent. A monthly-active device count describes activity during a reporting window. It does not mean those devices are powered, available or willing to run NodeLift at the same moment. “Reported on” dates a vendor statement when its measurement cutoff is not supplied.
Open the operational Hive inventory ↗