On June 12, 2026, Google Research published a blog post describing a Google-supported UC San Diego project to build a low-carbon computing platform from retired smartphones. The described approach extracts motherboards from retired phones, removes unnecessary consumer-device components such as batteries/screens/chassis, installs a general-purpose Linux software stack, and uses the phones as clustered/cloud/datacenter compute. The post says UCSD plans a 2,000-Pixel deployment, after early experiments with a 20-phone cluster, with the full system expected to launch in Fall 2026.

This market asks what becomes publicly documented by December 31, 2030, 11:59pm Pacific time. I will resolve based on public sources available by January 31, 2031, including Google/UCSD posts, academic papers, conference proceedings, preprints, GitHub repositories, credible journalism, official reports, or other public documentation.

For all answers, “the project” includes the Google/UCSD project described in the blog post and clear successor projects using substantially the same approach. For deployment-threshold answers, I will count deployments by any organization, not only Google or UCSD, provided the phones are retired or second-life consumer smartphones, or their extracted motherboards, repurposed as general-purpose clustered/cloud/datacenter/edge compute in roughly the manner described. Mere ordinary use of phones, phone farms for app testing/ad fraud, BOINC-style voluntary computing on still-in-use consumer phones, or emulated phone hardware does not count.

Deployment thresholds are cumulative and need not be a single cluster. Counts must be publicly documented with enough specificity to support the threshold. If sources provide a range, I will use the lower bound. If sources describe “phones,” “phone motherboards,” or “retired smartphones” interchangeably, each physical phone/motherboard counts as one unit.

Answers (Multiple answers may resolve YES)

1. The Google blog post is the last substantive public update
   Resolves YES if, by the resolution date, I find no substantive later public update about this project or a clear successor. Republished summaries, link posts, social-media shares, or articles that only restate the June 12, 2026 Google post do not count as substantive later updates. Any later public documentation of launch, cancellation, deployment, source code, paper, results, follow-on funding, or similar project progress makes this resolve NO.

2. A preprint or public technical paper is published
   Resolves YES if a paper, preprint, technical report, or equivalent citable research manuscript about this Google/UCSD retired-phone computing project, or a clear successor, is publicly posted by the deadline. Qualifying venues include arXiv, HAL, SSRN, TechRxiv, institutional repositories, Google/UCSD publication pages, or similar. The original blog post alone does not count. Prior “smartphone cluster” papers published before the June 12, 2026 blog post also do not count. This answer also resolves to true if a peer-reviewed paper is published.

3. A peer-reviewed paper is published
   Resolves YES if a paper about this project or a clear successor appears in a peer-reviewed journal, conference, or workshop proceedings by the deadline. A short paper, demo paper, systems paper, sustainability paper, or peer-reviewed workshop paper counts. A blog post, whitepaper, slide deck, or non-reviewed technical report does not count.

4. At least 1,000 phones are documented as deployed
   Resolves YES if public documentation shows at least 1,000 retired smartphones or smartphone motherboards deployed as compute using the described approach by the deadline. UCSD’s planned 2,000-phone cluster counts only if there is later public documentation that at least 1,000 were actually deployed, not merely planned.

5. At least 1 million phones are documented as deployed
   Resolves YES if public documentation shows at least 1,000,000 retired smartphones or smartphone motherboards cumulatively deployed as compute using the described approach by the deadline.

6. At least 1 billion phones are documented as deployed
   Resolves YES if public documentation shows at least 1,000,000,000 retired smartphones or smartphone motherboards cumulatively deployed as compute using the described approach by the deadline.

7. At least 100 iPhones are documented as deployed
   Resolves YES if public documentation by the deadline shows at least 100 retired Apple iPhones, or their extracted motherboards/SoC boards, cumulatively deployed as compute nodes using substantially the retired-phone computing approach described in this market, regardless of what OS they run after repurposing.

8. At least 100 non-Pixel Android phones are documented as deployed
   Resolves YES if public documentation by the deadline shows at least 100 retired Android phone that is not a Google Pixel, or its extracted motherboard/SoC board, deployed as a compute node using substantially the retired-phone computing approach described in this market. “Android phone” means a device originally sold running Android or an Android-derived OEM distribution, regardless of what OS they run after repurposing. Google Pixels do not count for this answer, because they are already the baseline device family in the original Google/UCSD project.

9. At least 100 HarmonyOS / Huawei phones are documented as deployed
   Resolves YES if public documentation by the deadline shows at least 100 retired Huawei/Honor phones originally sold with HarmonyOS, EMUI, or another Huawei-derived/HarmonyOS-era phone software stack, or its extracted motherboard/SoC board, deployed as a compute node using substantially the retired-phone computing approach described in this market. It counts regardless of what OS they run after repurposing.

10. At least 100 other smartphone platform phones are documented as deployed
    Resolves YES if public documentation by the deadline shows at least one retired smartphone, or its extracted motherboard/SoC board, from a platform not covered by the Pixel, non-Pixel Android, iPhone, or HarmonyOS/Huawei answers, deployed as a compute node using substantially the retired-phone computing approach described in this market. Examples could include Windows Phone, Firefox OS, Sailfish OS, Ubuntu Touch, Tizen, KaiOS only if the device is credibly smartphone-class, or another smartphone platform.Single-board computers, tablets, laptops, development boards, routers, and purpose-built embedded hardware do not count.