Draft-only external engagement
Daily path into the Polymarket developer orbit.
This page turns official GitHub issues, docs signals, and local product proof into concrete public engagement candidates.
It does not post, comment, submit forms, or push code without user confirmation.
Builder Actions
-
P1 Publish stable Builder Profile Site URL
Needs user-confirmed hosting target. Evidence: site/index.html, site/portfolio/index.html, site/evidence/index.html
-
P1 Push sanitized public GitHub repository
Needs user-confirmed GitHub account/repo target. Evidence: local commit plus docs/public-github-package.md
-
P1 Submit official Builders Program form
Needs user confirmation for Website URL, GitHub URL, contact fields, and Builder API key entry. Evidence: docs/builder-submission-package.md
-
P2 Ship next local product from 18-product portfolio
External publication is blocked until public GitHub/site target exists. Evidence: data/product-portfolio.json
GitHub Candidates
-
Polymarket/clob-client-v2 #69: All signature types rejected for new accounts: "maker address not allowed" / "signer address has to be the address of the API KEY"
score 5 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/clob-client-v2 #66: createApiKey() / create_or_derive_api_key() doesn't EIP-1271-wrap L1 auth for POLY_1271 deposit wallets — orders rejected with signer != api_key
score 3 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/polymarket-cli #71: BUG in Gamma API `/events`'s closed param which default to `true` while doc says `false` (propagates to CLI)
score 3 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/clob-client-v2 #64: BUG - V2 - Create ApiKey() doesn't EIP-1271-wrap L1 auth for POLY_1271 deposit wallets — orders always rejected with signer != api_key
score 3 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/clob-client-v2 #65: createApiKey() / create_or_derive_api_key() doesn't EIP-1271-wrap L1 auth for POLY_1271 deposit wallets — orders rejected with signer != api_key
score 3 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/clob-client-v2 #67: POLY_1271 deposit wallet orders rejected: "signer address has to be the address of the API KEY" — frontend reproduces too
score 3 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/py-clob-client #336: order_version_mismatch on every order placement (SIGNATURE_TYPE=1, v0.34.6) starting ~Apr 27
score 3 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/py-clob-client #331: polymarket clob api error
score 3 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/clob-client #344: createAndPostOrder returns 'balance: 0' on most markets despite valid balance (sigType=2, proxy wallet)
score 3 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/clob-client-v2 #73: POLY_1271 deposit wallet order rejected: "the order signer address has to be the address of the API KEY"
score 2 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/py-builder-relayer-client #21: WALLET-CREATE fails with RELAYER_API_KEY when from != RELAYER_API_KEY_ADDRESS
score 2 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/clob-client-v2 #63: How should a client distinguish legacy Gnosis Safe (sig_type=2) vs new V2 deposit wallet (sig_type=3) users?
score 2 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/py-clob-client #344: [BUG] py_clob_client (v1) cannot trade on new Polymarket Magic Wallet accounts (sigtype=3 not supported)
score 2 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/py-clob-client #340: order_version_mismatch on all sig_types with 0.34.6
score 2 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
-
Polymarket/py-clob-client #341: gamma-api: ?negRiskMarketID=<id>&limit=N saturates at limit, returns unrelated markets
score 2 | Review locally, reproduce with read-only or dry-run steps, then ask user before commenting, opening an issue, or submitting a PR.
Portfolio launch draft
Building a Polymarket ecosystem portfolio: 18 products across Builder proof, market intel, API examples, SDK compatibility, and safety tooling. Local proof is live for: Builder Profile Site, Builder Evidence Trail, Market Intelligence Dashboard, Community Intel Dashboard, Rewards Radar, Builder Leaderboard Tracker. @Polymarket @PolymarketBuild
Daily intel draft
Today s Polymarket builder priorities from official docs/GitHub/community signals: Community Support Desk, API Examples Kit, Risk & Compliance Monitor, Market Intelligence Dashboard. Turning these into read-only examples, issue candidates, and public proof before any trading integration. @PolymarketBuild
Safety positioning draft
Polymarket Developer Tracker is built around official links, read-only dashboards, dry-run examples, and no fake volume. Goal: useful builder tooling that can be reviewed publicly. @Polymarket @PolymarketBuild