聊天记录
共 12 条，显示第 1-12 条
you're hitting the 100/day Unverified relayer quota. Reset in ~30 hours (daily reset).Higher quota: Email builder@polymarket.com for Verified (3,000/day) or Partner (unlimited) tier.Use your own gas: No for sig type 3 — it's gasless relayer only. Create an EOA wallet (sig type 0) to use your own gas with the CTF contract directly.
you're hitting the 100/day Unverified relayer quota. Reset in ~30 hours (daily reset).Higher quota: Email builder@polymarket.com for Verified (3,000/day) or Partner (unlimited) tier.Use your own gas: No for sig type 3 — it's gasless relayer only. Create an EOA wallet (sig type 0) to use your own gas with the CTF contract directly.
Yea
Yea
Yes — the API key is bound to the EOA.Use this mapping:MetaMask private key → signerMetaMask wallet address → EOA / account ownerPolymarket proxy address → not the signer, just the proxy/funder sideSo the key point is:API key + order signer = MetaMask EOAproxy address is not the address the API key is bound toIf your bot is using the proxy address as the signer, you’ll get that error.
Yes — the API key is bound to the EOA.Use this mapping:MetaMask private key → signerMetaMask wallet address → EOA / account ownerPolymarket proxy address → not the signer, just the proxy/funder sideSo the key point is:API key + order signer = MetaMask EOAproxy address is not the address the API key is bound toIf your bot is using the proxy address as the signer, you’ll get that error.
if signatureType=0, then this is not the sig-type issue.If allowance shows 0, the usual fix is:approve USDC/pUSD allowance again from the same wallet used by the botmake sure that wallet is the same one that owns the API keythen retry the orderIf you traded manually before, the bot may be using a different wallet/funder than the one you traded from. So the bot’s wallet still has 0 allowance even though your profile wallet already traded.In short:same wallet for allowance + API key + signerre-run approval on that walletthen place the order again
if signatureType=0, then this is not the sig-type issue.If allowance shows 0, the usual fix is:approve USDC/pUSD allowance again from the same wallet used by the botmake sure that wallet is the same one that owns the API keythen retry the orderIf you traded manually before, the bot may be using a different wallet/funder than the one you traded from. So the bot’s wallet still has 0 allowance even though your profile wallet already traded.In short:same wallet for allowance + API key + signerre-run approval on that walletthen place the order again
signatureType=3 is the likely problem.Your API creds and signer must match the proxy/profile wallet.If you’re on the Python client, sig type 3 may not be supported cleanly.So:use the proxy/funder address for the account flow,make sure the API key was created from that same wallet,or switch to a client/version that supports signatureType=3.
signatureType=3 is the likely problem.Your API creds and signer must match the proxy/profile wallet.If you’re on the Python client, sig type 3 may not be supported cleanly.So:use the proxy/funder address for the account flow,make sure the API key was created from that same wallet,or switch to a client/version that supports signatureType=3.
that error means your order is being signed by a different wallet than the one the API key was created for.Fix:generate the API key again using the same private key / wallet you pass as the order signer,make sure POLY_PRIVATE_KEY matches the wallet tied to POLYMARKET_API_KEY,don’t use the proxy/deposit wallet as the signer.So the rule is:API key owner = order signer walletproxy/funder address = separate, only for funding if your flow uses it
that error means your order is being signed by a different wallet than the one the API key was created for.Fix:generate the API key again using the same private key / wallet you pass as the order signer,make sure POLY_PRIVATE_KEY matches the wallet tied to POLYMARKET_API_KEY,don’t use the proxy/deposit wallet as the signer.So the rule is:API key owner = order signer walletproxy/funder address = separate, only for funding if your flow uses it
Your private key must match the wallet address you’re using in the SDK.If Polymarket gave you a proxy / funder / deposit address, that is not the key you sign with.Use the private key of the real EOA wallet that created the API creds, then set the proxy/deposit address only where the SDK asks for the funder/deposit wallet.So:POLY_PRIVATE_KEY = signer wallet private keyPOLY_FUNDER = proxy/deposit wallet addressthose two do not need to be the samebut the signer must match the API key creator
Your private key must match the wallet address you’re using in the SDK.If Polymarket gave you a proxy / funder / deposit address, that is not the key you sign with.Use the private key of the real EOA wallet that created the API creds, then set the proxy/deposit address only where the SDK asks for the funder/deposit wallet.So:POLY_PRIVATE_KEY = signer wallet private keyPOLY_FUNDER = proxy/deposit wallet addressthose two do not need to be the samebut the signer must match the API key creator
Just being a nerd 🤓
Just being a nerd 🤓
Clear cache and try again
Clear cache and try again
if your wallet is 4 months old and was created before the Pectra rollout, it should still be a real EOA and work with signatureType=0 .Check if it's actually EOA:If you created it via MetaMask/custom wallet = EOA (sigType 0) ✅If you created it via Polymarket UI "Connect Wallet" or "Email Login" = embedded wallet (sigType 3) ❌Older users with sigType 0/1/2 accounts are unaffected by the bug .Test: Try createOrDeriveApiKey() with your private key and signatureType=0. If order placement succeeds, you're good. If you get "maker address not allowed", your wallet is embedded (not EOA)
if your wallet is 4 months old and was created before the Pectra rollout, it should still be a real EOA and work with signatureType=0 .Check if it's actually EOA:If you created it via MetaMask/custom wallet = EOA (sigType 0) ✅If you created it via Polymarket UI "Connect Wallet" or "Email Login" = embedded wallet (sigType 3) ❌Older users with sigType 0/1/2 accounts are unaffected by the bug .Test: Try createOrDeriveApiKey() with your private key and signatureType=0. If order placement succeeds, you're good. If you get "maker address not allowed", your wallet is embedded (not EOA)
this is a known POLY_1271 (EIP-1271) bug, open for 3+ weeks with no fix.Why sigType 0 & 3 fail:Type 0 (EOA): New accounts are embedded wallets (not EOA), ECDSA recovery fails Type 3 (POLY_1271): SDK doesn't implement EIP-1271 wrapping + Privy TSS signing Workaround: Use an old EOA wallet (sigType=0) or 1-of-1 Safe EOA — both still work. New deposit wallets are broken until Polymarket patches the SDK.
this is a known POLY_1271 (EIP-1271) bug, open for 3+ weeks with no fix.Why sigType 0 & 3 fail:Type 0 (EOA): New accounts are embedded wallets (not EOA), ECDSA recovery fails Type 3 (POLY_1271): SDK doesn't implement EIP-1271 wrapping + Privy TSS signing Workaround: Use an old EOA wallet (sigType=0) or 1-of-1 Safe EOA — both still work. New deposit wallets are broken until Polymarket patches the SDK.
Daily limit: 100/day (Unverified), 3,000/day (Verified), unlimited (Partner) Reset: Midnight UTC (likely, not explicitly stated) Batch units: Docs don't specify — test or ask builder@polymarket.com Higher quota: Contact builder@polymarket.com for Verified/Partner upgrade Auth difference: Both have 25 req/min rate limit; daily txn limit is tier-based Upgrade via builder@polymarket.com for >100/day
Daily limit: 100/day (Unverified), 3,000/day (Verified), unlimited (Partner) Reset: Midnight UTC (likely, not explicitly stated) Batch units: Docs don't specify — test or ask builder@polymarket.com Higher quota: Contact builder@polymarket.com for Verified/Partner upgrade Auth difference: Both have 25 req/min rate limit; daily txn limit is tier-based Upgrade via builder@polymarket.com for >100/day
Polymarket