Trump ties chip licenses to 15%: the policy still lacked a document

On August 11, 2025, Donald Trump confirmed that his administration expected to receive 15% of revenue associated with authorized China sales of Nvidia’s H20 and said he had initially asked for 20%. The statement turned an export license—a tool meant to manage a security risk—into a negotiation resembling revenue sharing. Yet one crucial piece was missing that day: a public text defining the obligation, its legal authority, the calculation and the collection mechanism.

The difference between a presidential statement, an individual license, a regulation and a tax is not semantic. It determines who is bound, what can be challenged, what Congress controls and what a citizen can verify. The official press-conference recording establishes that Trump described the negotiation. It does not by itself turn his account into a published rule.

What was confirmed and what still lacked a document

Four facts were firm. First, Nvidia was told on April 9 that exports to China, Hong Kong, Macau and D:5 countries of its H20 circuits—or circuits reaching similar memory- or interconnect-bandwidth parameters—would require a license. The company disclosed that fact in an 8‑K filed with the SEC.

Second, AMD received an equivalent requirement for its Instinct MI308. Its April 15 8‑K said it expected to apply for licenses, with no assurance they would be granted. Third, on August 5 AMD still said those applications were under review and excluded any revenue from MI308 shipments to China from its quarterly outlook, according to its official second-quarter release.

Fourth, the president publicly described the percentage on August 11. That supports the headline “Trump ties licenses to 15% of revenue.” It is more precise than stating that both companies definitively “will pay” under a fully implemented rule. In the primary sources available that day, there was no contract, written license condition, Commerce Department regulation, invoice or AMD statement accepting those terms.

This evidence map applies to any policy announcement. Separate who stated it; which document creates an obligation; when it takes effect; who enforces it; and what record shows enforcement. A press conference proves that words were spoken. A securities filing establishes what a company reported under legal obligations. Neither source should be made to perform the other’s job.

A license is not blanket permission to sell

Export controls do not operate like one switch declaring a product lawful or unlawful for everyone. The Commerce Department’s Bureau of Industry and Security administers the Export Administration Regulations and reviews applications containing information about the item, destination, end user and end use. Its official licensing page explains the process for determining whether authorization is required and applying for it.

“Washington allows H20 sales” is therefore too compressed. A license may cover identified customers or quantities, include conditions, expire and fail to protect a re-export or another user. Nor does it mean China will admit the product or that buyers will order it. Forecasting actual sales requires at least three open gates: US authorization, Chinese admission and customer demand.

The H20 and MI308 became subject to new controls in April. They were AI accelerators designed or positioned to operate within earlier limits. The episode reveals a durable pattern: compliance with a current regulatory threshold does not immunize a product against a later revision. A regulator may look beyond one compute number to memory, interconnects, the user, corporate ownership and diversion risk.

That is also the right way to read “obsolete chip.” It was Trump’s political characterization, not a technical specification. A component can sit below a manufacturer’s leading offer and remain valuable when thousands are clustered, software is optimized for its platform or local alternatives are less efficient. Security relevance cannot be inferred from whether a product tops the commercial catalog.

The economic cost was already verifiable

Uncertainty about the 15% does not erase the documented damage from the restriction. Nvidia initially expected up to $5.5 billion in charges for inventory, purchase commitments and related reserves. When it reported results on May 28, the realized charge was $4.5 billion; the company said it had sold $4.6 billion of H20 products during the quarter before the new licensing requirement and had been unable to ship another $2.5 billion in expected revenue. The figures appear in Nvidia’s financial release.

The live article misplaced the initial $5.5 billion estimate in July. The correct sequence matters: the estimate was filed on April 15, while the realized charge and affected sales were detailed on May 28. Moving the month distorts the connection between the licensing requirement and its accounting effect.

AMD recorded about $800 million in inventory and related charges for the MI308 in the second quarter. That was not a fine paid to the government, either. It was an accounting effect on inventory and commitments affected by the restriction. Combining a charge, foregone revenue and a public payment creates a fictitious total.

Every corporate figure needs a label: realized revenue, unshipped sale, impaired inventory, forecast, fee or Treasury transfer. Two dollar amounts can belong to different accounts and cannot automatically be added. This discipline measures the effect without pretending that Chinese billing, corporate margin and public revenue are one pool.

Tax, fee, revenue share or condition?

The US Constitution creates a genuine difficulty. Article I, Section 9, Clause 5 says no tax or duty shall be laid on articles exported from any state. The official Constitution Annotated explanation adds that the Export Clause covers taxes and duties but not every user fee; how a charge operates matters more than its label alone.

That is not enough for a news report to declare the arrangement unconstitutional. Doing so would require the exact instrument and an analysis of whether the 15% was an export tax, a charge tied to a government service, a negotiated license condition, a contractual obligation or something else. On August 11, the problem was that the instrument was not public. The intellectually honest conclusion was an open legal question, not a verdict.

A separate institutional problem remained. Export controls are justified by national security and foreign policy. If technology is too dangerous for a destination, receiving a share of sales does not by itself reduce its capability. If it can be exported with safeguards, those safeguards should be explainable independently of revenue. Mixing the two standards creates a risk that collection influences an assessment supposed to examine users, capabilities and diversion.

How to audit the policy instead of accepting the slogan

A public audit of the 15% would need at least six facts: the document imposing it; the legal authority invoked; the definition of revenue—gross, net, invoiced or collected; the licenses and products covered; the receiving agency; and the budgetary destination of the money. The next questions are whether the condition applies consistently to comparable applicants, how compliance is checked and what nonpayment triggers.

Until those elements appear, the language must preserve uncertainty: Trump said he had negotiated the percentage; the companies were subject to licenses; the costs of the restriction appeared in securities disclosures; the legal form of the collection was not public in the sources reviewed on August 11. That hierarchy prevents a secondary report from becoming proof of an agreement readers cannot inspect.

The lasting skill applies to any government announcement: ask not only “did it happen?” but “what kind of act happened, and which document produces its effects?” A statement can move markets. A license can authorize a particular transaction. A regulation creates general rules. A tax requires authority and administration. Telling them apart is the difference between reporting a display of power and demonstrating an executable policy.