It would probably be in conjunction with "location verification" where the chip won't operate without signed authorization from the verification server. If it can't contact that server or doesn't get reverification in N hours (or days or weeks), it won't run.
https://www.iaps.ai/research/location-verification-for-ai-chips
Which means you can't run internal-only-network servers and they
have to "go outside to touch grass". While theoretically you could arrange something like that for, say, AWS datacenter, where your workload is forcibly aborted every N whatever (reverification period), server wiped, empty image loaded, network updated to let GPU "go outside", then everything is re-loaded back, it'd be a big pain in the ass.
And for cases where companies want to have own internal-only AI runners this would require physical server re-connect. Giant pain in the ass.
At this point companies might go with more efficient Chinese AI software that runs on older hardware that doesn't demand random internet connectivity (versus current "oh it's slow? let's throw newer hardware at it"). Which would be ironic.
