Builder attribution is an on-chain identifier crediting third-party interfaces for routing user volume to Polymarket CLOB. Embedded in signed orders, it records which interface sourced each trade on-chain.
Builder attribution is an on-chain identifier crediting third-party interfaces for routing user volume to Polymarket CLOB. Embedded in signed orders, it records which interface sourced each trade on-chain.
Builder attribution is a mechanism that records, on-chain and permanently, which third-party interface routed a given trade to Polymarket's CLOB (centralized limit order book). Think of it as a cryptographic receipt—when you place an order through Polymarket Trade or any other builder interface, that order carries an identifier that proves the trade came through that specific interface. This identifier is cryptographically signed as part of the order itself, making it tamper-proof and verifiable by anyone examining the blockchain. In essence, builder attribution creates an immutable audit trail linking each trade to its source interface.
The term originates from Polymarket's architecture as a decentralized prediction market that settles on-chain. Unlike traditional centralized betting platforms, Polymarket uses a public orderbook where orders are signed by users and routed through various interfaces. Builders—third-party platforms like Polymarket Trade that provide user-facing trading interfaces—integrate directly with Polymarket's CLOB and submit signed orders on behalf of their users. The builder code is a unique bytes32 identifier assigned to each builder, embedded directly into the signed order structure through the EIP-712 signing standard. This allows Polymarket to track which interface sourced which volume, enabling fair attribution of trading activity and helping manage incentive programs, fee structures, and partnership tracking. Without builder attribution, Polymarket would have no reliable way to know whether volume came from Polymarket Trade, Polymarket.com directly, or some other interface.
From a trader's perspective, builder attribution is almost entirely invisible and requires no action on your part. When you open Polymarket Trade and place a trade, the platform automatically includes the builder identifier in your signed order. You don't manually enter or select a builder code—it happens behind the scenes during the order signing process, which already requires your wallet's cryptographic signature. However, the presence of this identifier is profoundly important for transparency and accountability. It creates an auditable record on-chain showing that your trade came through Polymarket Trade's interface, not directly from your wallet or through a different platform. This is valuable for traders who want to verify their trading history or trace how their orders were routed. For Polymarket Trade as a builder, it's essential to prove that the platform successfully executed your order on the CLOB and can be credited for sourcing your volume.
A common misconception is that builder attribution affects trade execution, pricing, or speed. It absolutely does not. The builder code is metadata embedded in the signed order and has zero bearing on how your order is matched, what price you receive, or how quickly you fill against counterparties. Another misunderstanding is that builder code is something users or traders need to manage or worry about. In reality, it's a purely backend mechanism completely abstracted away from the user interface—you'll never need to think about it unless you're debugging an order, auditing your trade history on-chain, or integrating your own interface with Polymarket's CLOB. Some traders also incorrectly assume that different builders might offer different routes, better pricing, or faster execution for the same market. The truth is that Polymarket's CLOB is unified: all orders execute against the same shared orderbook regardless of which builder they came through. Your fill price and execution are determined solely by market supply and demand, not by your builder choice.
Builder attribution sits at the intersection of several related concepts in prediction markets and decentralized finance. It's a form of volume attribution, enabling Polymarket to credit builders for the volume they source and allocate rewards accordingly. It's also closely tied to order signing and EIP-712 compliance, the cryptographic standard used to sign orders in Ethereum-based systems. Smart contracts on-chain can verify the builder code without additional lookups, making attribution tracking efficient at settlement time. Understanding builder attribution also illuminates why third-party builders exist at all: they provide custom user experiences, unique features, better accessibility, or localized trading interfaces, but they must prove their value by demonstrating they route genuine, tradable volume to Polymarket.
In the broader ecosystem, builder attribution encourages healthy competition among interfaces. Each builder can be measured fairly on the volume they source, enabling Polymarket to offer incentives, fee rebates, referral rewards, or partnership benefits based on verified contribution. It also protects Polymarket from bad-faith builders claiming false volume or unfairly gaming attribution systems. Because the builder identifier is cryptographically signed by the user's wallet, only legitimate orders from that builder's interface count toward attribution—there's no way to inflate numbers or claim volume you didn't actually source. This mechanism is fundamental to how decentralized prediction markets balance fairness with the need to incentivize multiple quality interfaces competing for user volume.
Imagine you use Polymarket Trade to place a $50 bet on "Will Bitcoin reach $100k by year-end?" When you sign and submit that order, your wallet signs an EIP-712 message that includes Polymarket Trade's unique builder code. That code is recorded on-chain when your order settles, creating an auditable trail showing Polymarket Trade routed this specific trade volume to Polymarket's CLOB.