Hubbry Logo
Berkeley Open Infrastructure for Network ComputingBerkeley Open Infrastructure for Network ComputingMain
Open search
Berkeley Open Infrastructure for Network Computing
Community hub
Berkeley Open Infrastructure for Network Computing
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Berkeley Open Infrastructure for Network Computing
Berkeley Open Infrastructure for Network Computing
Berkeley Open Infrastructure for Network Computing
View on Wikipedia
from Wikipedia
BOINC
DeveloperUniversity of California, Berkeley
Initial release10 April 2002; 23 years ago (2002-04-10)
Stable release
8.2.4 Windows
10 July 2025; 3 months ago (2025-07-10)

8.2.5 macOS
16 July 2025; 3 months ago (2025-07-16) 8.2.4 Linux
15 July 2025; 3 months ago (2025-07-15) 8.0.2 Android
30 May 2024; 17 months ago (2024-05-30)

Preview release
8.2.5 / 15 July 2025; 3 months ago (2025-07-15)
Repository
Written inC++ (client/server)
PHP (project CMS)
Java/Kotlin (Android client)
Operating systemWindows
macOS
Linux
Android
FreeBSD
Raspberry Pi OS
TypeGrid computing and volunteer computing
LicenseLGPL-3.0-or-later[1]
Project licensing varies
Websiteboinc.berkeley.edu
BOINC Manager Advanced View
BOINC Manager Advanced View

The Berkeley Open Infrastructure for Network Computing[2] (BOINC, pronounced /bɔɪŋk/ –rhymes with "oink"[3]) is an open-source middleware system for volunteer computing (a type of distributed computing).[4] Developed originally to support SETI@home,[5] it became the platform for many other applications in areas as diverse as medicine, molecular biology, mathematics, linguistics, climatology, environmental science, and astrophysics, among others.[6] The purpose of BOINC is to enable researchers to utilize processing resources of personal computers and other devices around the world.

BOINC development began with a group based at the Space Sciences Laboratory (SSL) at the University of California, Berkeley, and led by David P. Anderson, who also led SETI@home. As a high-performance volunteer computing platform, BOINC brings together 34,236 active participants employing 136,341 active computers (hosts) worldwide, processing daily on average 20.164 PetaFLOPS as of 16 November 2021[7] (it would be the 21st largest processing capability in the world compared with an individual supercomputer).[8] The National Science Foundation (NSF) funds BOINC through awards SCI/0221529,[9] SCI/0438443[10] and SCI/0721124.[11] Guinness World Records ranks BOINC as the largest computing grid in the world.[12]

BOINC code runs on various operating systems, including Microsoft Windows, macOS, Android,[13] Linux, and FreeBSD.[14] BOINC is free software released under the terms of the GNU Lesser General Public License (LGPL).

History

[edit]

BOINC was originally developed to manage the SETI@home project. David P. Anderson has said that he chose its name because he wanted something that was not "imposing", but rather "light, catchy, and maybe - like 'Unix' - a little risqué", so he "played around with various acronyms and settled on 'BOINC'".[15]

The original SETI client was a non-BOINC software exclusively for SETI@home. It was one of the first volunteer computing projects, and not designed with a high level of security. As a result, some participants in the project attempted to cheat the project to gain "credits", while others submitted entirely falsified work. BOINC was designed, in part, to combat these security breaches.[16]

The BOINC project started in February 2002, and its first version was released on April 10, 2002. The first BOINC-based project was Predictor@home, launched on June 9, 2004. In 2009, AQUA@home deployed multi-threaded CPU applications for the first time,[17] followed by the first OpenCL application in 2010.

As of 15 August 2022, there are 33 projects on the official list.[18] There are also, however, BOINC projects not included on the official list. Each year, an international BOINC Workshop is hosted to increase collaboration among project administrators. In 2021, the workshop was hosted virtually.[19]

While not affiliated with BOINC officially, there have been several independent projects that reward BOINC users for their participation, including Charity Engine (sweepstakes based on processing power with prizes funded by private entities who purchase computational time of CE users), Bitcoin Utopia (now defunct), and Gridcoin (a blockchain which mints coins based on processing power).

Design and structure

[edit]
Main article: BOINC client–server technology

BOINC is software that can exploit the unused CPU and GPU cycles on computer hardware to perform scientific computing. In 2008, BOINC's website announced that Nvidia had developed a language called CUDA that uses GPUs for scientific computing. With NVIDIA's assistance, several BOINC-based projects (e.g., MilkyWay@home. SETI@home) developed applications that run on NVIDIA GPUs using CUDA. BOINC added support for the ATI/AMD family of GPUs in October 2009. The GPU applications run from 2 to 10 times faster than the former CPU-only versions. GPU support (via OpenCL) was added for computers using macOS with AMD Radeon graphic cards, with the current BOINC client supporting OpenCL on Windows, Linux, and macOS. GPU support is also provided for Intel GPUs.[20]

BOINC consists of a server system and client software that communicate to process and distribute work units and return results.

Mobile application

[edit]

A BOINC app also exists for Android, allowing every person owning an Android device – smartphone, tablet and/or Kindle – to share their unused computing power. The user is allowed to select the research projects they want to support, if it is in the app's available project list.

By default, the application will allow computing only when the device is connected to a WiFi network, is being charged, and the battery has a charge of at least 90%.[21] Some of these settings can be changed to users needs. Not all BOINC projects are available[22] and some of the projects are not compatible with all versions of Android operating system or availability of work is intermittent. Currently available projects[22] are Asteroids@home, Einstein@Home, LHC@home, Moo! Wrapper, Rosetta@home, World Community Grid and Yoyo@home [ru]. As of September 2021, the most recent version of the mobile application can only be downloaded from the BOINC website or the F-Droid repository as the official Google Play store does not allow downloading and running executables not signed by the app developer and each BOINC project has their own executable files.

User interfaces

[edit]

BOINC can be controlled remotely by remote procedure calls (RPC), from the command line, and from a BOINC Manager. BOINC Manager currently has two "views": the Advanced View and the Simplified GUI. The Grid View was removed in the 6.6.x clients as it was redundant. The appearance (skin) of the Simplified GUI is user-customizable, in that users can create their own designs.

Account managers

[edit]

A BOINC Account Manager is an application that manages multiple BOINC project accounts across multiple computers (CPUs) and operating systems. Account managers were designed for people who are new to BOINC or have several computers participating in several projects. The account manager concept was conceived and developed jointly by GridRepublic and BOINC. Current and past account managers include:

  • BAM! (BOINC Account Manager) (The first publicly available Account Manager, released for public use on May 30, 2006)
  • GridRepublic (Follows the ideas of simplicity and neatness in account management)
  • Charity Engine (Non-profit account manager for hire, uses prize draws and continuous charity fundraising to motivate people to join the grid)
  • Science United (An account manager designed to make BOINC easier to use which automatically selects vetted BOINC projects for users based on desired research areas such as "medicine" or "physics")[23]
  • Dazzler (Open-source Account Manager, to ease institutional management resources)

