Skip to content

docs: fix CONTRIBUTE_COMPUTE.md calling a shipped feature 'the next step' #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wikithoughts merged 1 commit into from
Aug 30, 2026
Merged

docs: fix CONTRIBUTE_COMPUTE.md calling a shipped feature 'the next step' #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions docs/CONTRIBUTE_COMPUTE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,8 +97,11 @@ the limit key is the **socket peer**, which behind a tunnel is loopback — i.e.
**global** cap that is spoof-proof. Running more than a handful of operators? Put the coordinator
behind a reverse proxy that **sets and sanitizes** `X-Forwarded-For`, then set `PW_TRUST_XFF=1` for
per-client limits. Do **not** set `PW_TRUST_XFF` without such a proxy — clients could rotate the
header to bypass the limits. (Rate limits bound abuse *rate*; gating *who* may register at all is the
next step — per-operator enrollment tokens.)
header to bypass the limits. Rate limits bound abuse *rate*; gating *who* may register at all is a
separate, already-shipped mechanism (D37): with `PW_ENROLL` on, `/nodes/register` requires a valid
`X-Enroll-Token` minted by an operator via `/admin/enroll`, and `/users` (asker signup) stays open
but grants **zero** starter credit without one — so identity creation stays frictionless while free
credit stays gated.

## The geo-diversity moat

Expand Down
Loading