Maternal and paternal dietary arsenic exposure impairs reproduction and development in zebrafish offspring: the role of HPG axis dysregulation and altered DNA methylation
Bibliographic record
Abstract
Arsenic is a known reproductive toxicant to fish; however, the persistence of its toxicity beyond the parental generation remains unclear. The present study investigated the effects of maternal and paternal arsenic exposure via diet on the reproduction and development of zebrafish offspring. Adult male zebrafish exposed to dietary arsenic [30, 60 or 100 μg/g as arsenite for 90 days; F 0 generation] were crossed with unexposed (control) females and vice versa to generate F 1 progeny of maternal (ME) and paternal (PE) arsenic exposures, respectively. F 1 larvae were raised to adulthood in clean water and diet, and males and females from respective ME and PE groups were then bred to evaluate the reproductive and developmental effects of parental arsenic exposure in the offspring generations. A significant reduction in fecundity, fertilization success, and larval (F 2 ) development was observed with ME to arsenic, even at the lowest dose. However, similar effects were only recorded with PE to arsenic at medium and high doses. In addition, the HPG axis genes were consistently downregulated in F 1 males and females of both ME and PE treatment groups. The circulating E2 and VTG levels were also decreased in F 1 females of the ME treatment groups, whereas the circulating 11-KT levels were reduced in F 1 males of both the ME and PE treatment groups. In general, dysregulation of the HPG axis was more sensitive to the ME than the PE. In addition, arsenic exposure induced hypermethylation of the promoter region of key HPG axis genes, notably sf-1 in the brain and cyp19a1a in the gonads in both males and females of F 0 and F 1 generations of maternal and paternal arsenic lineages. Overall, our study demonstrated that both maternal and paternal arsenic exposure causes reproductive and developmental toxicity in zebrafish offspring, likely by disrupting the HPG axis via epigenetic alterations.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".