Credit system

[edit]
Main article: BOINC Credit System
  • The BOINC Credit System is designed to avoid bad hardware and cheating by validating results before granting credit.
  • The credit management system helps to ensure that users are returning results which are both statistically and scientifically accurate.
  • Online volunteer computing is a complicated and variable mix of long-term users, retiring users and new users with different personal aspirations.

Projects

[edit]

BOINC is used by many groups and individuals. Some BOINC projects are based at universities and research labs while others are independent areas of research or interest.[24]

Active

[edit]
Active Projects that have a Wikipedia page
Project Name Publications Launched Status Operating System GPU App Sponsor Category Research Focus
climateprediction.net 152 papers[25] 2003-12-09 307,359 volunteers[26] Windows, Linux, ARM, macOS[27] No Oxford University Climate change Improve climate prediction models. Sub-project: Seasonal Attribution Project.
Einstein@Home 42 papers[28] 2005-02-19 1,041,796 volunteers[29] Windows, Linux, ARM, macOS, Android[30] GPU CPU University of Wisconsin–Milwaukee, Max Planck Institute Astrophysics Search for pulsars using radio signals and gravitational wave data
Gerasim@Home [ru] 9 papers[31] 2007-02-10 6,811 volunteers[32] Windows, Linux[33] No Southwest State University (Russia) [ru] Multiple applications Research in discrete mathematics and logic control systems
GoofyxGrid@Home 2016 No Independent Mathematics Mathematically implement the Infinite monkey theorem
GPUGRID.net 53 papers[34] 2007-12-05 46,874 volunteers[35] Windows, Linux, macOS[36] NVIDIA GPU only Barcelona Biomedical Research Park Molecular biology Perform full-atom molecular simulations of proteins on Nvidia GPUs for biomedical research
iThena [pl] 2 papers[37][38] 2019 507,079[39] + 180,789[40] volunteers Windows, Linux, ARM[41] No Cyber-Complex Foundation (Poland) [pl; uk; et] Internet Measurements and analyses of global Internet architecture structures
LHC@home 71 papers[42] 2004-01-09 178,623 volunteers[43] Windows, Linux, ARM, macOS, Android, FreeBSD[44] No CERN Physics Help construct and test the Large Hadron Collider and search for fundamental particles
MilkyWay@home 27 papers[45] 2007-07-07 250,447 volunteers[46] Windows, Linux, macOS[47] No Rensselaer Polytechnic Institute Astronomy Create a simulation of the Milky Way galaxy using data from the Sloan Digital Sky Survey
PrimeGrid 3 papers[48] 2005-06-12 353,261 volunteers[49] Windows, Linux, macOS[50] GPU CPU Independent Mathematics Search for primes such as Generalized Fermat primes, 321 primes, Sierpiński numbers, Cullen-Woodall primes, Proth prime, and Sophie Germain primes. Subprojects include Seventeen or Bust, Riesel Sieve, and AP27 Search.
RALPH@Home [fr] Rosetta@home 2006-02-15 5548 volunteers[51] Windows, Linux, ARM, macOS, Android[52] GPU CPU University of Washington Molecular biology Test project for Rosetta@home
Rosetta@home 234 papers[53] 2005-10-06 1,373,480 volunteers[54] Windows, Linux, ARM, macOS, Android[55] No University of Washington Molecular biology Protein structure prediction for disease research
Tn-grid [it] 8 papers[56] 2013-12-19 3,201 volunteers[57] Windows, Linux, macOS[58] No University of Trento Genetics Currently deploying gene@home work to expand gene networks
World Community Grid 77 papers[59] 2004-11-16 85,119 volunteers[60] Windows, Linux, ARM, macOS, Android[61] GPU CPU Krembil Research Institute Multiple applications Subprojects: Open Pandemics - COVID-19. Clean Energy Project, GO Drug Search for Leishmaniasis, Fight Against Malaria, Computing for Clean Water, Discovering Dengue Drugs - Together, OpenZika, Help Cure Muscular Dystrophy, Help Defeat Cancer, Help Conquer Cancer, Help Fight Childhood Cancer, Smash Childhood Cancer, Human Proteome Folding Project, Uncovering Genome Mysteries, FightAIDS@Home, Let's outsmart Ebola together, Mapping Cancer Markers, Help Stop TB.
Yoyo@home [ru] 9 papers[62] 2007-07-19 94,236 volunteers[63] Windows, Linux, macOS, Android, ARM, Solaris, Sony Playstation 3[64] No Independent Multiple applications Using the BOINC Wrapper with existing volunteer projects

Completed

[edit]
Completed Projects that have a Wikipedia page
Project Name Publications Launched Status Operating System GPU app Sponsor Category Research Focus
ABC@Home paper[65] 2006-11-21 No Mathematical Institute of Leiden University Mathematics Find triples of the ABC conjecture
AQUA@home 4 papers[66] 2008-12-10 GPU CPU D-Wave Systems Computer science Predict the performance of Quantum computers
Artificial Intelligence System No Intelligence Realm Inc Artificial intelligence Simulate the brain using Hodgkin–Huxley models via an artificial neural network
Big and Ugly Rendering Project (BURP) 2 papers[67] 2004-06-17 No Independent Rendering (computer graphics) Use BOINC infrastructure with Blender (software) to render animated videos
Collatz Conjecture project [de] paper[68] 2009-01-06[69] 67,719 volunteers[70] Windows, Linux, macOS[71] GPU CPU Independent Mathematics Study the unsolved Collatz conjecture[72]
Correlizer [ru] 5 papers[73] 2011[74] No Biology Examining genome organization
Cosmology@Home 5 papers[75] 2007-06-26 87,465 volunteers[76] Windows, Linux, macOS[77] No Institut d'Astrophysique de Paris Astronomy Develop simulations that best describe The Universe
Docking@Home 20 papers[78] 2006-09-11[79] No University of Delaware Molecular biology Use the CHARMM program to model protein-ligand docking. The goal was the development of pharmaceutical drugs.
EDGeS@Home [ru] 12 papers[80] 2009-10 No MTA SZTAKI Laboratory of Parallel and Distributed Systems Multiple applications Support of scientific applications developed by the EGEE and EDGeS community
eOn 6 papers[81] No University of Texas at Austin Chemistry Theoretical chemistry techniques to solve problems in condensed matter physics and materials science
Evolution@Home 6 papers[82] No Evolutionary Biology Improve understanding of evolutionary processes
FreeHAL 2006 No Independent Artificial intelligence Compute information for software to imitate human conversation
HashClash 11 papers[83] 2005-11-24 No Eindhoven University of Technology Cryptography Find collisions in the MD5 hash algorithm
Ibercivis 18 papers[84] 2008-06-22 No Zaragoza, CETA-CIEMAT, CSIC, Coimbra Multiple applications Research in physics, material science and biomedicines
Leiden Classical 2 papers[85] 2005-05-12 No Leiden University Chemistry Classical mechanics for students and scientists
Malaria Control Project 26 papers[86] 2006-12-19 No Swiss Tropical and Public Health Institute Model Diseases Stochastic modelling of clinical epidemiology and the natural history of Plasmodium falciparum malaria
MindModeling@Home 6 papers[87] 2007-07-07 24,574 volunteers[88] Windows, Linux, macOS[89] No University of Dayton Research Institute and Wright State University Cognitive science Making cognitive models of the human mind
uFluids@Home 3 papers[90] 2005-09-19 No Purdue University Physics, Aeronautics A computer simulation of two-phase flow behavior in microgravity and micro fluidics
OProject@Home paper[91] 2012-08-13 No Olin Library, Rollins College Mathematics Algorithm analysis. The library is open and available in the Code.google.com SVN repository.
orbit@home paper[92] 2008-04-03 No Planetary Science Institute Astronomy Monitor near-earth asteroids
Pirates@home [es] 2004-06-02 No 1 Vassar College

