In the current implementation of FLEDGE, biddingLogicUrl, biddingWasmHelperUrl, dailyUpdateUrl and trustedBiddingSignalsUrl must have the same origin as the interest group owner.

The Fledge Explainer states that this may not be a long term constraint but does not provide a timeline for when this constraint may be lifted.

Ask
Clarify if and when this requirement will be lifted

Why is this needed
Requiring these Urls to have the same origin as the interest group owner causes some architectural constraints on ad-tech implementations for Fledge. Below are some example use-cases that this requirement is blocking

1. biddingLogic and biddingWasmHelper urls. The assets served by these endpoints are fairly static and could be served by a CDN to optimize for request latency, but this is not possible with the same-origin requirement.
2. trustedBiddingSignalsUrl In the trusted server model, a request is made from the client directly to the Trusted Execution Environment. This suggests that the trusted server needs its own origin, separate from the interest group owner’s origin.