Co-Founder, Polygon
Sandeep Nailwal (@sandeepnailwal) is Co-Founder of Polygon, mapped from the Coinfest Asia 2026 "Top Web3 Founders in Asia" founders card (Melasti Beach / White Rock Beach Club, Bali, 20-21 Aug 2026) onto the UnicornsMap.com $UM-Radar GIS OSINT layer as an Asia founder-intelligence node. Public title at mapping time: Co-Founder, Polygon. Base: Mumbai, India — GIS pin 19.076, 72.8777 (city-centroid pin, real coordinates only). Onchain rails observed: Polygon (POL) settlement + scaling rail — live-check required. Currencies carried: INR, POL, USD. Risk flags: POL token volatility — live-check. Identity confidence 84/100 (likely) — public-source only; no invented attendees, net-worth or deal claims; no handle invented (HANDLE_UNKNOWN where unpublished). Alpha cross-reference (not a product of this founder): the Frankencoin ($ZCHF) fixed-rate board measured ~1.11% live-check on 2026-09-07 — cross-linked here as corridor intelligence only, see /radar/johannes-kern-frankencoin. x402 intelligence dossier on this page settles at $4.99 via @bankrbot; founder-indexed by Aleksei Dolgikh (@alexdolbun).
Co-Founder — per public founders card + public company record.
Top Web3 Founders in Asia card, Bali 20-21 Aug 2026.
1 entities geo-pinned · toggle People / Institutions · 19.076, 72.8777
🔭 WATCH: agent-side integration count · whether the rail survives its own token · rail volume, not follower count
🔍 Sandeep Nailwal is carried at MED confidence on 2 filed sources. The horizon below is a hypothesis with a shelf life, not advice.
Paste the badge on a site, a README or an agent page. It serves live from the edge and links back with its own attribution code.
Machine form: GET /badge/sandeep-nailwal.json
Paste a Base wallet and this record joins your watchlist. Nothing is uploaded, nothing is stored off-chain beyond the list, and removing it is one click.
Paste the badge on a post, a deck or a partner page. The image links home with ?ref=badge-sandeep-nailwal, so every embed is attributed in the referral ledger and every reader lands on this record.
JSON twin: /badge/sandeep-nailwal.json returns the same snippet for a generator.
Paste the badge on a post, a deck or a partner page. The image links home with ?ref=badge-sandeep-nailwal, so every embed is attributed in the referral ledger and every reader lands on this record.
JSON twin: /badge/sandeep-nailwal.json returns the same snippet for a generator.
Paste the badge on your own page. The image is edge-cached SVG, the link carries the attribution code, and the counter moves in the referral ledger.
The record is what it is: Co-Founder, Polygon. Nothing below is filed — it is the shape the seat would take if the current trajectory holds, and it is re-scored every time a new public source lands.
🔭 agent-side integration countExpect the mandate to widen before it deepens. Watch whether Polygon adds an adjacent function to the seat rather than a bigger title on the same one.
🔭 whether the rail survives its own tokenA second mandate is the normal move here — a board seat, a fund-side advisory role, or an operating chair next to the current one. The tell is a first public co-signature, not an announcement.
🔭 rail volume, not follower countFirst capital event window. Either a priced round behind Polygon or a personal vehicle appears. Watch rail volume, not follower count rather than the headline valuation.
🔭 which chain the settlement moves to nextJurisdictional switch is the highest-probability structural change from Mumbai, India. A second residence, a second entity, or a second currency book (INR to a settlement unit) is the observable.
🔭 fee take-rate disclosureInstitutional shell forms: a holding vehicle, a family-office wrapper or a named co-investment club. Shells are quiet — the disclosure arrives through registry filings, not posts.
🔭 agent-side integration countDistribution becomes the constraint. At this horizon the question is who carries Polygon's output and this seat's name, and on what terms. Watch which chain the settlement moves to next.
🔭 whether the rail survives its own tokenSuccession pressure. Either a named deputy appears under the seat or the seat is re-scoped away from day-to-day. Both read as the same signal from outside.
🔭 rail volume, not follower countSecond-order liquidity: secondary sales, a tender, or a strategic minority into Polygon. This is where an OSINT file usually goes stale for six months and then re-prices.
🔭 which chain the settlement moves to nextRecord consolidation. By here the file should be readable as a single arc rather than a list of events, and the Mumbai, India base stops being the interesting part.
🔭 fee take-rate disclosureEnd-of-horizon check. Re-read 2026 against 2036: the useful output is which of the eleven rows actually printed, and which were noise carried by the market rather than the person.
🔭 agent-side integration count🔍 Deterministic horizon model: every row is derived from facts already on this record and re-scored when a new public source lands. No forecast value is asserted.
Buy without a browser: GET /oauth/protected-resource, then tools/call fetch_profile over MCP. Bulk and 402 retries are idempotent on the same slug.
Machine pack: /api/um-radar/agent-pack?slug=sandeep-nailwalBatch / dataset pricing on request
The dossier prose stays public. The space around it is for sale: locales, frames, video, links, the city slot, the verified badge. Holding $UM cuts the price at quote time - the balance is read from your wallet, nothing is self-declared.
Public OSINT radar only. Not investment advice. Not a prediction engine.
Creator-fee revenue is onchain and verifiable.