OpenZeppelin made Chainlink the default for cross-chain and compliance in its token tooling, and if you tick the compliance box, your token's license changes. A week ago, OpenZeppelin announced a strategic partnership with Chainlink. CCIP and ACE, Chainlink's cross-chain protocol and its Automated Compliance Engine, are now built into the Contracts Wizard, OpenZeppelin's AI tooling and its docs. The ERC20, Stablecoin and RWA generators all offer both options. Picking the CCIP option makes the token expose the mint and burn calls a Chainlink burn-and-mint pool needs, behind the token's own permissions. It also names an administrator for CCIP registration. That part keeps whatever license you chose, because no Chainlink code goes in. The ACE option is different. It forwards transfers, mints and burns to a Policy Engine that you deploy and configure. OpenZeppelin's own docs say tokens using ACE fall under BUSL-1.1, and production use has to satisfy the ACE license and its additional use grants. For years, a generated OpenZeppelin token carried whatever license you picked, usually MIT. A single checkbox now changes that, and a junior dev in a hurry may never notice. The generator doesn't register your pool, set permissions or write your policies. Attaching a Policy Engine doesn't configure any policy, and you stay responsible for meeting whatever rules apply to you. The announcement also mentions a migration path from OpenZeppelin Defender to Chainlink's Runtime Environment. None of this is hidden, and for an RWA team that already wants Chainlink, it saves real integration work. I just want builders to choose it on purpose, not because the wizard put it there.