Community Intel

Polymarket 开发者/社区情报面板。来源只读：官方 Docs、GitHub、已保存的 X 观察摘要，以及明确标记的 Discord/TG 阻塞项。 本页不执行发帖、进群、交易、签名、授权或资金操作。

生成时间：2026-05-25 08:56:10

Priority Workstreams

Community / X Observations

• Builder leaderboard and volume endpoints now expose builderCode [official docs changelog / official-docs-high]
  The May 18, 2026 changelog says `GET /v1/builders/leaderboard` and `GET /v1/builders/volume` include `builderCode`. Priority: add builderCode-aware parsing and examples to local builder/API evidence.
  https://docs.polymarket.com/changelog
• CLOB V2 is the live production target and V1 is no longer compatible [official docs changelog / official-docs-high]
  The Apr 28, 2026 changelog confirms production runs at `https://clob.polymarket.com`, V1-signed orders are unsupported, and pre-cutover open orders did not migrate. Priority: keep all local examples and compatibility checks V2-only.
  https://docs.polymarket.com/changelog
• Builder attribution moved to a single builderCode field and pUSD is the new collateral [official migration guide / official-docs-high]
  The migration guide states V2 uses `@polymarket/clob-client-v2` and `py-clob-client-v2`, moves builder attribution into the order struct via `builderCode`, and replaces USDC.e with pUSD. Priority: build an official-docs-derived API Examples Kit focused on V2 auth, signing, and builder attribution.
  https://docs.polymarket.com/v2-migration
• Builder program still routes users toward profile creation, attribution, and gasless relayer usage [official builder docs / official-docs-high]
  Official builder docs still tell builders to create a builder profile at `polymarket.com/settings?tab=builder`, attach `builderCode` on orders, and use the relayer client for gasless operations. Priority: keep local builder submission package and profile site aligned with this flow, without creating keys or profiles automatically.
  https://docs.polymarket.com/builders/overview
• Verified builder tier still advertises leaderboard visibility, private Telegram, and weekly USDC rewards [official builder docs / official-docs-high]
  The tiers page shows Verified builders can get leaderboard visibility, a private Telegram channel, and weekly USDC rewards subject to approval, while upgrades route through `builder@polymarket.com`. Priority: preserve a truthful rewards/community monitor and avoid any fake-volume or rewards-farming behavior.
  https://docs.polymarket.com/developers/builders/builder-tiers
• Builders landing page still markets grants and captures website, email, X, and Telegram fields [official builders site / official-site-high]
  The public builders page still advertises `$1M+` in grants and exposes the current application field shape, including Website URL, Email, X Handle, and Telegram Handle. Priority: keep the local submission package ready, but do not submit or interact with the form without user confirmation.
  https://builders.polymarket.com/
• Official help center continues to deny any Polymarket token or airdrop [official help center / official-help-high]
  The Jan 11, 2026 help-center article says Polymarket does not have a token or announced airdrop and points users back to official web, X, and Discord channels. Priority: treat token, airdrop, quest, and rewards claims outside official sources as scam-risk until verified.
  https://help.polymarket.com/en/articles/13364250-does-polymarket-have-a-token
• Official @Polymarket profile still points to polymarket.com and Discord [official X profile verification / official-x-profile-medium]
  The public @Polymarket profile page exposes the official website link and Discord path, which remains a valid source-record for later link verification. Priority: keep using official X profile metadata to confirm outbound community links before trusting them.
  https://x.com/Polymarket/affiliates
• Official @PolymarketBuild profile remains the public builders-program source on X [official X profile verification / official-x-profile-medium]
  The public @PolymarketBuild profile describes itself as the official source for builder updates and points back to the builders path. Priority: use it as an official source record, but note that timeline-level extraction is limited without logged-in browser or connector access.
  https://x.com/PolymarketBuild/affiliates
• Recent official X developer messaging still emphasizes developer experience [public X status search / official-x-search-low-freshness]
  Public search surfaced a Feb 19, 2026 official @Polymarket post about building the best developer experience and welcoming `@GetDomeAPI`. This is useful as a soft signal for DevRel emphasis, but it is not fresh night-window evidence and should be treated as lower-confidence than docs.
  https://x.com/Polymarket/status/2024514315823509826
• Night-window X timeline coverage is still blocked by missing Chrome/connector navigation [public X search limitation / run-blocker-high]
  This run could verify official X profile identity and public indexed posts, but could not safely inspect the full logged-in timeline because direct Chrome navigation tools were not available in-session. Priority: keep the blocker explicit and continue using official docs/site changes as the highest-confidence overnight signal.
  https://x.com/PolymarketBuild

Official GitHub

Access Blockers

• X continuous search: TWITTER_TOKEN is not available locally; current run uses connector results and saved summaries only. Use X connector/browser or configure a token before automated X search.
• Discord developer community: Login and posting are account actions. Open official Discord read-only; ask user before posting, joining restricted channels, or submitting forms.
• Telegram community: Telegram bot/channel interactions can include unsafe crypto links. Read official @polymarket only; verify any outbound link through official X/website before use.
• Deployment: Live server changes require fresh process/port/service preflight. Keep local site/report work moving until deployment target is explicitly confirmed.