Build specialized index for C+ profile
When synchronizing a new datapod, the whole oplog (the append-only TAMT for index request) is synchronized, which allows to serve as a ground truth of what has been submitted to the system. But this is not a convenient base to fill the database tables which do not mind the history like C+ profiles. Each profile edit indeed overwrites the previous version of the profile.
For this purpose, an other AMT can be built using the profile pubkey as keys so that when synchronizing, the database only has to read the last version of the profile.
This optimization would also allow to fetch the profile directly from IPFS using the pubkey instead of asking a grapqhl endpoint the CID of the profile. To decrease the depth of search a larger base could be used like base32 or base58 directly (theoretical depth 11 max but only 3 with the current number of pubkeys without vanity).
This index could also serve as a basis for the list of pubkeys allowed to submit to the datapod.