2 Spy Hill Research

Software testing Mission 1: Test BOINC software and help to develop Einstein@Home screensaver[93]

Mission 2: Develop forum software for Interactions in Understanding the Universe[94]

POEM@Home 5 papers[95] 2007-13-11 No University of Karlsruhe Molecular biology Model Protein folding using Anfinsen's dogma
Predictor@home 5 papers[96] 2004-05-04 No The Scripps Research Institute Molecular biology Test new methods of protein structure prediction and algorithms in the context of the Sixth Biannual CASP[97] experiment
proteins@home 4 papers[98] 2006-09-15 No École polytechnique Protein structure prediction Contribute to a better understanding of many diseases and pathologies and to progress in Medicine and Technology
QMC@Home 7 papers[99] 2006-03-03 No University of Münster Chemistry Study the structure and reactivity of molecules using quantum chemistry and Monte Carlo techniques
Quake-Catcher Network 13 papers[100] 2008-02-03 No Stanford University, then

University of Southern California

Seismology Use accelerometers connected to personal computers and devices to detect earthquakes and to educate about seismology
Riesel Sieve No Mathematics Prove that 509,203 is the smallest Riesel number by finding a prime of the form k × 2n − 1 for all odd k smaller than 509,203
SAT@home [ru] 8 papers[101] 2011-09 No Siberian Branch of the Russian Academy of Sciences Mathematics Solve discrete problems by reducing them to the problem of satisfiability of Boolean formulas
SETI@home 12 papers[102] 1999-05-17 1,808,938 volunteers[103] Windows, Linux, macOS, Android[104] GPU CPU University of California, Berkeley Astronomy Analyzing radio frequencies from space to search for extraterrestrial life. Sub project: Astropulse
SETI@home beta see above 2006-01-12 GPU CPU University of California, Berkeley Software testing Test project for SETI@home
SIMAP 5 papers[105] 2006-04-26 No University of Vienna Molecular biology Investigated protein similarities
SLinCA@Home 2010-09-14 No National Academy of Sciences of Ukraine Physics Research in physics and materials science
Spinhenge@home 3 papers[106] No Technion – Israel Institute of Technology genetic linkage Used genetic linkage analysis to find disease resistant genes
TANPAKU [ja] 2 papers[107] 2005-08-02[108] No Tokyo University of Science Molecular biology Protein structure prediction using the Brownian dynamics method
The Lattice Project 16 papers[109] 2004-06-30[110] No University of Maryland, College Park Life science Multiple applications
theSkyNet 3 papers[111] 2011-09-13 No International Centre for Radio Astronomy Research Astronomy Analysis of radio astronomy data from telescopes

See also

[edit]
Wikimedia Commons has media related to Berkeley Open Infrastructure for Network Computing.

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Berkeley Open Infrastructure for Network Computing

View on Grokipedia
from Grokipedia
The Berkeley Open Infrastructure for Network Computing (BOINC) is an open-source platform that enables by harnessing volunteered idle resources from personal computers and other devices worldwide to support scientific research projects. Developed at the , BOINC allows volunteers to contribute computing power to diverse fields such as disease research, climate modeling, and , running computational tasks invisibly in the background without interfering with normal device use. BOINC originated from the need to generalize beyond single-purpose applications like , which launched in 1999 and demonstrated the potential of public participation in science. In 2002, with funding from the , computer scientist David P. Anderson initiated the BOINC project at UC Berkeley to create a flexible, cross-platform framework for multiple research initiatives. The platform's server and client software were first released in 2004, supporting initial projects and evolving over more than two decades through open-source contributions, with the latest client version (8.2.4) incorporating features like Docker application support as of July 2025. Key features of BOINC include heterogeneous , which accommodates CPUs, GPUs, and other hardware; result validation through redundant to ensure accuracy; and user-friendly account managers like Science United for selecting and participating in projects. It supports approximately 30 active projects, enabling seamless job downloading, execution, and uploading of results via a client application available for Windows, macOS, , Android, and other platforms. Volunteers can join through direct installation or aggregated portals, fostering community-driven without dedicated hardware costs. As of November 2025, BOINC delivers an average of 18.569 petaFLOPS of computing power daily from 18,775 active volunteers operating 89,411 computers, making it one of the largest sources of public computational resources for and significantly outperforming equivalent infrastructure in cost-efficiency. Notable projects include for global health challenges, for gravitational wave detection, and for , collectively advancing research while engaging millions in over the platform's history.

Overview

Definition and Purpose

The Berkeley Open Infrastructure for Network Computing (BOINC) is an open-source middleware platform designed to coordinate large-scale efforts across personal devices worldwide. It serves as a non-intrusive software layer that enables volunteers to donate their idle resources—such as CPU, GPU, and storage from desktops, laptops, and mobile devices—to support scientific endeavors without requiring specialized hardware. The primary purpose of BOINC is to empower scientific by aggregating distributed computational power for computationally intensive tasks, including , simulations, and modeling. This model harnesses unused cycles from millions of participants to tackle complex problems in diverse fields, such as (e.g., searching for extraterrestrial signals), (e.g., protein folding for ), and climate science (e.g., predicting environmental changes). By running scientific jobs in the background during periods of device idleness, BOINC democratizes access to , allowing researchers to scale operations globally at minimal cost. At its core, BOINC operates on the principle of distributing discrete "work units"—small, independent computational tasks—to volunteers' devices, which process them locally and return results to central servers for aggregation and validation. This approach transforms a of consumer-grade hardware into a powerful, parallel processing resource, effectively providing researchers with petaFLOPS-level capacity comparable to leading supercomputers without the need for expensive data centers or infrastructure. For example, as of 2018, individual BOINC projects delivered around 2 petaFLOPS of sustained performance at an annual operational cost of approximately $100,000, far below equivalent commercial pricing.

