Independent research-data planningEditorial and review policy
PHPeptide HarborResearch Data Harbor
Menu ▼
Peptide Harbor / Lab Notes

Nomenclature-control dossier

How should a CJC-1295 no-DAC or Modified GRF(1-29) record be controlled?

A conservative dossier for the non-DAC hGRF(1-29) analogue, focused on alias ambiguity, formula and mass anchors, terminal state, and evidence gaps.

Reviewed by Peptide Harbor editorial reviewUpdated 2026-08-03Educational research-data guidance

Answer first

The label CJC-1295 no DAC is commonly used for Modified GRF(1-29), but it should not inherit the chemical fields of the maleimido-modified CJC-1295 entity. This dossier uses a separate public compound record for formula and mass and requires every project to state the exact sequence and terminal form it intends to compare.

Reviewed Chemical LedgerCJC-1295 no DAC / Modified GRF(1-29)
Molecular form representedNon-DAC hGRF(1-29) analogue record represented by PubChem CID 132595997
Molecular formula
C152H252N44O42
Average molecular weight
3367.9 g/mol average molecular weight
Exact mass
3366.8969331 Da
Reviewed peptide designationModified GRF(1-29) reference form; exact project sequence and terminal state must be declared
Known Aliases / Code Names:CJC-1295 no DACModified GRF(1-29)Mod GRF 1-29

Field-level sources

PubChem CID 132595997

National Library of Medicine / PubChem · accessed 2026-08-03

Supports: formula, weight, exactMass

Modified GRF(1-29) terminology in a controlled research record

Endocrine Society / PubMed · accessed 2026-08-03

Supports: name, molecularForm, peptideDesignation, aliases

Where this framework helps

  • Separating no-DAC shorthand from the DAC compound record
  • Reviewing formula and expected-mass consistency
  • Flagging unresolved sequence or terminal-state nomenclature

Limits to keep visible

  • The selected public compound record does not provide a reviewed CAS synonym.
  • Market shorthand is not a substitute for a sequence-defined project specification.
  • The page excludes performance, administration, dosing, and procurement claims.
01

Do not borrow the DAC identifier

CAS 446262-90-4 and PubChem CID 91971820 describe the DAC-modified CJC-1295 entity. Applying those fields to a no-DAC record creates a false identity match.

02

Require a sequence-defined request

A project brief should include the intended Modified GRF(1-29) sequence, residue substitutions, and terminal amide or acid state. Formula and mass can only be interpreted against that same molecular form.

03

Expose what remains unresolved

This ledger deliberately omits a CAS field because the reviewed PubChem compound record does not supply one. A future source can be added only after the entity match is independently confirmed.

Primary and official sources

References used for this page

Visible FAQ

Questions research teams ask

Why is there no CAS number in this ledger?

The reviewed compound record supports formula and mass but does not expose a CAS synonym. Omitting the field is safer than importing a number from an unverified commercial alias.

Is no-DAC simply CJC-1295 with the side chain removed?

The shorthand suggests that relationship, but the project record should still define the exact sequence and terminal state rather than deriving an entity by subtraction.

Can this dossier share the DAC MolecularEntity schema?

No. It has its own name, molecular form, formula, mass, source, and URL so crawlers and researchers do not merge the two entities.