What your browser can contribute
The intended browser contribution model uses a bounded amount of available capacity with participation enabled while the application is running. Eligible work includes maintaining assigned public cache coverage and preparing public information packages. A package is a collection of public network information prepared for reuse.
Private browsing data is not the material contributed. Contribution can be disabled, and assigned crawling is a separate opt-in. Credits require a browser version that supports live network contribution and is connected to the network. A contribution setting alone does not establish that work is taking place.
Completed work is what the network credits
Declaring capacity, remaining online, or serving one ordinary cached response does not by itself issue BFT. Assignment and verification tie credits to eligible work and the required evidence of completion. That is how the design seeks to credit service that supports the network.
This is contribution using your device’s resources, not a promise of money. Connectivity, eligibility, completed work, and operating costs matter. Whether your contribution covers your own publishing needs depends on actual use and results.
Support the things you value
The network’s accounting also supports contributions by authors and other participants. Its purpose is to keep value moving between the people supplying useful work and information and those benefiting from it. It does not grant the payer truth, ranking authority, or guaranteed attention.
Read Understanding BFT for the relationship between credits and spending, Fees and credits for what each action costs and what the network credits each role, or Node Help for the responsibilities of operating dedicated software.