I’m not terribly afraid of Apple doing that move. With Core Storage, Apple already has abstracted away low level storage access years ago. Even if Core Storage

I’m not terribly afraid of Apple doing that move. With Core Storage, Apple already has abstracted away low level storage access years ago. Even if Core Storage was mandatory (which it isn’t), O3X runs perfectly fine on top of Core Storage either with or without ZFS encryption. O3X will continue to run happily as long as block-level storage access remains built into macOS. And it will because APFS is a very young filesystem, which depends on block-level access; it took Apple a decade to build APFS from scratch so there’s no way for Apple to get rid of this dependency without throwing APFS away and starting from scratch. But what if Apple simply built APFS into one of the next generations of T-series chips so it can physically deny block-level access to software? Not going to happen: Apple needs APFS to work not only with built-in storage but also with external USB drives, RAM disks, DMGs, sparse bundles, and so on. This means APFS needs to remain in kernel space, and kernel code will continue to have block-level access, and so will O3X and all of its features.