Pretty much the same, I would say.

An eSim is essentially a virtualization solution with each eSim profile effectively running in a container which can be set up, deactivated, and deleted only by the profile manager.

The profile manager communicates with the provisioning infrastructure in an encrypted and authenticated way, so the profiles being loaded, i.e. their code (if any) and data, are as inaccessible as those on a physical SIM.

While active, an eSim profile has all the same capabilities as a physical SIM, including remotely loading Java applications, issuing proactive commands to communicate with the network, registering for event notifications about location changes and incoming/outgoing calls…

So an iOS device with an eSIM is running a JVM in the eSIM?

Yup! I have at least two eSIMs myself that have SIM applications running in them that wouldn't be able to function otherwise. (The operators do IMSI switching based on SAT event triggers, from the looks of it.)

The Oracle JVM installer wizard isn't lying when it's saying that there is billions of devices running Java in the world :)

This is blowing my mind. I'm not sure what's real anymore...

Considering that sim cards do a lot (think roaming on cheapest partner etc) .. you can bet that eSIM are equally capable and maybe even more capable.

I’d like to know the same thing! Maybe the config files are more observable?

They are encrypted and authenticated, since they contain the symmetric keys used to access the network.

Without the keys of a legitimate eSim (i.e. those chaining up to a GSMA-approved vendor) you won‘t be able to inspect a profile even if you know the activation code.

+1 I came to ask the same question