Key Features and Benefits

BOINC's cross-platform compatibility enables widespread adoption by supporting major operating systems including Windows, macOS, , and Android, while integrating with both central processing units (CPUs) and graphics processing units (GPUs) such as coprocessors for efficient computation. This versatility allows volunteers to contribute from diverse devices without compatibility barriers, maximizing the platform's reach across personal computers and mobile hardware. A core feature is its multi-project support, which permits users to attach a single BOINC client to multiple scientific endeavors simultaneously, allocating configurable resource shares—such as percentages of or disk space—to each project as preferred. This flexibility ensures continuous utilization of resources even if one project experiences downtime, enhancing efficiency for participants. Resource management in BOINC is designed for seamless, non-intrusive operation, automatically detecting and harnessing CPU and GPU cycles while honoring user-defined preferences for power usage, , work schedules, disk space limits, and network bandwidth constraints. For instance, users can set a "duty cycle" to throttle intensive tasks during peak hours, balancing computational contributions with device performance and energy efficiency. The platform's open-source nature, distributed under the GNU Lesser General Public License (LGPL), fosters transparency, -driven improvements, and customization, allowing developers to modify and extend the software for specific needs. Volunteers benefit from BOINC by directly aiding cutting-edge scientific across disciplines, while earning verifiable credits that quantify their contributions and enable participation in leaderboards and recognition systems. For projects, BOINC delivers scalable, low-cost power—for example, circa 2015, a medium-scale BOINC project providing 100 teraFLOPS was estimated to cost around $200,000 annually, compared to millions for equivalent resources—by from donated hardware. On a global scale, as of November 2025, BOINC aggregates immense computational resources from approximately 18,800 active volunteers operating over 89,400 computers, achieving a 24-hour average of 18.6 petaFLOPS, with a significant portion derived from GPU acceleration. This distributed network rivals top supercomputers, democratizing access to for resource-limited researchers and amplifying collective impact on global challenges.

History

Origins and Development

The Berkeley Open Infrastructure for Network Computing (BOINC) originated in 2002 at the , Berkeley's Space Sciences Laboratory (SSL), where it was developed as a successor to the client software used by the project. Led by David P. Anderson, a researcher at SSL and director of , the initiative aimed to create a non-project-specific platform that could harness idle computing resources from volunteers worldwide. This effort built directly on the success of , which had demonstrated the potential of distributed but was constrained by its custom-built infrastructure. The primary motivation for BOINC was to address the limitations of project-specific software, which required each scientific initiative to develop and maintain its own client and server systems, leading to high costs, lack of , and for new projects. By designing a generalized, open-source framework, developers sought to enable multiple projects to share the same infrastructure, allowing participants to contribute to diverse scientific efforts such as astronomy, climate modeling, and biomolecular simulations without needing separate installations. This approach was envisioned to scale the model beyond SETI@home's focus on extraterrestrial , fostering broader adoption in scientific research. Initial development was supported by grants from the (NSF), secured starting in summer 2002, along with collaborations involving and early partners like Predictor@home, a project. These resources enabled the core team at SSL to prototype the system, emphasizing modularity to accommodate varying application needs. Early challenges centered on creating a secure and scalable architecture suitable for distributed environments with untrusted volunteer hosts, including mechanisms to detect and mitigate erroneous computations, handle server loads from potentially millions of clients, and support cross-platform compatibility while preventing fraud in resource allocation. The first public release, BOINC 3.0, occurred in 2003 and targeted desktop platforms, marking the transition from internal testing to broader availability.

Major Milestones and Evolution

In 2004, the (WCG) was launched on November 16 as a major BOINC-based initiative, funded and operated by to harness for humanitarian research in areas such as and . This integration provided BOINC with significant computational resources from 's infrastructure, enabling large-scale projects and marking an early expansion beyond academic origins. By 2009, the BOINC 6.x series introduced support for GPU computing, initially through NVIDIA CUDA integration in version 6.6.32, which allowed projects like to leverage graphics processors for accelerated workloads, significantly boosting performance for certain scientific applications. The period from 2008 to 2015 saw the debut of the BOINC Android app in 2013, extending to mobile devices and broadening accessibility for users on the go. Version 7.x, starting with 7.0 in 2012, incorporated CPU throttling mechanisms to enhance energy efficiency, reducing power consumption during idle or low-priority tasks while maintaining computational output. During this era, BOINC's ecosystem expanded to support over 100 projects cumulatively, spanning diverse fields like , , and modeling. From 2016 to 2020, BOINC advanced compatibility with processors, building on Android support to include broader low-power architectures suitable for embedded systems. Enhancements for virtual machines, such as improved integration, allowed projects to run isolated Linux-based applications on diverse host operating systems, facilitating cross-platform development. In response to the , BOINC-powered projects like OpenPandemics on WCG launched in 2020 to accelerate by simulating protein structures from and related viruses. Between 2021 and 2025, the 8.x series progressed with incremental releases focused on stability and modern hardware, culminating in version 8.2.4 on July 10, 2025, which added native support for Docker containerized applications to simplify deployment of complex scientific workloads. Ongoing maintenance via the project's repository ensured regular security patches and compatibility updates, including support for and the latest Android versions, without major architectural overhauls. Over its evolution, BOINC has shifted from a desktop-centric platform to one inclusive of mobile and IoT devices, enabling volunteer contributions from smartphones and low-energy systems to democratize access to resources. This progression, highlighted by the 2025 Docker integration, underscores BOINC's sustained relevance in as of November 2025.

Architecture and Design

Core Components

