Oncofusion

start / graph / exp-lin28b-null-fetal-progenitor-second-oncogene-specificity-control

Experimentmoderate confidence 3 of 5: One strong study, or several smaller consistent ones.Q133-lin28b-fetal-ontogeny

PROPOSED: run a second oncogene in LIN28B-null human fetal liver CD34+ cells - the control that decides whether the KMT2A::AFF1 transformation block is fusion-specific or just a broken progenitor

also called the specificity control · second-oncogene control for Ling 2026

Removing LIN28B stops the infant-leukaemia fusion from turning fetal blood cells cancerous - but it also stops those cells from growing normally. So the honest question is whether LIN28B is special for this fusion, or whether a damaged cell simply cannot be turned cancerous by anything. Putting a different cancer gene into the same cells answers it.

The same thing, for a scientist

Ling et al. report two results from one perturbation: LIN28B-null human fetal liver CD34+ cells (i) lose proliferation, stem-like properties and B/NK output, and (ii) fail to transform on KMT2A::AFF1 induction [E1]. **Result (ii) is only interpretable as a fusion-specific requirement if result (i) does not by itself abolish transformability.** The control is to introduce a second, mechanistically unrelated transforming lesion into the same LIN28B-null cells and ask whether it also fails. **It may already exist behind the paywall** - the paper is not open access and is absent from PMC and Europe PMC, verified 2026-09-23 [E2] - so the first move is to read the paper or ask the authors, and the second is to run it. This entry exists so the graph records the control as *unread rather than known-absent*, which is a different claim and the one the evidence supports.

Go deeper
Design
elementspecification
cellshuman fetal liver CD34+ HSPC, LIN28B-null and LIN28B-intact, >=3 independent donors, matched gestational age
arm Ainducible endogenous KMT2A::AFF1 (the published arm, as a positive reference)
arm Ba transforming lesion whose mechanism does not run through the fetal programme. Best first choice: BCR::ABL1, which transforms adult and cord-blood progenitors readily and has no reported fetal-state dependence. Second choice: a MYC/BCL2 pair, or NRAS-G12D plus a differentiation block
arm Cempty vector / no induction
readouttransformation frequency (serial replating and/or immortalisation and/or xenograft initiation - use the same operational definition the source paper used, which is why reading it comes first)
key comparisonfold-reduction in transformation frequency on LIN28B loss, arm A versus arm B
interpretationarm B unaffected -> the requirement is fusion-specific and Ling et al.'s headline stands as stated. Arm B equally blocked -> the requirement is a statement about progenitor competence, and the headline needs rewording to 'a LIN28B-competent fetal progenitor is required', which is a weaker and much less targetable claim

Why BCR::ABL1 specifically. It needs no fetal programme, it transforms human CD34+ cells of several ontogenetic stages, and the graph already holds fusion-bcr-abl1. It is also the lesion for which a failure to transform would be least explicable by anything other than a broken cell.

Why this is the highest-value cheap experiment in the beat

This project's recurring failure mode is a measurement whose control was never specified, and this is a textbook instance available in advance rather than in hindsight. The experiment is one extra arm in a system that already exists, in a laboratory that already has the cells, and its two possible outcomes point at opposite therapeutic conclusions:

  • fusion-specific -> LIN28B is a target with a mechanism, and the initiation result is about KMT2A::AFF1.
  • competence-general -> LIN28B is a growth requirement of fetal progenitors, the transformation result is a corollary, and a LIN28B inhibitor is a general anti-progenitor agent with a paediatric toxicity profile and no leukaemia selectivity.

Nothing else in this beat separates those two readings.

Facts and figures
statusPROPOSED - and possibly already done behind a paywall; READ THE PAPER FIRST
designHuman fetal liver CD34+ HSPC, LIN28B-null versus LIN28B-intact, >=3 donors. Arm A: inducible endogenous KMT2A::AFF1. Arm B: BCR::ABL1 (or MYC+BCL2, or NRAS-G12D plus a differentiation block) as a fetal-programme-independent transforming lesion. Arm C: vector control.
readoutTransformation frequency using the same operational definition as the source study (serial replating, immortalisation, and/or xenograft initiation), compared as fold-reduction on LIN28B loss between arms A and B.
controlsArm C vector; LIN28B-intact counterparts of every arm; donor-matched pairs; a knockout-efficiency measurement (protein-level, not just indel frequency).
cost tiermed
timeline3-6 months given existing LIN28B-null fetal liver cultures; longer if fetal material must be newly obtained under local regulatory approval
decision ruleIf arm B's transformation frequency falls by less than 2-fold on LIN28B loss while arm A's falls by 5-fold or more, the requirement is fusion-specific. If both fall by 5-fold or more, it is a statement about progenitor competence.
answers hypothesishyp-fetal-state-is-permissive-for-lymphoid-and-protective-for-myeloid-kmt2a-transformation
blocking dependencyaccess to the full text of PMID 42213620, or correspondence with the authors
How this could bite us back
  • If the answer is 'competence-general', an entire therapeutic rationale collapses, and this graph will have been carrying it for at least two cycles. That is the outcome to plan for, not the one to hope against.
  • Conversely, running the control and getting 'fusion-specific' does not make LIN28B druggable - it only makes the requirement real. The normal-lymphopoiesis toxicity is unaffected by this experiment's outcome.
Still open
  1. Did Ling et al. run this control? A single email would resolve it and would be cheaper than any experiment in this beat.
  2. Is there a transforming lesion known to work in human fetal liver CD34+ cells that is definitely fetal-programme-independent? BCR::ABL1 is the best candidate this beat can name but its behaviour in first-trimester fetal liver cells is itself not well documented.
  3. How severe is the LIN28B-null phenotype quantitatively - a 20% proliferation deficit or a 20-fold one? The severity determines whether the control is likely to be informative or whether the cells are simply too sick to test.
Every source behind this entry (2)
  1. E1strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    LIN28B was essential in human fetal liver CD34+ cells to maintain proliferation and stem-like properties and to support B- and NK-lymphopoiesis, and in the same system human FL CD34+ cells fail to transform upon induction of the KMT2A::AFF1 translocation in the absence of LIN28B.

    The fetal specific gene LIN28B is essential for human fetal B-lymphopoiesis and initiation of KMT2A::AFF1 infant leukemia. · Ling RE, Welsh AM, Hamer L, Jackson T, Neil E, Elliott N, et al. · Blood 2026
    What this evidence cannot show

    ABSTRACT ONLY and paywalled. The two results quoted sit in the same abstract and the abstract does not relate them. THIS ENTRY MAKES NO CLAIM THAT THE CONTROL WAS OMITTED - it claims only that it cannot be read. If the paper contains a second-oncogene arm, this experiment is already done and the entry should be amended to record its outcome rather than deleted.

    Evidence that argues against this (1)
    • The concern would be defused if the LIN28B-null phenotype is mild - a shift in lineage output rather than loss of progenitor function - which is what the mouse literature reports for Lin28b deletion in fetal progenitors. J Exp Med 2016
  2. E2established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    The source paper is not open access and is absent from PubMed Central and Europe PMC as of 2026-09-23, so its control arms cannot be read.

    What this evidence cannot show

    A statement about availability on one date. Blood deposits to PMC after an embargo; re-check before repeating.

    Evidence that argues against this (1)
    • Availability is a moving target, not a fact about the paper. Blood deposits to PMC after an embargo, so this record's 'not open access' status will become false and any bounded statement resting on 'the full text could not be read' silently expires. A later reader must re-check rather than inherit this. source 2026
Connected to