Cannot register on Bounty Marketplace — Privy OAuth fails with "User limit reached" (400/422)

[EslaM-X]

Bug

New users cannot log in / connect GitHub on the RoboPay Bounty Marketplace (https://robopay.fabric.foundation/bounties), so they cannot claim a bounty or submit a PR before the Aug 21 deadline.

Steps to reproduce

1. Open https://robopay.fabric.foundation/bounties
2. Pick a company (e.g. Unitree) -> select a robot (e.g. Go2) -> Tier 1
3. Click Apply / "Connect your GitHub" -> "Continue with GitHub"
4. Authorize on GitHub (the GitHub authorization itself completes fine)
5. On redirect, authentication fails and no profile is created

Console / network errors

• POST https://auth.privy.io/api/v1/oauth/authenticate -> 400 (Bad Request)
• index.js: Error authenticating session
• Also seen: 422
• The OAuth response reports: "User limit reached" (this maps to Privy max_accounts_reached — the Privy app is in development mode and has hit the dev-mode account limit, so new users cannot sign up)

Environment

• Chrome (latest), third-party cookies enabled, popups allowed, no ad-blockers
• Fresh attempt after clearing site data / single tab

Expected

GitHub OAuth should complete and create a BountyHub profile so the user can claim a bounty and submit their PR.

Impact

Without registration, contributors are ineligible for rewards even with a valid, merged PR. The bounty closes Aug 21, 2026 00:00 PT, and it is first-come-first-served (first merged PR wins), so this blocker needs to be fixed urgently.

Request

Please upgrade the marketplace Privy app to production mode (or raise the dev-mode account limit) so new users can register.

Thanks!

[EslaM-X]

Hi team 👋 — EslaM-X here.

I've submitted a complete Tier-1 Robot Action Profile for Unitree Go2 (quadruped, 12-DOF) with all required evidence and tests, but I'm blocked from registering on the Bounty Marketplace due to the Privy OAuth "User limit reached" bug reported in this issue.

✅ My Submission — PR #89

PR: #89
Target branch: unitree-go2-tier-1 (correct bounty branch)
Title: Add robot profile: unitree/go2/unitree.go2.mujoco-pybullet-sim.v1 (per wiki format)

What's implemented & verified (green CI on fork):

• 7 paid embodied skills: wave, sit, stand, bow, nod, turn_to_face, hold — all joint-space PD + gravity compensation on official MuJoCo mujoco_menagerie Go2
• 34 tests / 5 suites: control, payment_gate, result_semantics, link, sim2sim
• x402 payment gate: unpaid→402, forged→402, replay→409, no-settle-on-failure proven
• Sim-to-sim validation: MuJoCo ⇄ PyBullet ≤ 0.01 cm position / ≤ 0.1° orientation drift (identical kinematics by construction from same MJCF)
• Visual evidence: GIF (go2.gif) + 6 per-skill screenshots + full terminal logs (go2-ci-logs.txt)
• Reproducible: clean checkout + 5 commands < 30 min (Windows + ubuntu-latest)

🚫 The Blocker

I cannot complete the "Apply" step on the Bounty Marketplace (https://robopay.fabric.foundation/bounties/Unitree) because the Privy OAuth flow fails with "User limit reached" (400/422) — the dev-mode account limit has been hit. This makes me ineligible for rewards even with a valid, merged PR.

Marketplace URL I'm trying to access: https://robopay.fabric.foundation/bounties/Unitree → "Unitree Go2 — Tier 1" → Apply

⏰ Urgency

The bounty closes Aug 21, 2026 00:00 PT (≈ 9 days). This is first-come-first-served — the first merged PR wins. Every day this auth bug persists, contributors like me who have done the work cannot claim their rightful place in the queue.

🙏 Request

Please upgrade the Privy app to production mode (or raise the dev-mode account limit) so new users can register. This is a platform-side bug, not a user error.

/cc @shicaih @parasyte-x @S-Zopiclone @fabricfoundationdev

---

Built with 🇪🇬 Egypt — EslaM-X

[EslaM-X]

Request for explicit eligibility confirmation

Hi maintainers,

I want to formally document the impact of this Marketplace authentication blocker on my Unitree Go2 Tier-1 submission.

Submission

PR #89:
#89

The PR is already open and the implementation is ready for maintainer verification.

Platform-side blocker

I have attempted to complete the Marketplace Apply / GitHub connection flow, but the Privy authentication step fails with:

400/422 — User limit reached

The GitHub authorization itself completes, but the Marketplace profile cannot be created.

This prevents me from completing the Marketplace registration step even though the failure is outside the submitted code and outside my control.

Why I am documenting this before the deadline

The bounty is first-come-first-served and the first qualifying merged PR wins.

I therefore want to avoid any ambiguity where a platform-side authentication failure could later be interpreted as contributor-side failure to register.

Request

Could a maintainer please explicitly confirm one of the following:

1. PR Add robot profile: unitree/go2/unitree.go2.mujoco-pybullet-sim.v1 (Tier-1 simulator, obstacle navigation) #89 remains eligible for the Unitree Go2 Tier-1 bounty while Issue Cannot register on Bounty Marketplace — Privy OAuth fails with "User limit reached" (400/422) #88 is unresolved; or
2. An alternative official registration procedure is available; or
3. The Marketplace issue will be fixed before the bounty deadline so I can complete the normal Apply flow.

I am not requesting an exemption from any technical bounty requirement.

I am only requesting that a documented platform-side authentication failure does not invalidate an otherwise qualifying submission.

I am also requesting that this issue remain as the public record of the registration attempt and platform-side blocker.

Thank you.

[daluoboda]

@Junzhe https://robopay.fabric.foundation/bounties Please fix the issues. You can connect with GitHub/Google OAuth but registration fails, then it goes back to 'not logged in' (Privy shows 'user limit reached'). Is registering to claim the Marketplace mandatory? Thanks!

[alienvisitor8675-bit]

/claim #88

PR: #106

[EslaM-X]

Hi @daluoboda — to answer your question:

Is registering to claim the Marketplace mandatory?

The Marketplace Apply step is the official registration mechanism, but the Privy auth bug (Issue #88) makes it impossible for new users to complete. This is a platform-side blocker, not a contributor-side failure.

I documented this formally in my earlier comment and requested that the maintainer confirm my submission remains eligible while #88 is unresolved.

---

For the record — status of qualifying submissions:

Submission	What it contains	Privy fix?	Bounty-qualifying work?
PR #89 — Unitree Go2 Tier-1	9 paid skills, 34 tests, MuJoCo/PyBullet sim-to-sim, x402 payment gate, EIP-3009 on-chain settlement	No (platform bug)	Yes — full Tier-1 implementation
PR #106 — "Fix #88"	173 lines in 1 file, body: "Closes #88"	No (not a Privy fix)	No — does not implement any robot profile

PR #106 does not fix the Privy OAuth infrastructure. It appears to be a claim attempt without qualifying work.

---

My submission (PR #89) implements the full Unitree Go2 Tier-1 simulator profile per the bounty spec, with evidence and CI. The only blocker to Marketplace registration is the Privy dev-mode account limit — a platform issue outside my control.

I respectfully request that the maintainers:

1. Confirm PR Add robot profile: unitree/go2/unitree.go2.mujoco-pybullet-sim.v1 (Tier-1 simulator, obstacle navigation) #89 remains eligible for the Unitree Go2 Tier-1 bounty
2. Note that Issue Cannot register on Bounty Marketplace — Privy OAuth fails with "User limit reached" (400/422) #88 is the public record of the platform-side registration blocker
3. Ensure the first-come-first-served queue accounts for documented platform-side failures

[fabricfoundationdev]

Hi, the issue has been fixed. Thanks.