{"id":"ba69724b-4c50-4b84-a40c-8e9f0ee19f17","seo":{},"slug":"verifymetadaoactivitywithfairscale","tags":[],"orgId":"00000000-0000-0000-0000-0000000000a0","title":"VerifyMetaDaoActivityWithFairscale","domain":"fairscale.xyz","status":"ACTIVE","iconUrl":"https://devtool-images.s3.ap-south-1.amazonaws.com/http-provider-brand-logos/fairscale.xyz-5a53d3f0-2dd1-49ce-a435-991bac7eb231.png","visibility":"PUBLIC","description":"Proves Fairscale's eligibility gate returned authorized:true for the connected wallet, i.e. the wallet has MetaDAO ICO or governance activity. Reads the authenticated POST https://fairscale.xyz/api/embed/authorize. The wallet is OPRF-hashed so only a stable pseudonym is revealed; the request body (wallet, launch token, privyUserId) is templated with SECRET-named params so none of it reaches the public claim, and the Privy bearer token is routed to secretParams by the SDK public-header allowlist. NOT YET CAPTURED OR REPLAYED - authored from a supplied curl, so the body template must be confirmed byte-exact against a real intercepted request before this is trusted. BINDING CAVEAT: in the sample request the body wallet differed from the wallet inside the bearer token, and the API still scored the body-supplied wallet, which suggests the gate may evaluate an arbitrary wallet. If so authorized:true does not prove control of that wallet - verify before gating anything. See agents/docs/workflow/reclaim-provider-registry.md.","effectiveSeo":{"title":"VerifyMetaDaoActivityWithFairscale — verify fairscalewallet","brandUrl":"https://fairscale.xyz","brandName":"VerifyMetaDaoActivityWithFairscale","dataPoints":["fairscalewallet"],"description":"Proves Fairscale's eligibility gate returned authorized:true for the connected wallet, i.e. the wallet has MetaDAO ICO or governance activity. Reads the authenticated POST https://fairscale.xyz/api/embed/authorize. The wallet is OPRF-hashed so only a stable pseudonym is revealed; the request body (wallet, launch token, privyUserId) is templated with SECRET-named params so none of it reaches the public claim, and the Privy bearer token is routed to secretParams by the SDK public-header allowlist. NOT YET CAPTURED OR REPLAYED - authored from a supplied curl, so the body template must be confirmed byte-exact against a real intercepted request before this is trusted. BINDING CAVEAT: in the sample request the body wallet differed from the wallet inside the bearer token, and the API still scored the body-supplied wallet, which suggests the gate may evaluate an arbitrary wallet. If so authorized:true does not prove control of that wallet - verify before gating anything. See agents/docs/workflow/reclaim-provider-registry.md.","primaryDataPoint":"fairscalewallet"},"latestVersion":{"major":1,"minor":0,"patch":3},"createMetadata":{"doneAt":"2026-10-20T06:15:49.752772+00:00"},"seoSuggestions":{"title":"Fairscale","iconUrl":"https://www.google.com/s2/favicons?domain=fairscale.xyz&sz=128","brandUrl":"https://fairscale.xyz","dataPoints":["fairscalewallet"],"primaryDataPoint":"fairscalewallet"},"updateMetadata":{"doneAt":"2026-10-23T11:36:20.126939+00:00"}}