new lesson Jupiter DTF

[mu1titudes]

Written by JD SOL.

[tpompon]

📚 Lesson review — jupiter-dtf.mdx

Automated review by the Academy lesson agents. Read-only — nothing was changed. Reviewed commit 9993f44.

Summary: 🔴 1 blocker · 🟡 13 suggestions across 4 checks

Integrity (illustrations · video · links · frontmatter · glossary)

Verdict: ✅ PASS — 0 blockers, 4 suggestions

Sev	Where	Finding	Suggested fix
🟡	frontmatter badges	topic Product not in CONTRIBUTING.md's documented topics	update CONTRIBUTING.md or use a documented topic
🟡	lines 31, 65	smart contract not wrapped in <Term>	wrap with <Term id="smart-contract">
🟡	lines 32, 65, 75	liquidity pool not wrapped	wrap with <Term id="liquidity-pool">
🟡	lines 32, 75	liquidity not wrapped	wrap with <Term id="liquidity">

🔎 Accuracy vs docs.jup.ag

Verdict: ✅ PASS — 0 blockers, 1 to verify
Docs consulted: dtf overview / how-it-works / faq

Sev	Lesson says (line)	Docs say (source)	Action
🟡	HumidiFi $WET launch details — "sold out quickly … no unsold tokens", per-phase pricing (l.57-63)	not in DTF docs; third-party sources corroborate the 3-phase/Wetlist structure only	confirm sell-out and per-phase pricing with team

✍️ Quality (language · coherence)

Verdict: 1 blocker, 8 suggestions

Sev	Where	Finding	Suggested fix
🔴	line 23	"It leverages upon the features" — unidiomatic	"It leverages the features"
🟡	line 23	run-on; near-duplicate of lines 19/21	split or merge to avoid repetition
🟡	line 31	passive/wordy "promises that were made"; singular contract	"converts project promises into transparent, verifiable onchain contracts"
🟡	line 57	pronoun "they" has no clear antecedent	"HumidiFi … launched its $WET token via DTF"
🟡	line 65	long run-on listing three simultaneous events	convert to a bullet list
🟡	whole file	zero <Term> components	wrap TGE, vesting, liquidity pool
🟡	whole file	no images	add a DTF interface/phase-eligibility illustration
🟡	lines 80–88	"Participating" section is description, not a walkthrough	convert to numbered steps
🟡	line 23	"onchain" vs "on-chain" inconsistency across corpus	(this file is consistent; flag governance lesson)

Quiz (proposed)

Verdict: proposed 4-question quiz

• Q1 — the three buyer protections
• Q2 — what happens to unsold tokens at TGE
• Q3 — HumidiFi eligibility phases
• Q4 — vetting is not a guarantee

{
  "questions": [
    {
      "question": "Which three protocol-level protections does Jupiter DTF provide to buyers?",
      "options": [
        "Onchain allocation locking, immediate liquidity at TGE, and curated vetting",
        "Fixed token prices, guaranteed profits, and VC exclusion",
        "Anonymous launches, burn mechanisms, and airdrop distribution",
        "CEX listings, token buybacks, and community governance votes"
      ],
      "correctAnswer": 0,
      "explanation": "Jupiter DTF protects buyers through onchain lock-up of unsold tokens via Jupiter Lock, immediate liquidity provisioning on Meteora at TGE, and a rigorous pre-launch vetting process."
    },
    {
      "question": "What happens to unsold tokens at the Token Generation Event (TGE) in a Jupiter DTF launch?",
      "options": [
        "They are burned to reduce total supply",
        "They are airdropped to $JUP stakers",
        "They are locked onchain via Jupiter Lock under enforced vesting schedules",
        "They are returned to buyers as a refund"
      ],
      "correctAnswer": 2,
      "explanation": "Unsold tokens reserved for the project team are locked onchain via Jupiter Lock at TGE, turning project promises into a transparent, verifiable smart contract."
    },
    {
      "question": "In the HumidiFi $WET token launch example, which of the following was NOT one of the three eligibility phases?",
      "options": [
        "Whitelisted (Wetlist) participants",
        "$JUP stakers",
        "Jupiter team allocation",
        "Public access"
      ],
      "correctAnswer": 2,
      "explanation": "The HumidiFi launch used three phases — Wetlist, $JUP stakers, and public access — with no separate phase for a Jupiter team allocation."
    },
    {
      "question": "Which risk does Jupiter DTF explicitly acknowledge despite its vetting process?",
      "options": [
        "All DTF projects are guaranteed to deliver on their roadmap",
        "A vetted project can still fail commercially or technically after launch",
        "DTF vetting eliminates all liquidity risk permanently",
        "Token prices are stabilized by Jupiter after TGE"
      ],
      "correctAnswer": 1,
      "explanation": "The lesson states that while vetting reduces the chance of outright fraud, it cannot predict execution risk or market reception, so a curated project can still fail after launch."
    }
  ]
}

---

🤖 Ready-to-use prompt for Claude Code

Copy this into Claude Code on the PR branch to apply the fixes:

Apply the Jupiter Academy lesson review for lessons/jupiter-dtf.mdx.

Blockers (must fix):
1. Line 23: replace "It leverages upon the features of the blockchain" with "It leverages the features of the blockchain".

Suggestions (apply if you agree):
1. Wrap smart contract (l.31/65), liquidity pool (l.32/65/75), liquidity (l.32/75), TGE, vesting in <Term> tags.
2. Frontmatter: reconcile the "Product" topic badge with CONTRIBUTING.md (add it as a documented topic or use a listed one).
3. Lines 57–63: confirm the HumidiFi "sold out / no unsold tokens" and per-phase pricing details with the team (not in DTF docs).
4. Line 23: split the run-on and remove duplication with lines 19/21.
5. Line 31: "converts project promises into transparent, verifiable onchain contracts".
6. Line 57: fix the dangling "they" — "HumidiFi … launched its $WET token via DTF".
7. Line 65: convert the Stage 4 run-on into a bullet list.
8. Lines 80–88: convert the "Participating in a DTF Launch" section into numbered steps.
9. Add at least one DTF interface/phase-eligibility illustration.

Then commit and push to this PR branch. Do not invent facts — cite docs.jup.ag where the review did. Keep the Academy tone (educational, no financial advice).

(Quiz proposal in the comment above is for the app repo — not this content repo.)

_{Re-run with /review-lesson-pr 17 after pushing — this comment updates in place.}

[mu1titudes]

Agentic feedback addressed. No further comments.

• corrected market suitability content
• minor corrections on grammar, punctuation, syntax