BOINC employs a client-server model in which centralized project servers distribute computational tasks, known as , to volunteer clients installed on participants' devices. Each consists of an application executable along with input data, which the client downloads, processes locally, and returns the results to the server via HTTP-based remote procedure calls (RPCs). This architecture enables scalable distribution of scientific computations across heterogeneous volunteer resources worldwide. The core server-side components manage task assignment, data handling, and result processing. The scheduler, implemented as a program within an web server, assigns work units to incoming client requests by querying a shared-memory cache for available tasks. The feeder daemon maintains this cache by periodically populating it with unsent work units from the database, optimizing database access and reducing load during high-traffic periods. The server, typically part of the web server infrastructure, facilitates the transfer of application files, input , and output results between clients and the project storage. The transitioner daemon monitors and updates the states of work units and results in the database, handling transitions such as marking computations as complete or initiating validation. These components collectively ensure efficient operation, with the scheduler and feeder focusing on distribution while the transitioner coordinates post-computation workflows. The lifecycle of a begins with its creation on the server, where project-specific software generates the unit along with associated input files and registers it in the database. The unit is then made available for distribution: a client requests work via the scheduler, downloads the application and data files from the data server, and executes the in a local process. Upon completion, the client uploads the output files and result metadata back to the server. Finally, the transitioner and subsequent components aggregate validated results for scientific , completing the cycle. This flow supports fault-tolerant computing, as unfinished or erroneous units can be reassigned to other clients. BOINC accommodates heterogeneous computing environments by providing platform-specific application versions and flexible wrappers that allow legacy or diverse applications—written in languages such as C or Python—to run uniformly across operating systems like Windows, Linux, and macOS. These wrappers interface with the BOINC client API to handle resource allocation, checkpointing, and file I/O, enabling support for both CPU and GPU tasks without requiring modifications to the core application code. Security in BOINC's core architecture relies on sandboxing mechanisms to isolate computations and prevent unauthorized access or malicious execution on volunteer machines. Clients run applications under unprivileged user accounts with strict limits on , memory, disk usage, and network access; exceeding these triggers task termination. Additional protections include for application files to verify integrity and optional wrappers for enhanced isolation. These features collectively mitigate risks from untrusted code while maintaining volunteer participation.

Credit and Validation System

BOINC ensures computational accuracy through a validation process that relies on redundant , where each —a discrete task requiring identical —is assigned to multiple volunteer clients for independent execution. The server-side then compares the output files from these replicas, performing a syntax check to confirm their presence and format before assessing equivalence, typically using checksums for exact matches or tolerance thresholds for floating-point results. This replication mitigates errors from hardware faults, software bugs, or malicious activity by requiring agreement among instances. Central to validation is the quorum system, which mandates a minimum number of consistent results—often three—to declare a valid, with additional replicas scheduled if initial outputs disagree until a strict is achieved or a maximum threshold is reached. The result, serving as the authoritative output for scientific analysis, is selected from this consensus, while dissenting results are discarded. For long-running tasks prone to interruptions, applications can employ trickle-up messages to report partial progress or to the server asynchronously, enabling early detection of issues and potential partial validation without awaiting full completion. Error rates are managed through adaptive replication, which reduces redundancy for reliable hosts, and punitive mechanisms that limit task assignments to flaky hardware exhibiting repeated failures. To motivate volunteer participation, BOINC's credit system awards units—termed cobblestones—proportional to validated computational effort, estimated via the hardware's benchmarked floating-point operations per second (FLOPS). Each host's peak FLOPS is determined through initial benchmarks like Whetstone for CPUs, with claimed credit calculated as the product of elapsed time and peak FLOPS, scaled to cobblestones where 200 cobblestones represent the daily output of a 1 GFLOPS processor (8.64×10138.64 \times 10^{13} operations). The precise is: Claimed Credit C=(T×Peak FLOPS)×20086400×109\text{Claimed Credit } C = \left( T \times \text{Peak FLOPS} \right) \times \frac{200}{86400 \times 10^9} where TT is elapsed time in seconds; however, granted credit is adjusted for validation success to prevent inflation: for two replicas, the lower claim is awarded, while for larger quorums, it averages the middle values excluding extremes. This ties rewards directly to verified contributions, ensuring fairness across diverse hardware. Incentives extend beyond raw credits through community features like project-specific leaderboards ranking users by total output, achievement badges for milestones such as consecutive computation days, and a cross-project identification system that aggregates credits across BOINC initiatives for a unified volunteer profile. These elements cultivate competition and recognition, sustaining long-term engagement without monetary value.

Software Components

Client and Server Software

