XPO1 / exportin-1 (CRM1) - the cell's main nuclear export receptor, and a chromatin-bound transcriptional scaffold
also called CRM1 · exportin-1 · Exp1 · chromosome region maintenance 1 · XPO1_HUMAN
XPO1 is the protein the cell uses to push hundreds of other proteins out of the nucleus, grabbing them by a short greasy tag and using a molecular battery called Ran-GTP to make the trip one-way. The surprise for leukaemia is that some XPO1 never leaves: a pool of it sits directly on DNA, including at the HOX genes, where several different leukaemia lesions dock onto it. Whether that pool is a specific address or just a protein that sits on active genes everywhere is the open question.
The same thing, for a scientist
XPO1 (UniProt **O14980**, **1,071 aa**, HGNC symbol XPO1, protein name exportin-1, gene synonym CRM1) is the karyopherin-beta family receptor for leucine-rich nuclear export signals. It binds NES cargo cooperatively with **RAN-GTP** in the nucleus, docks on nucleoporins at the nuclear pore, and releases cargo in the cytoplasm when RANBP1/RANGAP1 trigger GTP hydrolysis - the asymmetric Ran-GTP/GDP gradient is what makes export directional [E1]. Structurally it is a superhelix of HEAT repeats; **Cys528** lies in the NES-binding groove and is the covalent target of leptomycin B and of the SINE compounds selinexor and eltanexor [E4]. **The part this graph cares about is not the textbook function.** A fraction of XPO1 is detectable **on chromatin**, at active regulatory regions including the **HOX clusters and the MEIS1 locus**, and that pool behaves as a pre-bound platform that genetically diverse leukaemia drivers dock onto - NUP98 and NUP214 fusions through FG-repeat-XPO1 contacts, NPM1c through its NES [E2][E3]. See `mechanism-nes-crm1-chromatin-addressing` for the route and `localization-xpo1-chromatin-bound-versus-soluble-pool` for what separates the two pools. **And XPO1 is not a selective dependency of KMT2A-rearranged leukaemia.** In this project's own DepMap scan it is profoundly pan-essential (mean gene effect **-2.14** across 1,208 lines) and ranks **2,228 of 17,728** on KMT2A-selectivity, with a difference of only **-0.070** between KMT2A-rearranged and other leukaemia lines [E5]. Any therapeutic argument here is about a shared address, not about a selective vulnerability.
This is a prediction, not a measurement. No one has seen this protein in this shape. The colours say how much the software trusts itself, and that is worth reading before anything else — the orange stretches are places the model is effectively saying this part has no fixed shape.
I have never read one of these pictures before
A protein is one long chain of amino acids that folds up. The ribbon traces that chain from one end to the other; it is not a wire, it is a simplification of where the backbone runs. Drag to rotate, scroll to zoom.
Domains are the stretches of chain that do a particular job, and they are what the coloured blocks above the picture mark out. Click one and the view flies to it. In this project the important question about any domain is usually whether the fusion still has it — the labels say lost where it does not.
Anything in yellow sticks is a bound small molecule, which is usually the drug.
The Ran-GTP cycle in one paragraph
In the nucleus, RCC1 keeps RAN loaded with GTP. XPO1 binds a leucine-rich NES only when RAN-GTP is also bound - the two binding events are cooperative, which is why a cargo is picked up in the nucleus and nowhere else. RANBP3 assists complex formation, and the XPO1 region 327-450 is annotated as necessary for Ran interaction and export-complex formation 1. The trimer transits the pore via nucleoporin contacts. In the cytoplasm RANBP1 and RANGAP1 drive GTP hydrolysis, the complex falls apart, and the cargo is released. Nothing about this cycle requires XPO1 to leave chromatin, and that is the loophole the leukaemia lesions exploit.
Identifier check, done live
gene_exact:XPO1 AND organism_id:9606 AND reviewed:true returns exactly one reviewed human record: O14980, XPO1_HUMAN, primary gene name XPO1, protein name Exportin-1 (Exp1) (Chromosome region maintenance 1 protein homolog), 1,071 aa. gene_exact:CRM1 returns the same single record. Rules 62-65 clear here - there is no paralogue trap on XPO1 itself.
The trap is elsewhere, and it is real. CAN is a UniProt gene synonym of NUP214, the nucleoporin XPO1 docks against, and is a catastrophic bare search term (SET-CAN returns about 1,375 records of ordinary English). It is already in data/symbol-collisions.json. CRM1 is also an abbreviation of chromosome region maintenance 1, which is the protein name and not a second gene.
Sequence positions verified against the fetched sequence on 2026-09-20: residue 528 is C, residue 571 is E.
Why the chromatin pool is not the textbook function
Every standard account of XPO1 is about traffic. The chromatin observation says something different: XPO1 is detectable at active regulatory regions, is not obviously in transit there, and is upstream of the lesions that bind it. In LOUCY, knocking down SET-Nup214 lowers HOX expression without significantly reducing chromatin-bound CRM1 3. That ordering is what turns a transport receptor into an address.
The reframing has now been written up explicitly as a pre-bound XPO1 platform model covering NUP98/NUP214 fusions and NPM1c, with the proposal that the dual engagement (XPO1 contact plus a partner-encoded chromatin contact) lowers the threshold for condensate formation at HOX/MEIS loci 2.
Correction of emphasis, 2026-09-21 (Q68): the chromatin pool may not be locus-restricted at all
This entry, and the beat built on it, describe chromatin-bound XPO1 as a locus-restricted pool at the HOX clusters that acts as an address. That framing comes almost entirely from one laboratory's ChIP-seq in LOUCY and MEGAL and from that author's own 2026 perspective 2.
An independent group measuring the same thing with a chemical tool reports something much less specific. Chen et al. (PMID 38917791, Cell Chem Biol 2024) show that XPO1 directly binds chromatin and co-occupies HUNDREDS of loci with p300, and that degrading XPO1 with C646 or S109 diminishes the chromatin occupancy of both, so that an XPO1 degrader phenocopies p300 inhibition. Every phenotype they attribute to XPO1 is controlled with the XPO1-C528S drug-resistance allele.
Two consequences this entry now carries.
- A factor present at hundreds of p300-marked active loci is a general chromatin cofactor, not a postal address. Finding XPO1 at HOXA in a HOX-driven leukaemia line is then the expected observation rather than a discriminating one, and whatever specificity exists has to come from the lesion's own chromatin contacts.
- The specificity control for any XPO1-inhibitor chromatin result is the C528S allele, and no study cited anywhere in this beat has run one. That includes the DEK::NUP214 CUT&RUN and the 2026 menin preprint.
The data.uniprot, length_aa, Cys528 and Glu571 assertions are unaffected; this corrects the framing in the title's second clause ('a chromatin-bound transcriptional scaffold'), which is right, and the beat's reading of it as an address, which is not established.
The epigenetic column: a chromatin position, a counted absence, and drug synergy standing in for mechanism
XPO1 modifies nothing. It is a HEAT-repeat superhelix that binds leucine-rich NES cargo cooperatively with RAN-GTP, and Cys528 in the NES groove is the covalent target of leptomycin B and the SINE compounds. So the writer/eraser/reader answer is no on all three, and the interesting content is what sits around that.
The position, with the correction this entry already carries. A fraction of XPO1 is detectable on chromatin at active regulatory regions including the HOX clusters and the MEIS1 locus, acting as a pre-bound platform that NUP98 and NUP214 fusions and NPM1c dock onto. That is this entry's 2 and 3, and it is why XPO1 is in this project at all. It is also qualified by this entry's own 2026-09-21 correction: the chromatin pool may be a general co-activator position rather than a leukaemia-specific address. Both statements matter for the epigenetic column, because "XPO1 is at HOXA and MEIS1" sounds like a chromatin mechanism and is currently a localisation observation with an unresolved specificity question.
The mark is unmeasured, and the absence is counted rather than assumed. exp-locus-resolved-h3k79me2-under-xpo1-inhibition records that XPO1-inhibitor terms combined with H3K79 terms return 0 records on PubMed, against operands of 829 and 654, with a positive control through the identical shape returning 3, bounded by titles and abstracts with supporting figures not searched. One thing worth adding about that bound: it is written in the grouped (A OR B) form, which expands to [All Fields] rather than title/abstract, so the search that actually ran was broader than the one written down - which makes the zero conservative. The absence is stronger than stated, not weaker. Nobody has measured a histone mark under an XPO1 inhibitor in this disease or, on this evidence, in any disease.
What does exist is pharmacology, and it should not be mistaken for mechanism. The only published intersection between XPO1 and the epigenetic machinery is combination synergy: the p300/CBP acetyltransferase inhibitor A485 synergises with the XPO1 inhibitor KPT-8602 in multiple myeloma E8, the same pairing is reported against EP300 in diffuse large B-cell lymphoma E9, selinexor assists vorinostat in tongue squamous carcinoma, and nuclear-to-cytoplasmic transport is a druggable dependency in HDAC7-driven small-cell lung cancer E10. Three of those four involve an acetylation-machinery agent and an XPO1 inhibitor in the same well. None is in KMT2A-rearranged leukaemia and none reports a histone-mark readout, so what they establish is that the combination is worth trying and nothing at all about why.
The experiment that would close this is already written down. exp-locus-resolved-h3k79me2-under-xpo1-inhibition specifies spike-in-normalised H3K79me2 ChIP-seq or CUT&RUN under selinexor or leptomycin B at a displacement-not-degradation exposure, reported as both the HOXA cluster profile and the genome-wide global level, with fusion and DOT1L occupancy at the same loci and an NES-mutant control. Its designed purpose is to discriminate the CALM-AF10 export model from the docking model, which predict opposite directions for the focal HOXA H3K79me2 peak. The same run in a KMT2A-rearranged line would answer the plainer question this entry cannot: does blocking nuclear export move a chromatin mark at fusion targets at all? Given that this graph already records ziftomenib/selinexor synergy in KMT2A-rearranged and NPM1-mutant AML, that is a combination with a clinical rationale and no chromatin pharmacodynamic endpoint.
| uniprot | O14980 |
|---|---|
| length AA | 1071 |
| hgnc symbol | XPO1 |
| uniprot entry name | XPO1_HUMAN |
| primary protein name | Exportin-1 |
| gene synonym | CRM1 |
| resolution note | gene_exact:XPO1 and gene_exact:CRM1 each return exactly one reviewed human record (O14980); gene_primary read back as XPO1; residues C528 and E571 read directly off the fetched sequence 2026-09-20 |
| chromosome | 2p15 |
| alphafold ID | AF-O14980-F1 |
| PDB entry count uniprot | 18 |
| chromatin bound pool | detectable at HOX clusters and the MEIS1 locus; upstream of SET-Nup214 binding in LOUCY; see localization-xpo1-chromatin-bound-versus-soluble-pool |
| cell context evidence class | expressed_in (ubiquitous) + required_in (pan-essential, floor-compressed, NOT selective) + maintains_a_state (combination only, unattributed). Deliberately not pooled: the dependency is general and the state effect is drug-combination-specific. |
| cell context shown for fusion | PARTIAL, and weaker than the entry's degree suggests. The only KMT2A-rearranged cell-context evidence is a 2026 bioRxiv PREPRINT in AML - MV4;11, i.e. KMT2A::MLLT3 - and it is a combination study. There is NO KMT2A::AFF1 experiment, NO infant B-ALL experiment, and no monotherapy demonstration that XPO1 maintains any cell state. Measured 2026-09-21: (XPO1[tiab] OR selinexor[tiab] OR CRM1[tiab]) AND (KMT2A[tiab] OR MLL[tiab]) AND (differentiation[tiab] OR "cell state"[tiab] OR "stem cell"[tiab]) returns 2 records. Zero in titles and abstracts is not the claim here - 2 is - but supporting figures were not searched. |
| subcellular location uniprot evidence note | READ WITH EVIDENCE CODES ON 2026-09-21 (Q72): all four values above, and the accompanying free-text note, are UNCODED in UniProt O14980 - no ECO:0000269, no ECO:0000305, no ECO:0000250. The list is a curated summary, not an attributed assertion. It is also silent on the chromatin-bound pool, which is the only pool this graph's export-axis argument depends on. See data.localization and E_q72_xpo1_loc1. |
| subnuclear localization | NUCLEOPLASM, CAJAL BODIES AND NUCLEOLI per UniProt, all uncoded [E_q72_xpo1_loc1]; plus a CHROMATIN-BOUND pool at HOXA and HOXB cluster regions measured by ChIP-seq with two independent anti-CRM1 antibodies in the human T-ALL line LOUCY, where CRM1 is upstream of SET-Nup214 rather than recruited by it [E_q72_xpo1_loc2 counter-note]. The chromatin pool and the shuttling pool have NEVER been separated as biochemical species - see localization-xpo1-chromatin-bound-versus-soluble-pool, which is the entry that carries this properly. [EXPLICIT NEGATIVE] NO XPO1 LOCALISATION MEASUREMENT OF ANY KIND HAS BEEN MADE IN A KMT2A-REARRANGED CELL. No XPO1 or CRM1 ChIP, no fractionation, no imaging, in any KMT2A-rearranged line, xenograft or patient sample - the chromatin work is in LOUCY (SET::NUP214 T-ALL), MEGAL, HEL and mouse embryonic stem cells. UNPUBLISHED RATHER THAN NOT-APPLICABLE, and it is the single measurement that would decide whether the export axis is a real feature of this disease. The experiment is already written up as exp-xpo1-chip-in-kmt2a-rearranged-with-menin-inhibitor. |
| epigenetic readout | INDIRECT, AND THE HONEST ANSWER IS THAT NOBODY HAS MEASURED A MARK. XPO1 writes, erases and reads no histone or DNA modification: it is a karyopherin-beta HEAT-repeat superhelix with Cys528 in the NES-binding groove, and it has no SET, JmjC, HAT, HDAC, bromo, chromo, PHD or CXXC module. Its epigenetic relevance runs entirely through position and through pharmacology. (1) POSITION: a fraction of XPO1 is detectable ON CHROMATIN at active regulatory regions including the HOX clusters and the MEIS1 locus, behaving as a pre-bound platform that genetically diverse leukaemia drivers dock onto - already this entry's E2/E3 - BUT this entry also carries a 2026-09-21 correction (E_q72_xpo1_loc2) that the chromatin pool may be a GENERAL CO-ACTIVATOR POSITION rather than a leukaemia-specific address, so 'XPO1 sits at HOXA' must not be quoted as a fusion-specific fact. (2) THE MARK IS UNMEASURED, AND THE ABSENCE IS COUNTED: this graph's exp-locus-resolved-h3k79me2-under-xpo1-inhibition records that XPO1-inhibitor terms combined with H3K79 terms return 0 records on PubMed against operands of 829 and 654, with a positive control through the identical shape returning 3 - bounded by titles and abstracts, supporting figures not searched. NOTE THE QUERY FORM: that absence is written in the grouped (A OR B) shape, which per rule 94 expands to [All Fields] and is therefore BROADER than labelled, so the zero is CONSERVATIVE and the absence is stronger than stated, not weaker. (3) THE ONLY PUBLISHED XPO1-EPIGENETICS INTERSECTION IS DRUG SYNERGY, NOT MECHANISM: the p300/CBP acetyltransferase inhibitor A485 synergises with the XPO1 inhibitor KPT-8602 in multiple myeloma and, via EP300, in diffuse large B-cell lymphoma; selinexor assists vorinostat in tongue squamous carcinoma; and nuclear-to-cytoplasmic transport is a druggable dependency in HDAC7-driven small-cell lung cancer. NONE of these is in KMT2A-rearranged leukaemia and NONE reports a histone-mark readout, so they establish a combination opportunity and no mechanism. WHAT WOULD CLOSE IT: the experiment is already designed in this graph and has never been run - a spike-in-normalised, locus-resolved H3K79me2 ChIP or CUT&RUN under selinexor, which in CALM-AF10 would also discriminate the export model from the docking model because the two predict OPPOSITE directions for the focal HOXA peak. CAUSE OR CONSEQUENCE: unanswerable, because no mark has been measured under any XPO1 perturbation. |
PDB IDS
[ "1W9C", "3GB8", "4BSM", "4BSN", "5DIS", "6TVO", "7B51", "8URJ" ]
domains — the numbers behind the chart
[
{
"name": "Importin N-terminal (IBN_N)",
"start": 46,
"end": 112
},
{
"name": "HEAT 1",
"start": 217,
"end": 240
},
{
"name": "HEAT 2",
"start": 241,
"end": 277
},
{
"name": "HEAT 3",
"start": 354,
"end": 472
},
{
"name": "HEAT 4",
"start": 515,
"end": 553
},
{
"name": "HEAT 5",
"start": 560,
"end": 597
},
{
"name": "HEAT 6",
"start": 602,
"end": 639
},
{
"name": "HEAT 7",
"start": 775,
"end": 813
},
{
"name": "HEAT 8",
"start": 885,
"end": 916
},
{
"name": "HEAT 9",
"start": 917,
"end": 954
},
{
"name": "HEAT 10",
"start": 1002,
"end": 1039
}
]key residues
{
"Cys528": "covalent target of leptomycin B and the SINE compounds (selinexor, eltanexor); lies in the NES-binding groove; verified as cysteine in the fetched O14980 sequence",
"Glu571": "recurrent somatic hot spot in CLL, PMBL and classical Hodgkin lymphoma; in the NES-binding groove; verified as glutamate in the fetched sequence"
}uniprot regions
{
"Ran interaction and export-complex formation": "327-450",
"RANBP3 interaction": "411-481",
"HIV-1 Rev interaction": "800-820"
}subcellular location uniprot
[ "Cytoplasm", "Nucleus, nucleoplasm", "Nucleus, Cajal body", "Nucleus, nucleolus" ]
essentiality
{
"depmap_common_essential": true,
"chronos_mean_all_lines": -2.1422,
"chronos_mean_kmt2a_rearranged": -2.332,
"chronos_mean_other_leukemia": -2.2623,
"kmt2a_selectivity_difference": -0.0697,
"kmt2a_selectivity_rank": "2228 of 17728",
"floor_compression_warning": "pan-essentiality of -2.14 leaves almost no dynamic range; the near-zero selectivity difference is uninterpretable rather than a measured null"
}cell type
{
"expressed_in": "Ubiquitous. No cell type in which XPO1 is absent has been reported, and the graph records none.",
"required_in": "Every cell type tested, and that is the point. DepMap Chronos mean -2.142 across 1,208 lines; in this project's own scan the KMT2A-rearranged arm is -2.332 against -2.263 in 43 other leukaemia lines, difference -0.070, rank 2,228 of 17,728. The gene sits on the essentiality floor, so the small difference is uninterpretable rather than small and NO selectivity claim is supportable from it.",
"required_in_fusion_context": "In KMT2A-rearranged AML, ziftomenib plus selinexor suppressed colony formation of primary CD34-positive KMT2A-rearranged progenitors WITHOUT affecting normal stem cells, and improved survival in MV4;11 and patient-derived KMT2A-rearranged xenografts. This is a combination result in a preprint, not a monotherapy dependency.",
"off_target_cell_type": "Human erythroid progenitors. In cells from patients with severe beta-0-thalassaemia/HbE, XPO1 inhibition by selinexor was the most effective of nine XPO1 inhibitors at ENHANCING terminal erythroid maturation, through nuclear retention of HSP70 and stabilisation of GATA1. The lineage consequence of inhibiting XPO1 therefore runs in OPPOSITE directions in two haematopoietic cell types - maturation in erythroid cells, loss of the leukaemic programme in blasts.",
"nodes": [
"cell-type-hsc-bone-marrow"
],
"not_written": "No erythroid-progenitor node exists in this graph (cell-type-mep is the upstream bipotent progenitor and is not the cell measured here), so the erythroid result is recorded in this field and in E-XPO1-erythroid but carries no edge."
}cell state
{
"maintains_state": "Contributes to holding the differentiation block, on combination evidence only. Ziftomenib plus selinexor downregulated HOXA9 and MEIS1 and UPREGULATED the monocytic differentiation marker CD11b in both KMT2A-rearranged and NPM1-mutant AML, with robust apoptosis and a decreased G2/M population.",
"how_shown": "cell-line combination pharmacology, colony assays on primary CD34-positive cells, RNA-seq and proteomics, and MV4;11 / OCI-AML3 / PDX models in NSG mice (preprint)",
"attribution_limit": "The CD11b rise is reported for the COMBINATION. Nothing in the source separates the XPO1 contribution from the menin-inhibitor contribution to the differentiation readout, and menin inhibition alone is already established in this graph to drive differentiation in AML. The XPO1-alone share of this state effect is not measured.",
"nodes": [
"cell-state-differentiation-block"
]
}localization
{
"subcellular": "CYTOPLASM AND NUCLEUS, shuttling - UniProt O14980 gives 'Cytoplasm', 'Nucleus, nucleoplasm', 'Nucleus, Cajal body' and 'Nucleus, nucleolus', and NONE OF THE FOUR CARRIES AN EVIDENCE CODE [E_q72_xpo1_loc1]. Nobody doubts that XPO1 shuttles; the point is that a reader who treats these as attributed annotations is mistaken, and that CHROMATIN - the pool this graph's export-axis argument rests on - is not among them.",
"subnuclear": "NUCLEOPLASM, CAJAL BODIES AND NUCLEOLI per UniProt, all uncoded [E_q72_xpo1_loc1]; plus a CHROMATIN-BOUND pool at HOXA and HOXB cluster regions measured by ChIP-seq with two independent anti-CRM1 antibodies in the human T-ALL line LOUCY, where CRM1 is upstream of SET-Nup214 rather than recruited by it [E_q72_xpo1_loc2 counter-note]. The chromatin pool and the shuttling pool have NEVER been separated as biochemical species - see localization-xpo1-chromatin-bound-versus-soluble-pool, which is the entry that carries this properly.",
"do_not_strengthen": "THE CHROMATIN POOL MAY NOT BE SPECIAL. XPO1 and p300 co-occupy HUNDREDS of chromatin loci in a non-leukaemic system, and degrading XPO1 diminishes the occupancy of both [E_q72_xpo1_loc2]. That is compatible with chromatin-bound XPO1 being a general feature of active chromatin, of which the HOX-cluster signal is one instance. This graph has already challenged the export-axis hypothesis on exactly this ground (ana-xpo1-chromatin-measurements-never-made, hyp-xpo1-is-a-shared-address-for-hoxa-driven-leukaemia) and this localisation record must not be read as new support for it.",
"explicit_no": "NO XPO1 LOCALISATION MEASUREMENT OF ANY KIND HAS BEEN MADE IN A KMT2A-REARRANGED CELL. No XPO1 or CRM1 ChIP, no fractionation, no imaging, in any KMT2A-rearranged line, xenograft or patient sample - the chromatin work is in LOUCY (SET::NUP214 T-ALL), MEGAL, HEL and mouse embryonic stem cells. UNPUBLISHED RATHER THAN NOT-APPLICABLE, and it is the single measurement that would decide whether the export axis is a real feature of this disease. The experiment is already written up as exp-xpo1-chip-in-kmt2a-rearranged-with-menin-inhibitor.",
"how_shown": "UniProtKB O14980 fetched 2026-09-21 and read comment-by-comment for evidence codes; ChIP-seq with two independent anti-CRM1 antibodies plus SET-Nup214 knockdown in LOUCY (PMID 31755865); XPO1 and p300 ChIP after C646- or S109-induced XPO1 degradation, with the XPO1 C528S resistance allele as the specificity control (PMID 38917791).",
"systems": "LOUCY human T-ALL (SET::NUP214), MEGAL, HEL, mouse embryonic stem cells, and non-leukaemic lines for the p300 co-occupancy work. NO KMT2A-REARRANGED SYSTEM.",
"shown_for_fusion_localisation": "NAME WHICH, and none of them is the index fusion. XPO1's chromatin localisation has been shown in the context of SET::NUP214 (LOUCY T-ALL, ChIP-seq, two antibodies) and in NPM1c AML (reported co-partitioning with KMT2A and menin in NPM1c C-bodies, imaging, abstract-level). For ANY KMT2A REARRANGEMENT the answer is NO, and in those words: nobody has looked in any KMT2A fusion. The only KMT2A-rearranged XPO1 evidence in this graph is a 2026 preprint combination study in MV4;11 that measures growth, occupancy of menin and survival - not XPO1's own localisation.",
"node": "localization-xpo1-chromatin-bound-versus-soluble-pool"
}epigenetic bounded absence
{
"claim": "No histone mark has ever been measured under XPO1 inhibition, in this disease or on this search, and no epigenetic activity is attributed to XPO1.",
"date_measured": "2026-09-21 (this tranche), re-stating a bound first recorded in exp-locus-resolved-h3k79me2-under-xpo1-inhibition",
"tool": "NCBI esearch db=pubmed (eutils), querytranslation read back from each response",
"queries": [
{
"query": "XPO1[tiab] AND histone[tiab]",
"querytranslation": "\"XPO1\"[Title/Abstract] AND \"histone\"[Title/Abstract]",
"count": 24,
"title_checked": "the first eleven were title-checked: two A485/XPO1-inhibitor synergy papers (myeloma, DLBCL), an HDAC7-driven SCLC transport dependency, a selinexor/vorinostat combination in tongue SCC, two cutaneous-toxicity reviews, two spheroid combination screens, a KPT-8602/dexamethasone ALL paper, an autophagy paper and a cyclin D1 review. NONE reports XPO1 writing, erasing or reading a mark, and NONE reports a histone-mark readout under XPO1 inhibition."
},
{
"query": "selinexor[tiab] AND epigenetic[tiab]",
"querytranslation": "\"selinexor\"[Title/Abstract] AND \"epigenetic\"[Title/Abstract]",
"count": 13,
"role": "operand check on the drug side - the instrument returns plenty, so the absence of a mark measurement is not a retrieval failure"
},
{
"query": "XPO1[tiab] AND chromatin[tiab]",
"querytranslation": "\"XPO1\"[Title/Abstract] AND \"chromatin\"[Title/Abstract]",
"count": 23,
"role": "the POSITION literature, which exists and is already cited on this entry (E2, E3, E_q72_xpo1_loc2); occupancy is not a mark"
}
],
"prior_bound_in_this_graph": {
"entry": "exp-locus-resolved-h3k79me2-under-xpo1-inhibition",
"query_as_recorded": "(selinexor OR \"XPO1 inhibitor\" OR \"XPO1 inhibition\" OR eltanexor OR KPT-330) AND (H3K79 OR \"H3-K79\" OR \"lysine 79\")",
"count": 0,
"operands": "829 and 654; positive control through the identical shape returns 3",
"rule_94_note": "That query uses the grouped (A OR B) form, which PubMed expands to [All Fields] rather than [Title/Abstract]. Per rule 94 the executed search is therefore BROADER than the one written, which makes a ZERO conservative: the absence is STRONGER than claimed, not weaker. No re-run is needed for this direction of error."
},
"absence_class": "never-measured",
"absence_class_basis": "Bounded by titles and abstracts only; supporting figures not searched (rule 80), and the prior entry explicitly names two papers (PMID 23487024, PMID 32733011) that should be opened in full text before the absence is treated as final. Classed never-measured rather than measured-not-analysed because no deposited dataset pairing an XPO1 inhibitor with a histone-mark assay was identified - no archive query was run in this tranche, which is itself a limit on the class assignment.",
"what_would_close_it": "exp-locus-resolved-h3k79me2-under-xpo1-inhibition, already designed in this graph: spike-in-normalised H3K79me2 ChIP-seq or CUT&RUN under selinexor or leptomycin B at a displacement-not-degradation exposure, reported as both the HOXA profile and the global level, with fusion and DOT1L occupancy and an NES-mutant control. Running it in a KMT2A-rearranged line as well as in CALM-AF10 would answer both the model-discrimination question and the plain one."
}- XPO1 is common-essential at a DepMap mean of -2.14 across 1,208 lines. There is no therapeutic index available from the target's biology; any window has to come from schedule and from the tumour's greater reliance, not from selectivity.
- XPO1 exports many tumour suppressors as well as oncogenic cargo, so inhibition is simultaneously pro- and anti-leukaemic in ways that are cargo-specific and not predictable from the target.
- If the chromatin-bound pool is the therapeutically relevant one, every existing XPO1 inhibitor engages it only incidentally - they were designed and optimised against the export function, and no assay in clinical use reads out chromatin occupancy.
- ESSENTIAL-FUNCTION TOXICITY — XPO1 is pan-essential with a Chronos mean of -2.142 across 1,208 lines and is depleted in 99 percent of them, so there is no therapeutic window from selectivity - the window has to come from dose and schedule. The erythroid finding adds a specific, testable on-target effect in a second haematopoietic lineage, and in an infant already anaemic from marrow replacement the direction of that effect is not obvious a priori.
- Pairing an XPO1 inhibitor with an epigenetic agent is currently justified by synergy screens in unrelated malignancies and by no mark measurement anywhere. That is exactly the configuration in which a combination advances on a plausible story and fails for a reason nobody looked for: if XPO1's chromatin pool is a general co-activator position, the synergy is additive requirement rather than mechanistic cooperation, and the combination will carry both drugs' toxicities - including the erythroid-progenitor cost this entry already records - without the supra-additive benefit the rationale promises.
- What puts XPO1 on chromatin in the first place? Every paper in this literature starts from the fact that it is already there, and nothing identifies the tether, the sequence feature or the modification that recruits it.
- Is the chromatin-bound pool a distinct biochemical species - a different conformation, a different post-translational state, cargo-free versus cargo-loaded - or just the same molecules in transient contact? Nobody has separated the two pools biochemically.
- Does a SINE compound acting at Cys528 in the NES groove affect chromatin-bound XPO1 through the same chemistry as it affects export, or does it work here by degrading XPO1 and its docked partners? The published KPT-330 experiments confound the two.
- The MEIS1 locus is named alongside HOX in the 2026 perspective but this graph has no XPO1 occupancy data at MEIS1 in any KMT2A-rearranged system. Is MEIS1 a second shared address?
- Does XPO1 inhibition alone, without a menin inhibitor, move any differentiation marker in a KMT2A-rearranged cell? Every cell-state readout on record is from the combination, and the single-agent arm is the cheapest missing experiment in this entry.
- Selinexor enhances terminal erythroid maturation in thalassaemic progenitors and is credited with promoting monocytic differentiation in AML. Are these one mechanism read in two lineages, or two? Measuring nuclear HSP70 and GATA1 in a KMT2A-rearranged blast under selinexor would separate them.
- Is chromatin-bound XPO1 in a leukaemia cell locus-restricted to HOX, or is it the same broad p300-co-occupied pool reported in PMID 38917791? One XPO1 CUT&RUN with a p300 track in the same cells answers it, and no published experiment distinguishes the two.
- Is chromatin-bound XPO1 a general property of active chromatin or a leukaemia-specific address? The p300 co-occupancy result (PMID 38917791) makes the general reading live, and the discriminating experiment is an XPO1 ChIP in a KMT2A-rearranged cell compared against a non-leukaemic line of the same lineage - not against a different disease.
- Does XPO1 inhibition move any histone mark at KMT2A-fusion target loci? This graph records ziftomenib/selinexor synergy in KMT2A-rearranged AML and a chromatin-bound XPO1 pool at HOX and MEIS1, and it has no chromatin pharmacodynamic endpoint for that combination. The designed experiment exists; only the KMT2A-rearranged arm is missing from it.
- Is the repeated A485/XPO1-inhibitor synergy - now reported in multiple myeloma and in DLBCL - a shared mechanism at chromatin or just two independently required genes? The discriminating measurement is histone acetylation at XPO1-occupied regulatory elements under each agent alone and in combination, and it has not been made in any of the three reports.
- If chromatin-bound XPO1 is a general co-activator position rather than a specific address, does it have a MARK signature? XPO1 occupancy is reported at 'active regulatory regions', which is a category defined by marks nobody has measured alongside XPO1 in the same cells. Co-profiling XPO1 with H3K27ac and H3K4me1 would say whether the pool tracks enhancers, promoters or neither, and would settle this entry's own specificity correction.
- E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database
XPO1 mediates nuclear export of cargoes bearing a leucine-rich NES, binding cooperatively to the NES and to RAN-GTP in the nucleus with RANBP3, docking at the nuclear pore through nucleoporin contacts, and releasing cargo in the cytoplasm when RANBP1 and RANGAP1 drive Ran-GTP hydrolysis; the reviewed human record is O14980, primary gene name XPO1, 1,071 aa, with HEAT repeats annotated from residue 217 to 1,039 and a Ran-interaction region at 327-450.
UniProtKB - O14980 (XPO1_HUMAN), Exportin-1 · UniProt Consortium · UniProtKB 2026What this evidence cannot show
Database record fetched live on 2026-09-20 via the UniProt REST API with gene_primary and length requested, per brief rules 62-65. The FUNCTION text is a curated synthesis of several primary papers (the record cites PMIDs 9311922, 9323133, 15574332, 20921223), not a single measurement. Residues 528 (Cys) and 571 (Glu) were read directly off the fetched sequence rather than from recall.
Evidence that argues against this (1)
- PUBLISHED CONFLICTING RESULT against the completeness of the reviewed record. UniProt's FUNCTION and subcellular-location text for O14980 carries no chromatin term, but Chen et al. demonstrate that XPO1 directly binds chromatin, co-occupies hundreds of loci with p300, and that degrading XPO1 diminishes p300 chromatin occupancy and phenocopies p300 inhibition. The curated record is not wrong; it is incomplete in exactly the direction this beat depends on, and an entry whose load-bearing first evidence item is the reference annotation will systematically understate the chromatin pool. Chen YF et al. 2024
- E2moderate confidence 3 of 5: One strong study, or several smaller consistent ones.review
XPO1/CRM1 is detectable on chromatin at active regulatory regions including the HOX clusters and the MEIS1 locus, and a 'pre-bound XPO1 platform' model holds that nucleoporin (NUP98/NUP214) fusions and mutant NPM1 are recruited to these loci through FG-repeat-XPO1 or NES-XPO1 interactions coupled with partner-encoded chromatin contacts, potentially lowering the threshold for LLPS-linked condensate formation.
Beyond nuclear export: chromatin-bound XPO1/CRM1 as a transcriptional scaffold. · Oka M · International Journal of Hematology 2026What this evidence cannot show
A PERSPECTIVE/REVIEW by the author of the primary chromatin-bound CRM1 papers, so it is a map of his own position rather than independent corroboration. Cited here for the framing and for the MEIS1 locus, which this graph had not recorded; every underlying measurement is cited to its own primary source elsewhere in this beat. The LLPS-threshold claim is a proposal, not a measurement, and this graph's standing caveat on phase-separation assays applies. Abstract-level reading only.
Evidence that argues against this (1)
- PUBLISHED CONFLICTING RESULT, and it is the strongest available objection to the 'pre-bound XPO1 platform' model as an ADDRESS. Measured by an independent group with an independent chemical tool, chromatin-bound XPO1 is not locus-restricted: XPO1 and p300 co-occupy HUNDREDS of chromatin loci, and degrading XPO1 with C646 or S109 reduces the chromatin occupancy of both, which is why an XPO1 degrader phenocopies a p300 inhibitor. A factor sitting at hundreds of p300-marked active loci is a general chromatin cofactor, not a postal address that distinguishes one set of lesions from another. Finding XPO1 at HOXA in a HOX-driven leukaemia line is then the expected observation, and the specificity has to come from the lesion's own chromatin contacts rather than from XPO1. Chen YF et al. 2024
- E3strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper
In the human T-ALL line LOUCY, ChIP-seq shows CRM1 selectively bound at HOXA and especially HOXB cluster regions; knocking down SET-Nup214 down-regulates HOX genes without significantly reducing chromatin-bound CRM1, indicating CRM1 is the recruiter rather than the cargo; and the same chromatin-bound CRM1 recruits NPM1c via its NES.
Chromatin-bound CRM1 recruits SET-Nup214 and NPM1c onto HOX clusters causing aberrant HOX expression in leukemia cells. · Oka M, Mura S, Otani M, et al. · eLife 2019What this evidence cannot show
Human leukaemia CELL LINES only (LOUCY, MEGAL, with K562/HL60/HEL as comparators); no patient sample and nothing in infant B-lineage KMT2A::AFF1. The recruiter conclusion rests on a knockdown, which leaves residual protein. Recorded in full in `mechanism-set-nup214-crm1-is-the-address-not-the-fusion`; cited here only for the chromatin-bound pool's existence and ordering.
Evidence that argues against this (1)
- The same paper reports KPT-330-sensitive CRM1 signals at HOX regions in HEL cells, which do NOT carry SET-Nup214, and states the biological significance is undetermined. Chromatin-bound XPO1 at HOX is therefore not by itself a fusion-specific event. Oka M et al. 2019
- E4strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper
Recurrent XPO1 hot-spot mutations, predominantly E571K or E571G, disrupt conserved biophysical interactions in the NES-binding groove and confer novel cargo-binding abilities; crystal structures of wild-type and E571K XPO1 bound to KPT-185, selinexor (KPT-330) and eltanexor (KPT-8602) are highly similar, indicating SINE activity is not affected by E571 mutations.
Recurrent XPO1 mutations alter pathogenesis of chronic lymphocytic leukemia. · Walker JS, Hing ZA, Harrington B, et al. · Journal of Hematology & Oncology 2021What this evidence cannot show
CLL, not the leukaemia this graph is about, and abstract-level for this beat. Cited here for the structural localisation of the drug-binding cysteine and the hot-spot residue; the disease claims are held in `mechanism-xpo1-e571k-hotspot-change-of-function`. The SINE-binding structures argue that E571 mutation does not cause SINE resistance and say nothing about acquired C528S.
Evidence that argues against this (1)
- PUBLISHED CONFLICTING RESULT on the conclusion drawn from the structures. The structures show that E571 mutation does not alter SINE binding; they say nothing about whether SINE resistance is achievable, and it demonstrably is - at the residue two helices away. Neggers et al. engineered C528S into multiple leukaemia cell lines with CRISPR/Cas9 and found that a single HETEROZYGOUS substitution confers resistance to selinexor as effectively as a homozygous one, i.e. the resistance is dominant and one allele of one codon is sufficient. 'SINE activity is not affected by E571 mutations' is true and is routinely read as 'the SINE class has no target-site resistance liability', which this paper refutes. Neggers JE et al. 2016
- E5strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.dataset
In a genome-wide DepMap scan over 17,728 protein-coding genes comparing 11 Cellosaurus-annotated KMT2A-rearranged leukaemia lines with 43 other leukaemia lines, XPO1 has a mean gene effect of -2.332 in the rearranged arm and -2.263 in the comparator, a difference of only -0.070, ranking 2,228 of 17,728; its pan-essentiality across 1,208 lines is -2.142.
DepMap KMT2A-selective dependency scan (full genome), analyses/depmap-kmt2a-selective-scan-full · Oncofusion Knowledge Graph project · internal analysis over DepMap CRISPR gene effect 2026What this evidence cannot show
This graph's own scan, generated 2026-09-19, read directly from analyses/depmap-kmt2a-selective-scan-full/results.json on 2026-09-20. Standing DepMap caveats apply and one bites hard: XPO1 sits at a pan-essentiality of -2.14, deep in the FLOOR-COMPRESSION regime the brief names, where almost no dynamic range remains for selectivity to appear. So the near-zero difference is UNINTERPRETABLE rather than a demonstrated absence of selectivity. The 11 KMT2A-rearranged lines are myeloid-enriched and none is infant-derived, and the DepMap release version is not stated by the API.
Evidence that argues against this (1)
- AUTHORS' OWN STATED LIMITATION of the instrument that produced -2.332 and -2.142. The Chronos authors open by stating that CRISPR loss-of-function screens 'exhibit a number of biases and artifacts that can confound the results', and Chronos is explicitly an inference of fitness effects from an explicit model of CELL PROLIFERATION DYNAMICS after knockout. A gene effect of -2.3 is therefore a statement about how fast a population stops expanding over the screen, not about how much XPO1 activity a cell requires, and it carries no information at all about differentiation, quiescence or drug-conditional phenotypes. The floor-compression caveat in this item is correct; the deeper point is that the quantity being compressed is proliferation rate. Dempster JM et al. 2021
- E6moderate confidence 3 of 5: One strong study, or several smaller consistent ones.preprint
In KMT2A-rearranged and NPM1-mutant AML, the menin inhibitor ziftomenib combined with the XPO1 inhibitor selinexor synergistically inhibited growth of multiple cell lines, suppressed colony formation of primary CD34-positive KMT2A-rearranged progenitor cells without affecting normal stem cells, downregulated HOXA9 and MEIS1 while upregulating the monocytic differentiation marker CD11b, and improved survival in MV4;11, OCI-AML3 and patient-derived xenograft models; mechanistically XPO1 stabilises menin's binding to chromatin and its interactions with KMT2A and KMT2A/MLLT3.
Combined Menin and XPO1 inhibition drive synergistic antileukemic activity in KMT2Ar and NPM1-m AML. · Uddin MH, Dhiman S, Han Y, Aboukameel A, Dhillon V, Aguillar J, Buck S, Deol A, Boerner JL, Polin L, Kessler L, Burrows F, Yang J, Azmi AS, Maciejewski JP, Cutler J, Du Y, Balasubramanian SK · bioRxiv 2026What this evidence cannot show
A bioRxiv PREPRINT, not peer reviewed, and the graph should not upgrade this until it is. AML only - MV4;11 is KMT2A::MLLT3 and OCI-AML3 is NPM1-mutant; there is no B-lineage and no KMT2A::AFF1 arm. Every cell-state readout, including the CD11b differentiation marker, is reported for the drug COMBINATION, so the XPO1-alone contribution to the state change is not measured. Read: abstract only.
Evidence that argues against this (1)
- A CRISPR viability screen finds no KMT2A-selective requirement for XPO1 at all. In this project's own genome-scale scan XPO1 is -2.332 in the 11 KMT2A-rearranged lines against -2.263 in 43 other leukaemia lines, a difference of -0.070 at rank 2,228 of 17,728, on a gene whose pan-line Chronos mean is -2.142. That is floor compression: with almost no dynamic range left, the difference is uninterpretable rather than small, and it means 'XPO1 is required in KMT2A-rearranged cells' is a statement about all cells. Oncofusion knowledge graph, analyses/depmap-kmt2a-selective-scan-full; DepMap Chronos via Open Targets; 11 KMT2A-rearranged versus 43 other leukaemia lines, 17,728 genes 2026
- E7strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper
Inhibiting XPO1 in a non-leukaemic haematopoietic cell type produces the opposite kind of effect: in erythroid progenitors from patients with severe beta-0-thalassaemia/HbE, selinexor was the most effective of nine XPO1 inhibitors at ENHANCING terminal erythroid maturation, associated with nuclear retention of HSP70, stabilisation of GATA1 and a dose-dependent increase in cytoplasmic HSP70.
Inhibition of XPO1 by selinexor enhances terminal erythroid maturation through modulation of HSP70 trafficking in severe β0-thalassemia/HbE. · Khamphikham P, Tantiworawit A, Anuchapreeda S · PLoS One 2025What this evidence cannot show
Primary erythroid progenitors from nine patients with a haemoglobinopathy, not from healthy donors and not from leukaemia. The cell type is a cultured erythroid progenitor undergoing terminal maturation and the graph has no node for it. This establishes a lineage-specific consequence of XPO1 inhibition; it says nothing about XPO1 in a KMT2A-rearranged blast. Read: abstract only.
Evidence that argues against this (1)
- The same drug class in the AML setting is credited with pushing blasts toward monocytic differentiation, so 'selinexor promotes maturation' is being asserted in two lineages with two different mechanisms and, in the AML case, only as part of a combination. A shared word - maturation - across an erythroid HSP70/GATA1 mechanism and a myeloid HOXA9/MEIS1 mechanism is not shared biology. Uddin MH et al. 2026
- E_q72_xpo1_loc1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database
NONE OF XPO1'S FOUR UNIPROT LOCATIONS CARRIES ANY EVIDENCE CODE. Fetched from UniProtKB 2026-09-21, O14980 (XPO1_HUMAN, primary gene XPO1, 1,071 aa) lists 'Cytoplasm', 'Nucleus, nucleoplasm', 'Nucleus, Cajal body' and 'Nucleus, nucleolus', and the SUBCELLULAR LOCATION comment carries a free-text note - 'Located in the nucleoplasm, Cajal bodies and nucleoli. Shuttles between the nucleus/nucleolus and the cytoplasm'. EVERY ONE OF THOSE FIVE STRINGS IS UNCODED: no ECO:0000269, no ECO:0000305, no ECO:0000250, nothing. XPO1 sits in the 10.7% of this graph's accession-carrying gene entries whose UniProt locations have no evidence code at all.
UniProtKB entry O14980 (XPO1_HUMAN), SUBCELLULAR LOCATION comment read with evidence codes · UniProt Consortium · UniProtKB 2026What this evidence cannot show
A database state on a date, and an UNCODED annotation IS NOT A WRONG ANNOTATION - XPO1 shuttling is among the best-established facts in cell biology, and the absence of a code here reflects curation history for a long-standing entry, not doubt. What it does mean is narrow and worth carrying: this entry's existing data.subcellular_location_uniprot field lists those four strings, and a reader is entitled to assume a UniProt location is attributed. It is not. Anyone building on the Cajal-body or nucleolar value in particular should find and cite the primary observation, because the database will not hand it to them. See ana-uniprot-localization-is-not-a-measurement-in-a-quarter-of-this-graph.
Evidence that argues against this (1)
- The compartment that matters for this graph is not in that list at all. XPO1's leukaemia-relevant pool is CHROMATIN-BOUND, and chromatin is not among UniProt's four values - so the database is simultaneously unattributed on what it does say and silent on the thing the export-axis hypothesis rests on. localization-xpo1-chromatin-bound-versus-soluble-pool records that the two pools have never been separated as biochemical species. Oka M et al. 2019
- E_q72_xpo1_loc2moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper
CHROMATIN-BOUND XPO1 MAY BE A GENERAL CO-ACTIVATOR POSITION RATHER THAN A LEUKAEMIA-SPECIFIC ADDRESS, AND THIS GRAPH SHOULD NOT QUIETLY STRENGTHEN THE OPPOSITE. In a non-leukaemic chemical-genetics study, the compound C646 - long used as a p300 inhibitor - was shown to DEGRADE XPO1, with its cellular phenotypes abrogated in cells carrying the XPO1 C528S drug-resistance allele; and P300 AND XPO1 CO-OCCUPY HUNDREDS OF CHROMATIN LOCI, with degradation of XPO1 by C646 or by the modulator S109 diminishing the chromatin occupancy of BOTH. Direct XPO1 degradation phenocopies p300 inhibition.
C646 degrades Exportin-1 to modulate p300 chromatin occupancy and function. · Chen YF, Rahman A, Sax JL, Atala Pleshinger MJ, Friedrich RM, Adams DJ · Cell Chem Biol 2024What this evidence cannot show
Abstract read in full; full text not read. NOT A LEUKAEMIA SYSTEM and no KMT2A fusion anywhere in it (brief rule 73). Already cited 7 times in this graph, including in this entry's own E1/E2 and in ana-xpo1-chromatin-measurements-never-made and hyp-xpo1-is-a-shared-address-for-hoxa-driven-leukaemia - rule 82 applies and this item is recorded as a LOCALISATION caveat, not as a new finding. THE POINT IS DEFLATIONARY: a chromatin-bound XPO1 that co-occupies hundreds of loci with p300 is compatible with XPO1 being a general component of active chromatin, in which case the HOX-cluster occupancy reported in leukaemia lines is an instance of a general property rather than a fusion-specific address. The co-occupancy is a crosslinked-ChIP result and reports proximity, not residence, and losing both signals after degrading one protein does not establish that one recruits the other.
Evidence that argues against this (1)
- The directional experiment in leukaemia points the other way and is the strongest argument that the chromatin pool is not merely decorative: in the human T-ALL line LOUCY, ChIP-seq with two independent anti-CRM1 antibodies finds CRM1 selectively at HOXA and especially HOXB cluster regions, and knocking down SET-Nup214 down-regulates HOX genes WITHOUT significantly reducing chromatin-bound CRM1 - i.e. CRM1 is upstream, the recruiter rather than the cargo. That is a specific, locus-restricted, order-of-assembly result. It is also in a SET::NUP214 T-ALL line, not a KMT2A-rearranged cell, and no XPO1 ChIP has ever been done in a KMT2A-rearranged system. Oka M et al. 2019
- E8weak confidence 2 of 5: Preliminary, small, indirect, or not yet peer reviewed.paper
THE XPO1-EPIGENETICS INTERSECTION IS COMBINATION PHARMACOLOGY, NOT MECHANISM: the p300/CBP histone acetyltransferase inhibitor A485 and the XPO1 inhibitor KPT-8602 show synergistic antitumour activity in multiple myeloma.
Synergistic Antitumor Activity of HAT Inhibitor A485 and XPO1 Inhibitor KPT8602 in Multiple Myeloma. · Xu H, Wu W, Jiang Y, et al. · Cancer Med 2026What this evidence cannot show
Abstract-level read; full text not read in this tranche. MULTIPLE MYELOMA - a mature plasma-cell malignancy, not leukaemia, not KMT2A-rearranged and not paediatric, so rule 73 applies and nothing about the index disease follows. Marked WEAK because a synergy result establishes a drug interaction and no mechanism: no histone acetylation or any other mark is reported as a readout in the abstract, so the pairing of an acetyltransferase inhibitor with an export inhibitor is not evidence that XPO1 acts on acetylation. A485 is itself a tool-grade compound with its own selectivity questions. Not cited anywhere in this corpus before 2026-09-21, verified with scripts/check-citation-reuse.py.
Evidence that argues against this (1)
- The combination that actually matters for this project is a different one and is already in this entry, which is why the myeloma result is recorded at weak confidence rather than built on. In KMT2A-rearranged and NPM1-mutant AML, the menin inhibitor ziftomenib combined with the XPO1 inhibitor selinexor synergises - the right disease, the right lesion, and a mechanistic rationale through the chromatin-bound XPO1 pool. That combination also has no histone-mark readout, which is the actual gap: the epigenetic case for pairing XPO1 inhibition with anything in this disease rests on synergy screens in every instance, and on a mark measurement in none. Uddin MH et al. 2026
- E9weak confidence 2 of 5: Preliminary, small, indirect, or not yet peer reviewed.paper
The same acetyltransferase/export pairing is reported in a second B-lineage-adjacent malignancy: targeting EP300 with A485 in diffuse large B-cell lymphoma is efficacious and shows synergistic effects with XPO1 inhibition.
Targeting EP300 in diffuse large b-cell lymphoma: efficacy of A485 and synergistic effects with XPO1 inhibition. · Jiang Y, Xing D, He X, et al. · BMC Cancer 2025What this evidence cannot show
Abstract-level read; full text not read. DIFFUSE LARGE B-CELL LYMPHOMA - a mature B-cell malignancy, not precursor B-ALL and not KMT2A-rearranged. Recorded only because it is the second independent report of the A485/XPO1-inhibitor pairing and so raises the pairing above a single-paper observation; like the myeloma result it reports a growth and synergy readout and, at abstract level, no histone acetylation measurement, so it adds replication of a drug interaction and no mechanism. Not cited anywhere in this corpus before 2026-09-21.
Evidence that argues against this (1)
- The tempting mechanistic bridge - that chromatin-bound XPO1 cooperates with acetyltransferases at active regulatory elements, which would explain the synergy - is exactly the inference this entry's own correction warns against. Chromatin-bound XPO1 may be a GENERAL CO-ACTIVATOR POSITION rather than a leukaemia-specific or locus-specific address, and this graph explicitly declines to quote the HOXA/MEIS1 occupancy as a specific address. If XPO1 sits at active regulatory regions generally, then synergy with a p300/CBP inhibitor is expected wherever both are required and carries no information about a shared mechanism at any particular locus. Chen YF et al. 2024
- E10weak confidence 2 of 5: Preliminary, small, indirect, or not yet peer reviewed.paper
Third instance of the same shape, from the eraser side: nuclear-to-cytoplasmic transport is a druggable dependency in HDAC7-driven small-cell lung cancer, so an XPO1 dependency has been reported downstream of a class IIa histone deacetylase programme.
Nuclear to Cytoplasmic Transport Is a Druggable Dependency in HDAC7-driven Small Cell Lung Cancer. · Qin T, Wang J, Wang J, et al. · Adv Sci (Weinh) 2025What this evidence cannot show
Abstract-level read; full text not read. SMALL-CELL LUNG CANCER - a neuroendocrine epithelial tumour with no relationship to this disease, and the HDAC7 connection is a driver-programme context rather than a demonstrated XPO1-HDAC7 biochemical relationship. Already cited once in this corpus (gene-hdac7). Recorded here as the third member of a pattern - XPO1 inhibition intersecting acetylation machinery in three unrelated malignancies - and the pattern's honest reading is that XPO1 is broadly required and therefore synergises broadly, not that it has an acetylation mechanism.
Evidence that argues against this (1)
- A pattern of synergy across malignancies says nothing about the therapeutic window, and this entry already records the counterexample in the relevant tissue. Inhibiting XPO1 in a non-leukaemic haematopoietic cell type produces the opposite kind of effect in erythroid progenitors, which is the on-target cost that matters in an infant with a marrow disease. Three synergy reports in myeloma, DLBCL and small-cell lung cancer add nothing to that calculus, and none of them is in a haematopoietic progenitor. Khamphikham P et al. 2025
covalent SINE at Cys528 in the NES-binding groove
XPO1 docks on NUP214 FG repeats at the pore and in the fusion
chromatin-bound CRM1 is upstream of the fusion at HOX
chromatin-bound XPO1 at HOXA/HOXB clusters
the receptor behind the borrowed address
the receptor the CALM NES is recognised by
the pre-bound platform is XPO1 itself
the reported stabilising factor
which pool of the protein is which
NPM1c C-terminal NES binds XPO1
XPO1-dependent chromatin binding at FOXC1 and HOXA/HOXB
NES motifs created de novo by the duplication bind XPO1
a recurrent somatic hot spot in the NES-binding groove
1 of 739 sequenced B-ALL, 0 of 1,687 sequenced AML
covalent second-generation SINE at Cys528, dosed more frequently
the platform
- ← related toTwo reasons XPO1 is a hard target: every cell needs it, and blocking it switches on a survival pathway
DepMap mean gene effect -2.14 across 1,208 lines
- ← related toHow a lift operator became a postal address: the idea behind the XPO1 axis, in plain language
layman explainer for the protein
XPO1 mRNA rises when XPO1 protein is inhibited
XPO1 inhibition WITH a menin inhibitor raises CD11b and lowers HOXA9/MEIS1 in KMT2A-rearranged AML; combination evidence only, XPO1-alone contribution unmeasured, and the source is a preprint
ziftomenib plus selinexor suppressed colony formation of primary CD34-positive KMT2A-rearranged progenitors WITHOUT affecting normal stem cells - a sparing claim, not a requirement claim, from a preprint
the NES/clathrin-binding/oligomerisation claims all concern one CALM span and no experiment separates them; the fusion is nuclear in leukaemia cells
XPO1 and p300 co-occupy HUNDREDS of chromatin loci and an XPO1 degrader phenocopies p300 inhibition (PMID 38917791) - so chromatin-bound XPO1 is a general p300-associated cofactor, not a HOX-restricted postal address, and finding it at HOXA in a HOX-driven line discriminates nothing
the entry's title says the hot spot does not confer resistance to drugs binding the same groove - true of E571 and false of the groove: a single HETEROZYGOUS C528S is sufficient and dominant for SINE resistance (PMID 27634897), so 'XPO1-mutant' is at least two biomarkers pointing opposite ways
XPO1 protein is degraded by C646, a compound universally annotated to p300, via a neddylation-dependent molecular-glue mechanism (PMID 38917791) - so XPO1 levels and the feedback that follows them move under agents nobody attributes to XPO1, and the SELHEM children received fludarabine and cytarabine alongside selinexor with no comparator arm
the two XPO1 pools; UniProt annotates neither with an evidence code and omits chromatin
no XPO1 localisation measurement of any kind exists in a KMT2A-rearranged cell
the locus-restricted chromatin CRM1 signal is a SET::NUP214 T-ALL result, not a KMT2A one
XPO1 and p300 co-occupy hundreds of loci, so chromatin-bound XPO1 may be a general cofactor position
SMARCB1 has no bona fide NLS but a MASKED NES; C-terminal truncation unmasks it, exportin-1 exports the protein, and selinexor puts it back in the nucleus and kills rhabdoid cells (PMID 34003336) (Q91 2026-09-22)
DEK::NUP214 chromatin occupancy at FOXC1 and HOXA/HOXB by CUT&RUN is XPO1-DEPENDENT and is lost on XPO1 inhibition, alongside selective selinexor/eltanexor sensitivity in t(6;9) AML (PMID 40204893) (Q91 2026-09-22)
THE DESIGNED-AND-UNRUN EXPERIMENT THAT WOULD SUPPLY THIS ENTRY'S EPIGENETIC CONTENT: spike-in-normalised locus-resolved H3K79me2 under selinexor, which in CALM-AF10 discriminates the export from the docking model (opposite predictions for the focal HOXA peak) and in a KMT2A-rearranged line would answer whether blocking export moves a mark at all.
POSITION, NOT A MARK: chromatin-bound XPO1 is detectable at active regulatory regions including the HOX clusters and the MEIS1 locus. Qualified by this entry's own 2026-09-21 correction that the pool may be a general co-activator position rather than a specific address; no mark has been co-profiled with it.
- related to →Plain-English: chromatin and epigenetics — the sticky notes on the DNA, and which ones matter here
WRITES, ERASES AND READS NOTHING: a karyopherin-beta HEAT-repeat superhelix with Cys528 in the NES groove and no chromatin module. The only published XPO1-epigenetics intersection is combination synergy with acetylation-machinery agents in three unrelated malignancies, with no histone-mark readout in any of them.