Is dm-verity table still used in android verified boot 2.0?

[Coapprentice]

It seems instead of using dm-verity table, Android Verified Boot 2.0 only uses hashtree whose root hash is stored in vbmeta partition and vbmeta is signed by the OEM.

Hashtree also doesn't have to be appended with each partition because integrity can be verified by reconstructing the hashtree in memory at boot time and comparing its root hash with the one stored in vbmeta.

Does it need dm-verity table or only hashtree in the footer of each partition?

[Coapprentice]

So I was right. Both dm-verity table and hashtree are optional to include in footer. To verify a partition, storing its hash and hashtree descriptor in vbmeta is enough because hash and hashtree are reconstructed in memory at boot time for integrity checking anyway. The only requirement is vbmeta should be signed.

Source: The integrity footer on an image can be removed from an image. The hashtree can optionally be kept in place.