Review date: . This scaffold records the
evidence to verify before expanding the short review. It is a research checklist only,
not investment advice, legal advice, tax advice, or an income forecast.
SectorData
Operator fitBandwidth contributors
Demand signal to verifyData buyer demand, contributor rules, and privacy constraints
Review Lens
Grass should be reviewed through buyer demand, contributor rules, and data-policy risk
before discussing participation. A fuller profile should avoid treating bandwidth rewards
as durable until buyer categories, traffic rules, and consent expectations are documented.
Grass turns residential and institutional bandwidth into web scraping infrastructure for AI training and data indexing. The network's value proposition is clear — AI companies need fresh, diverse web data at scale — but the project operates in a regulatory gray area around data sourcing, consent, and network usage policies. Contributors should carefully review what types of traffic are allowed, how data is collected and sold, and whether their local ISP or jurisdiction imposes restrictions on bandwidth resale.
Confirm whether data buyers have repeat access needs that survive incentive changes.
Record contributor eligibility, allowed traffic, privacy constraints, and prohibited uses.
Keep bandwidth overages, taxes, policy changes, and local network restrictions outside the simple calculator.
Demand Questions
What customer categories need the data access and how repeatable is that demand?
Which policy, privacy, or data-source restrictions change contributor eligibility?
How should buyer quality be verified before treating rewards as sustainable marketplace demand?
Operator Assumptions
Bandwidth, device uptime, policy compliance, and household or business network limits need checks.
Any payout scenario should include eligibility rules, volatility, and liquidity haircuts.
Privacy review, taxes, bandwidth overages, and local legal requirements are outside the simple calculator.
Dated Source Snapshot Template
Use this table as a manual evidence log before publishing Grass buyer-demand or contributor assumptions.
Evidence gap
Source to check
Dated field to record
Data buyer demand
Official product, docs, or customer materials
Buyer category, data access need, and retention signal
Contributor rules
Official docs
Device eligibility, uptime expectation, and payout condition
Privacy and policy constraints
Docs and official policy pages
Allowed traffic type, user consent, and prohibited use
Source Checklist
Re-check these primary sources before publishing dated data-demand or contributor assumptions.