The BOINC client software is available for download from the official website at boinc.berkeley.edu, supporting major operating systems including Windows, macOS, and Linux distributions. For Windows, users download platform-specific executables such as boinc_8.2.4_windows_x86_64.exe for Intel 64-bit systems (Vista through 11), which includes the core daemon boinc.exe that runs as a background process to manage task downloads, execution, and uploads without user intervention. Installation involves running the executable, which sets up the client in the default directory (typically C:\Program Files\BOINC) and prompts for initial configuration, including project selection; the daemon operates silently thereafter, utilizing idle resources. On macOS, the universal package boinc_8.2.5_macOSX_universal.zip supports both Intel and Apple Silicon architectures; users unzip the file, mount the DMG, and run the installer, with the core client functioning as a background service via launchd. For Linux, packages are provided for x64 and ARM64 via distribution repositories or scripts like boinc_8.2.4_x86_64-pc-linux-gnu.sh, installed by running the script as root (e.g., sh boinc_*.sh), placing binaries in /usr/local/bin and enabling the daemon through systemd for persistent background operation. Client configuration is primarily handled through the cc_config.xml file, located in the BOINC data directory (e.g., %APPDATA%\BOINC on Windows or ~/.boinc on /macOS), which allows advanced global customization beyond the graphical manager, such as network and options. For - or app-specific settings like CPU usage limits, users can use app_config.xml files with options such as <cpu_usage> (e.g., setting 0.5 for 50% utilization to balance performance and responsiveness); global CPU throttling is managed through the BOINC Manager or preferences. Network bandwidth can be limited using tags like <max_file_xfers> (default 8, for total simultaneous transfers) and <max_file_xfers_per_project> (default 2, per ), preventing excessive data usage on metered connections. Proxy settings are configured in a <proxy_info> section, specifying <http_server_name>, <http_server_port>, <http_user_name>, and <http_user_passwd> for HTTP proxies or SOCKS versions (e.g., 5), ensuring connectivity in restricted environments; changes require restarting the client or using the boinccmd --read_cc tool. The BOINC server software consists of open-source tools designed for project administrators to host custom distributed computing initiatives, built on a stack including Apache web server, PHP for dynamic content, and MySQL (or MariaDB) for database management. Setup begins with cloning the repository from GitHub (git clone https://github.com/BOINC/boinc.git), installing dependencies like apache2, php-mysql, libapache2-mod-php, and mysql-server on Ubuntu-based systems via apt-get, then configuring the database with a dedicated user (e.g., boincadm with password foobar99). Administrators use the make_project script to initialize a project (e.g., ./make_project --url_base http://example.com myproject), creating directories, databases, and initial files in ~/projects/myproject; this automates schema setup in MySQL and generates PHP scripts for user registration and workunit distribution. Additional tools like xadd for adding applications and update_versions for deploying binaries complete the stack, with the server running daemons (e.g., transitioner, feeder) via bin/start for ongoing operation. BOINC supports automatic updates for project applications and results reporting, but client updates require manual downloads from the official site, with notifications via project messages or the event log. The version history includes incremental releases addressing compatibility; for instance, version 8.2.4, released on July 10, 2025, introduced native support for Docker-based applications, enabling containerized workloads on volunteer hosts without altering the core client. Maintenance involves periodic checks for updates using the BOINC Manager's "Update" button for projects and manual reinstalls for the client to resolve deprecated features, such as older 32-bit support phased out after 7.4.22. Common troubleshooting for the client includes firewall blocks, which often prevent task downloads or uploads; users should allow boinc.exe (Windows) or the boinc daemon (Linux/macOS) through ports 80, 443, and 31416 in firewall rules, as well as disabling interfering antivirus scans on the BOINC directory. Driver incompatibilities, particularly for GPUs, arise from outdated or mismatched graphics drivers (e.g., /); verifying compatibility via project forums and updating to the latest certified drivers resolves detection issues, with the event log providing clues like "No usable GPUs found." Proxy misconfigurations trigger "can't access " errors, fixable by editing cc_config.xml or testing direct connections; restarting the client after changes applies fixes.

User Interfaces and Managers

The BOINC Manager serves as the primary graphical user interface (GUI) for end-users, providing a centralized control panel to monitor and manage the BOINC client software. It features a dashboard in both Simple and Advanced views, allowing users to track computational task progress, view accumulated credits from completed work, and receive project messages or notices about updates. Users can adjust settings such as , network usage, and temporary pauses (e.g., via the "Snooze" option, which halts computations for one hour), with the interface displaying real-time status through notification area icons on Windows or menu bar indicators on macOS and . Account managers are third-party web services that streamline user participation across multiple BOINC projects by handling account creation, attachment, and team affiliations in a unified manner. Notable examples include BOINC Account Manager (BAM!), GridRepublic (which offers a virtual currency called GridCoin), and Science United (which allows selection by science areas with anonymous pooled accounts). These tools present a curated list of available projects for users to select via checkboxes, automatically generating project-specific accounts linked to a single email and password for the manager service. They facilitate easier multi-project management and team joining without navigating individual project sites repeatedly. Web-based interfaces are integral to BOINC's user onboarding, primarily through individual project websites where volunteers create accounts using an email address and password before attaching to the software. This process involves visiting a project's homepage, completing the registration form to receive an account ID via email, and then using the BOINC Manager's "Attach Project" wizard to input the project's URL and credentials, enabling seamless volunteering and progress tracking online. Customization options enhance within the BOINC , including skins that allow modification of the Manager's visual appearance in Simple, Advanced, and wizard views to match personal preferences or themes. Notifications are configurable through the interface's message system and status balloons, alerting users to task completions or errors, while integration with desktop widgets is supported via third-party add-ons for quick glances at activity without opening the full Manager. Privacy controls in BOINC emphasize user discretion, with options to participate anonymously by selecting non-identifying usernames during account creation and limiting shared through project-specific preferences. Services like Science United further support anonymity by pooling users under shared accounts on projects, confining personal details such as email to the manager level and restricting or visibility in public statistics.

Mobile and Specialized Applications

BOINC extended its platform to mobile devices with the release of an official Android application in July 2013, designed to leverage idle time on smartphones and tablets running Android 4.1 or later. The app supports , , x86, and x86_64 architectures, enabling computation on a wide range of devices including tablets. Key features include battery-aware scheduling, which suspends tasks when battery levels drop below user-defined thresholds to prevent excessive drain, and offline computation queuing, allowing downloaded work units to process without constant connectivity. These adaptations address the resource limitations of mobile hardware while maximizing volunteer contributions during charging periods or availability. In contrast, BOINC lacks a native application due to Apple's strict guidelines, which prohibit apps from downloading and executing arbitrary code—a core requirement for BOINC's dynamic task handling. Developers have explored alternatives, but no official solution exists; users may access BOINC projects via web interfaces or unofficial jailbreak methods, though the latter is not recommended due to risks and voids. For specialized environments, BOINC introduced Docker container support in client version 8.2.4, released on July 10, 2025, enabling volunteers to run containerized science applications on Windows, macOS, and hosts in a manner akin to workflows. This wrapper facilitates portable, isolated tasks without modifying host systems, broadening participation to server-grade or virtualized setups. Additionally, BOINC supports deployment on low-power IoT devices like through its client, which compiles and runs on ARM-based single-board computers, allowing integration into scenarios for distributed tasks. Mobile and specialized integrations face inherent challenges, particularly power constraints that limit computation to brief sessions on battery-powered devices, often resulting in shorter run times compared to desktops. over cellular networks adds further complexity, as intermittent connectivity can delay task uploads or downloads, requiring robust queuing mechanisms to maintain progress. Adoption of mobile BOINC has grown steadily since the Android app's launch, with volunteers contributing device cycles to scientific efforts, including climate modeling simulations that benefit from aggregated mobile processing power. This expansion has enabled broader participation in resource-intensive projects, though uptake remains tempered by device limitations.

Projects

Active Projects

As of 2025, the BOINC ecosystem hosts approximately 30 active projects spanning diverse scientific fields, including , physics, earth sciences, , and astronomy, each leveraging resources to advance goals. These projects distribute computational tasks as discrete work units, allowing volunteers worldwide to contribute idle processing power from desktops, laptops, and even mobile devices. Participation is facilitated through the BOINC client software, where users attach to a project by entering its URL in the manager interface, selecting preferred resource shares, and running tasks in the background without interrupting normal computer use. In , focuses on predicting protein structures and designing novel proteins to support and development, with ongoing applications in modeling variants for treatments like the SKYCovione vaccine. Work units consist of simulations for and docking, which often utilize GPU acceleration for efficiency in exploring conformational spaces. The project engages over 1.3 million registered users, processing over 8,000 jobs daily as of November 2025 to contribute to biomedical breakthroughs. World Community Grid addresses multiple humanitarian challenges, particularly for diseases like through the OpenPandemics initiative and climate-related efforts such as improving rainfall predictions for in vulnerable regions. Its work units involve large-scale molecular docking and simulations run on volunteer devices during periods, enabling rapid screening of potential therapies and environmental models. With contributions from around 818,000 volunteers, the project has expanded in 2024-2025 to include AI-assisted mapping of cancer markers from patient data. In physics, searches for and signals using data from observatories like and , aiming to detect weak astrophysical emissions from neutron stars. Work units process radio, gamma-ray, and interferometer datasets through signal correlation algorithms, compatible with CPU and GPU hardware across Windows, Linux, and Mac platforms. The project draws from over 500,000 volunteers, sustaining continuous analysis of vast astronomical archives. Climateprediction.net models long-term climate patterns, including temperature, precipitation, and probabilities, to inform resilience and . Volunteers execute work units as full climate simulations using the UK Met Office's model variants, which run for days on standard home computers to generate ensemble data for global comparisons. Other projects like LHC@home continue to support at by simulating accelerator experiments, while mathematics-focused efforts such as PrimeGrid hunt for large primes using probabilistic tests on volunteer hardware. Collectively, these active projects maintain a vibrant volunteer base exceeding 18,000 daily active participants across the platform.

Completed and Archived Projects

Completed and archived projects in the Berkeley Open Infrastructure for Network Computing (BOINC) refer to those that have ceased active operations after fulfilling their primary objectives, exhausting , or transitioning to alternative computational resources. These projects typically conclude when scientific goals are met, such as data collection targets, or when maintenance becomes unsustainable due to outdated infrastructure. Unlike ongoing efforts, archived projects no longer distribute new work units to volunteers but preserve their outputs for further research and analysis. One prominent example is Predictor@home, launched in June 2004 as the first public BOINC-based project focused on using volunteer resources to simulate with the CHARMM software. It operated until approximately 2007, contributing to advancements in understanding relevant to the CASP6 competition. The project ended primarily due to shifts in research priorities and the need for more specialized computing environments beyond volunteer contributions. Another notable case is SIMAP (Similarity Matrix of Proteins), which ran from 2005 to the end of 2014 and utilized BOINC to compute all-against-all protein sequence similarities, building a comprehensive database covering major public protein repositories. The project achieved its goal of generating a pre-computed similarity matrix but terminated BOINC involvement to adopt new algorithms on dedicated server infrastructure, citing the limitations of for updated scoring methods. Results from SIMAP remain accessible via its archived database, supporting ongoing bioinformatics research. LHC@home, initiated in 2004 to support CERN's simulations for the , saw several phases conclude in the 2010s, including early applications like SixTrack for beam dynamics modeling. Specific phases ended as simulations integrated into professional or as hardware demands outpaced volunteer capabilities, though the project continues in evolved forms. Outputs from completed phases, such as simulation datasets, are preserved in CERN's repositories and cited in high-energy physics publications. SETI@home classic, a flagship project analyzing data for extraterrestrial signals from 1999 to 2020 (with BOINC integration from 2004), exemplifies a long-running effort that achieved extensive data collection over 21 years. It ceased on March 31, 2020, to prioritize data analysis and update its aging software infrastructure, which had become challenging to maintain. The amassed dataset is archived at UC Berkeley for scientific review, with key findings published in literature. Common reasons for project termination include the fulfillment of core scientific aims, such as sufficient accumulation, alongside practical challenges like funding constraints or the migration to institutional for more complex tasks. Low volunteer participation in niche areas can also contribute, prompting teams to consolidate resources. Archival access to completed projects' results is ensured through public databases, peer-reviewed publications, and project websites, allowing researchers to build on volunteer-generated outputs without ongoing . For instance, volunteers' account and credits are often migrated or preserved for historical records, facilitating transitions to successor initiatives. Lessons from these completions have informed BOINC's evolution, particularly in enhancing algorithms to better support variable volunteer availability and in developing tools for smoother project handovers to systems. These experiences underscored the platform's flexibility, leading to improvements in server software for handling diverse workloads and integrating with grid infrastructures.

Impact and Community

Usage Statistics and Growth

BOINC experienced rapid initial growth following its public release in 2004, when it transitioned users and reached approximately 300,000 volunteers, building on the project's earlier peak of over 1 million participants. By , BOINC-based projects collectively had 80,721 participants across 188 countries, supplying about 106 teraFLOPS of computing power. The platform peaked around 2007 with over 700,000 active computers, reflecting widespread adoption among science enthusiasts. Subsequent years saw a gradual decline in participation, dropping to around 60,000 active computers by 2022, attributed to factors such as limited efforts, complexities, and concerns over energy costs and . As of 2025, BOINC maintains approximately 18,430 active volunteers and 89,177 computers, contributing a 24-hour average of 20.759 petaFLOPS, with daily changes showing modest volunteer gains but host losses. This stabilization follows a post-2010 downturn influenced by the rise of alternatives, offset by enhancements like mobile app support and Docker integration for easier deployment. In terms of computational scale, BOINC's peak performance reached about 93 petaFLOPS in 2018, supported by roughly 4 million CPU cores and 560,000 GPUs across devices. The current daily average of around 21 petaFLOPS underscores sustained but reduced capacity compared to its height, with total historical contributions enabling significant scientific workloads, though exact cumulative FLOPS figures are not centrally aggregated. User demographics remain dominated by participants from the and , with top contributors often from these regions based on multi-project rankings. Device usage is heavily weighted toward desktops and laptops, comprising the majority of active hosts, while mobile participation via Android apps constitutes a smaller share, with surveys indicating low adoption rates for smartphones and tablets. Growth was bolstered by strategic partnerships, notably IBM's launch of World Community Grid in 2004, which leveraged BOINC to mobilize volunteer resources for humanitarian research and attracted corporate and individual participants. Improvements in ease of use, such as the intuitive BOINC Manager interface and cross-platform support, have also helped retain dedicated users amid broader trends toward accessible distributed computing.

Scientific Contributions and Challenges

BOINC has facilitated significant scientific discoveries across multiple disciplines through its distributed computing framework. In , the project has identified numerous pulsars, including the gamma-ray millisecond pulsar PSR J2039+5617 in 2020, by analyzing data from radio telescopes and detectors to detect continuous from spinning stars. In , has advanced , enabling the design of novel proteins for therapeutic applications, such as miniprotein inhibitors targeting the to block viral entry into human cells. Additionally, climateprediction.net and related projects like weather@home have produced high-resolution models that attribute events to human-induced , such as linking the 2000 floods to anthropogenic warming, thereby informing adaptation policies. These contributions have led to substantial academic and practical impacts. BOINC projects have resulted in over 1,000 peer-reviewed publications, with dozens appearing annually in high-impact journals like and , demonstrating the platform's role in enabling large-scale simulations unattainable on traditional supercomputers. Real-world applications include the identification of COVID-19 drug candidates through and SiDock@home, where volunteer computing screened potential inhibitors and repurposed drugs like against in 2020-2021 efforts. Despite these successes, BOINC faces challenges inherent to volunteer resources. Volunteer attrition is common due to the costs of running computations on personal devices and concerns over transmission to servers, leading to fluctuating participation and resource unreliability. Validation overhead, where results from multiple volunteers are cross-checked to ensure accuracy amid heterogeneous hardware and potential malicious submissions, reduces overall efficiency by requiring redundant computations. Furthermore, competition from scalable services and AI-driven platforms has diminished volunteer computing's appeal for some areas, as centralized resources offer more predictable without volunteer . Criticisms of BOINC often center on its energy consumption, with debates highlighting the environmental footprint of distributed computing on idle devices compared to optimized data centers. Improvements have addressed some issues, such as enhanced privacy modes that allow anonymous participation and limit data sharing, alongside optimizations for low-power devices to mitigate energy use. Looking ahead, BOINC's potential integration with edge computing could leverage mobile and IoT devices for real-time, localized simulations, expanding its scope beyond traditional desktops. The BOINC community plays a vital role in sustaining and evolving the platform through active forums where volunteers discuss issues and propose features, driving updates like improved scheduling algorithms based on user feedback. Teams, ranked by total credits earned—such as top performers like "Team China" or "Gridcoin"—foster competition and collaboration, with over 100,000 registered teams contributing to project momentum and scientific progress.

References

  1. https://boinc.berkeley.edu/
  2. https://boinc.berkeley.edu/boinc_papers/crossroads.pdf
  3. https://boinc.berkeley.edu/computing.php
  4. https://boinc.berkeley.edu/boinc_a_platform_for_volunteer_computing.pdf
  5. https://boinc.berkeley.edu/grid_paper_04.pdf
  6. https://boinc.berkeley.edu/download.php
  7. https://boinc.berkeley.edu/develop.php
  8. https://queue.acm.org/detail.cfm?id=1080872
  9. https://boinc.berkeley.edu/anderson/resume.html
  10. https://www2.cs.uh.edu/~jaspal/cosc7397/06papers/boinc.pdf
  11. https://www.worldcommunitygrid.org/about_us/article.s?articleId=603
  12. https://www.ibm.com/history/world-community-grid
  13. https://boinc.berkeley.edu/forum_thread.php?id=4146
  14. https://boinc.berkeley.edu/forum_thread.php?id=8519
  15. https://github.com/BOINC/boinc/wiki/Client-release-notes
  16. https://boincsynergy.ca/wiki/BOINC_projects/
  17. https://github.com/BOINC/boinc/wiki/VersionHistory
  18. https://github.com/BOINC/boinc/wiki/VirtualBox
  19. https://www.worldcommunitygrid.org/research/opn1/overview.do
  20. https://boinc.berkeley.edu/forum_thread.php?id=15544
  21. https://github.com/BOINC/boinc/releases
  22. https://arxiv.org/pdf/1903.01699
  23. https://github.com/BOINC/boinc/wiki/Software-and-data-architecture
  24. https://www.spy-hill.net/help/boinc/Create_Project.html
  25. https://boinc.berkeley.edu/boinc_papers/api/text.html
  26. https://github.com/BOINC/boinc/wiki/Validators
  27. https://github.com/BOINC/boinc/wiki/TrickleImpl
  28. https://github.com/BOINC/boinc/wiki/CreditNew
  29. https://boinc.berkeley.edu/boinc_papers/credit/text.php
  30. https://boinc.berkeley.edu/download_all.php
  31. https://github.com/BOINC/boinc/wiki/Client-configuration
  32. https://github.com/BOINC/boinc/wiki/Create-a-BOINC-server-%28cookbook%29
  33. https://boinc.berkeley.edu/old_news.php
  34. https://boinc.berkeley.edu/forum_thread.php?id=13444
  35. https://boinc.berkeley.edu/forum_thread.php?id=8571
  36. https://github.com/BOINC/boinc/wiki/BOINC-Manager
  37. https://github.com/BOINC/boinc/wiki/Account_managers
  38. https://boinc.berkeley.edu/intro.php
  39. https://github.com/BOINC/boinc/wiki/Choosing-and-joining-projects
  40. https://github.com/BOINC/boinc/wiki/Creating-a-skin-for-the-BOINC-Manager
  41. https://boinc.berkeley.edu/addons.php
  42. https://boinc.berkeley.edu/info.php
  43. https://news.berkeley.edu/2013/07/22/new-app-puts-idle-smartphones-to-work-for-science/
  44. https://github.com/BOINC/boinc/wiki/AndroidBuildApp
  45. https://boinc.berkeley.edu/download_all.php?platform=android
  46. https://boinc.berkeley.edu/forum_thread.php?id=15068
  47. https://apple.stackexchange.com/questions/294820/is-it-allowed-for-an-ios-app-to-run-volunteer-computing-projects
  48. https://boinc.berkeley.edu/forum_thread.php?id=11639
  49. https://pimylifeup.com/raspberry-pi-boinc/
  50. https://www.degruyterbrill.com/document/doi/10.1515/eng-2018-0012/html?lang=en
  51. https://github.com/BOINC/boinc/issues/4873
  52. https://climateprediction.net/volunteer-your-computer
  53. https://www.hajim.rochester.edu/ece/sites/tapparello/papers/Tapparello_BookChapter2015.pdf
  54. https://boinc.berkeley.edu/projects.php
  55. https://boinc.bakerlab.org/rosetta/
  56. https://boinc.bakerlab.org/rosetta/rah/rah_about.php
  57. https://www.worldcommunitygrid.org/
  58. https://einsteinathome.org/
  59. https://climateprediction.net/
  60. https://continuum-hypothesis.com/boinc_history.php
  61. https://academic.oup.com/nar/article/42/D1/D279/1069408
  62. https://ceur-ws.org/Vol-1973/paper02.pdf
  63. https://setiathome.berkeley.edu/forum_thread.php?id=85996
  64. https://www.seti.org/news/seti-at-home-going-into-hibernation/
  65. https://boinc.berkeley.edu/pubs.php
  66. https://www.continuum-hypothesis.com/boinc_history.php
  67. https://boinc.berkeley.edu/forum_thread.php?id=5031
  68. https://boinc.berkeley.edu/chart_list.php
  69. https://thesciencecommons.org/BOINC/Census/2022/
  70. https://www.science.org/doi/10.1126/science.abd9909
  71. https://www.nature.com/articles/nature09762
  72. https://arxiv.org/abs/1903.01699
  73. https://www.researchgate.net/publication/260111450_Volunteer_computing_Requirements_challenges_and_solutions
  74. https://indico.cern.ch/event/1379525/contributions/5979694/attachments/2867842/5020151/BOINC-toPublish.pdf
  75. https://boinc.berkeley.edu/forum_index.php
Add your contribution
Related Hubs
User Avatar
No comments yet.