I would like to thank the author for the work and the update. Now, the phylogenetic methods of the example are much clearer. The analysis of contamination of the proteomes is shared and worth sharing as the user could choose genomes according to contamination thresholds. Moreover, the HGT reasoning, together with the contamination assessment, is more precise now. The documentation shared in the Zenodo repository is better, allowing the user to trace every process step, database file and protein header, which confers robustness to the resource. The new example with the 20 markers is much more suitable for showing the potential of the database and strengthens its power to gain insights into the clades represented in LukProt.
Regarding the colours, it was just a minor comment. They are nice, although I could not distinguish some in my printed version. However, the annotation in the internal nodes helps to detect clades properly. Maybe, and just as a suggestion, reducing the palette to a certain taxonomic level (all SAR with the same colour, not a palette of a given colour) would be a strategy to reduce the colour complexity of the figure and increase the readability, but it is a matter of style.
I consider the reviewed version of the paper suitable for publishing, and the work done has substantially improved the manuscript.

The manuscript of Sobala provides a new pervasive and curated eukaryotic database. It gathers information from EukProt and many other resources to increase the Metazoa sampling in released protein databases. I consider the paper interesting for the phylogenomics and comparative genomics communities, and I thank the author for their work. The analysis and data management are suitable. However, I have found some weaknesses that would make the database user distort the interpretation of the given protein sets. I would recommend this paper for publication after some corrections.

Overview and general comments
The database construction is rigorous as it considers different sources of information, homogenises the IDs, and distributes it using standard formats. The metadata incorporated to the database is easy to read and parse, as well as it is completely integrated with EukProt, maximising the compatibility between both databases. The server that the author provides is accessible, and the taxonomic structure implemented in the server helps the user to perform clade-specific analyses.

I miss an analysis of the contamination and quality of each genome. Providing this information to the users would let them better choose the genomes for downstream analyses. Moreover, this point is essential for lateral gene transfer analyses.

The taxonomy accounts for up-to-date literature, and they performed a readable table, which I personally think is a sound synthesis work and thank. It enforces the deep branches of the events the author considers important for the Metazoan researchers. The author may improve the documentation for the taxonomic tree in the supplementary file. The structure of the taxonomic groups and how they cluster is not clear to me. An indentation table structure with the literature would be more understandable as you would easily identify shallow and deep groups.

Regarding the example analysis, I found the first paragraph in the results more suitable to be written in methods, as the huntingtin example method’s section seems incomplete and unclear. I could not understand why the author included two inference software and which criteria they used for removing branches from the preliminary trees. I emphasise this in the detailed comments of my review.

I finally consider that the assessment of limitations is fair, although I think that the author should add a contamination assessment to the database. BUSCO completeness and contamination values (for instance calculated with OMArk) would be valuable and would make the database even more complete.

Detailed comments on the methods
The methods are proper and suitable for the kind of data that Sobala used. However, I see some weaknesses that they should address:

• Dataset naming: the renaming sounds good. Although the author incorporates the sequence identifier of the original source after the protein ID (L81), a file connecting the protein IDs of LukProt, EukProt, AniProtDB, would be helpful for the community in the cases they change or just for comparison purposes. Despite this, the files are accessible and well-documented in the Zenodo repository.
• Distribution of the database: it may be helpful to separate the BLAST databases by the taxonomic depth of the database in separate compressed files, as Zenodo allows a folder structure. I propose the author to share the folder structure with the compressed version of the database rather than the complete set of databases in a single compressed folder if they consider it appropriate. It would be easier to use and download.
• Data processing: Sobala uses two different software (Trinity and TransAbyss) and multiple versions of the Trinity software for assembling transcriptomes. Moreover, they also use different versions of the software for protein prediction (TransDecoder). However, they do not explain why the author chooses one or the other and the criteria substantiating the software election. The author should include this information in the manuscript. Regarding the clustering, I see the same as previously commented. The author does not specify why and when proteomes are clustered (“in most cases”, L96). Moreover, for the strain “pangenome”, they do not determine whether the CD-HIT parameters are or are not maintained.
• Huntingtin example: as I previously said, the methods section of this example is incomplete. The author should describe better how they obtained the phylogeny with a clear description of each step. They should move the first paragraph of the results section to the methods section with a few changes and clarifications: 1) the procedural scheme is diffuse, I had to read twice to understand the steps they followed; 2) the changes in the CD-HIT clustering identity parameter are not justified; 3) I miss a definition for “outlier” (L192), as some sequences have been removed, I consider necessary to explain which criterion has been used to remove them.

General detailed comments 
L58: the author should define AniProtDB, Animal Proteome DataBase (AniProtDB).

L58,64,134,138: AniProtDB appears written differently. The author should homogenise them to the database name in the reference “AniProtDB”.

L127-128: HGT analyses are sensitive to contamination, as they consider that a given protein originated through HGT when it is more similar to a distant taxon than to a close one. For this reason, although I agree with the author that phylogeny will help “drawing conclusions”, I consider that this argument does not apply to HGT. In my opinion, they should at least release a bona fide list of proteins for each organism and a bona fide sister database.

L133: I suppose that a dataset is the whole protein set for a species, but it is not defined. It would be helpful.

L134: a brief comment on the sources of the newly added datasets would be necessary, at least commenting that they have been collected from repositories of numerous studies and the source is available in the metadata table.

L152: the figure 1 colours need to be more different to be easily distinguished. Most of them are similar colours (Apusomonadida, Streptophyta, Breviatea…).

L152: the table 1 title starts with an uppercase letter, while the figure 1 caption starts in lowercase; it should be uppercase.

L202: the figure 2 caption lacks the caption for the panel B, it should be added. Moreover, I suggest to increase the size of the panel B and put the label “A” on top. There are some groups which do not match the topology (Ambulacraria placement, Chordata…), I would understand the size when both topologies match, but I do not see the point here.

L214-216: sequence similarity networks gain insights into deeper relationships and higher detection of far homologs. However, the whole analysis is trying to remove homologs by clustering and manual curation, this sentence may confuse the reader.