Internal Alignment (For team)
🔹 Quantus Internal Alignment Document
(Team Context & Product Direction)
“Quantus is not just a stablecoin yield protocol — it is an execution layer where liquidity itself becomes productive.” — Team Quantus Alignment Draft
1️⃣ Current Status
The Quantus GitBook is now a fully drafted, near-final version. The overall narrative is consistent, but certain terms, numbers, and phrasing still differ slightly between sections.
These are not errors — they reflect different stages of product evolution (early LSP concept → latest execution-based model).
Hence, what follows is not merely “copy edits,” but a strategic clarification of how the team wants to present Quantus to the world: how we describe it, how we visualize it, and how we align communication across design, tech, and marketing.
2️⃣ Key Discussion Points (with Context)
A. “Stablecoin-Staking Protocol” vs. “Execution-Backed Yield Protocol”
🧩 Current
Some pages (e.g., What Is Quantus) still say “stablecoin-staking protocol.”
Newer pages already use “execution-backed yield layer.”
🎯 Context
Staking commonly implies PoS or lending-based yield (Lido, RWA, etc.).
Quantus, however, earns yield purely from execution quality — atomic arbitrage, MEV, routing.
Yet, the word staking is user-friendly and conveys the idea of “earning on deposited assets.”
💬 Our Perspective
We don’t have to discard staking. We can keep “liquid stablecoin staking protocol”, but clarify that this staking is execution-driven, not validator-based.
🧠 Product Explanation
Users stake stablecoins, but that liquidity participates in execution routes, generating yield.
Thus the flow is Stake → Execute → Yield.
“Staking” becomes a metaphor for participating in efficiency validation.
✅ Decision
Brand tone:
“A liquid stablecoin staking protocol powered by execution efficiency.”
Documentation note:
“Quantus uses the familiar concept of staking — but instead of validating blocks, your stablecoins validate efficiency.”
B. Yield Range (8–20 % vs. “Up to 30 %”)
🧩 Current
Early versions: “Up to 30 % APY.”
Technical sections: “8–20 % APR, stretch 30 %.”
🎯 Context
The difference is between short-term operational goals and long-term vision.
Realistic early yield: 12–20 %.
Optimized cross-chain + AI execution could reach 25–30 % later.
💬 Messaging
“Quantus targets a stable 8–20 % APR at launch, with long-term optimization aiming for 25–30 % APY as the execution network matures.”
🧠 Product Framing
Phase 1–2: Solana execution → 8–20 %.
Phase 3–4: Cross-chain MEV + AI routing → 25–30 %.
The 30 % figure is not hype; it’s a Phase 3 performance milestone.
✅ Decision
“8–20 %” = Operational Target.
“30 %” = Vision Target.
All public wording → “Target 8–20 %, stretch up to 30 %.”
C. NAV Update Frequency — Real-Time vs. Epoch
🧩 Current
Some pages: “Every 30 seconds.”
Parameter tables: “6–12 hour epoch.”
🎯 Context
NAV is computed continuously but posting every block is gas-inefficient.
The system therefore uses continuous accrual + periodic checkpoints.
💬 User-Friendly Copy
“NAV increases continuously; checkpoints occur every few minutes (currently ~30 s in beta) and full reports publish every 6–12 hours.”
🧠 Product Explanation
30 s = beta simulation speed.
6–12 h = official reporting cycle.
Users perceive “real-time yield,” though actual updates are periodic.
✅ Decision
Technical docs → “checkpoint / epoch.”
Marketing → “real-time compounding, periodically verified on-chain.”
D. “Hedge Unit v2” vs. “Execution Unit v2”
🧩 Current
Older: “Hedge Unit v2 — Delta-Neutral Engine.”
New: “Execution Unit v2 — Delta-Neutral Executor.”
🎯 Context
“Hedge” evokes derivative-based strategies (Ethena, GMX).
Quantus achieves neutrality through atomic execution and basket balancing, not derivatives.
🧠 Product Explanation
The Execution Unit acts like a market-efficiency validator.
It removes price dislocations, maintaining delta-neutrality organically.
💬 Tone
“Quantus doesn’t hedge positions — it executes neutrality.”
✅ Decision
Final name: Execution Unit v2 — The Delta-Neutral Executor.
Replace all “Hedge Engine” icons/terms in visuals.
E. Layer-Level Yield Percentages
🧩 Current
Layer 1 = 5–10 %, Layer 2 = 10–15 %, Layer 3 = 10–15 %.
Readers might incorrectly sum them.
🎯 Context
These numbers are contribution shares, not additive yields.
💬 Clarification
“Percentages indicate contribution shares of each yield source and are non-additive.”
🧠 Product Explanation
Arbitrage = base yield.
NAV Capture = efficiency yield.
Execution Efficiency = optimization yield.
Combined they form one compounded APY, not separate returns.
✅ Decision
Keep table, add footnote “non-additive.”
Visualize as a pie chart (share composition).
F. Terminology Consistency (“Gasless”, “Gas-Free”, etc.)
🧩 Current
Mixed usage: gasless / gas-free / no gas fee.
🎯 Context
From a user’s view, “no gas” is key.
Technically, the Paymaster sponsors gas fees.
Therefore official term: gasless.
💬 Example
“All transactions are gasless, sponsored by the Quantus Paymaster.”
✅ Decision
Official glossary term: Paymaster (gasless UX).
UI labels: “Gasless Deposit / Gasless Redeem.”
Remove all other variants.
3️⃣ Strategic Direction
🌱 Product Identity
Quantus = Liquid Stablecoin Staking Protocol (Execution-Backed)
Keep staking for accessibility.
Redefine its meaning as liquidity participating in execution, not validator staking.
Philosophy: Execution as Yield.
No leverage, no credit, no synthetic exposure.
💵 Yield Roadmap
Short Term (Phase 1–2)
Solana core execution
8–20 %
Mid Term (Phase 3)
Cross-chain + AI optimizer
20–25 %
Long Term (Phase 4)
Global LSL mesh
25–30 % APY
🎨 Branding & Tone
Friendly to users, honest to developers.
Marketing can use staking and yield language; documentation must always clarify execution origin.
Visual tone: stability + intelligence → “the dollar that works.”
4️⃣ Consolidated Team Decisions
Product Positioning
“Liquid Stablecoin Staking Protocol (Execution-Backed)”
Core Philosophy
“Execution as Yield” — no leverage / no lending
Yield Messaging
Baseline 8–20 %, Stretch Goal 30 %
NAV Logic
Continuous accrual + 6–12 h epoch checkpoint
Terminology
“Execution Unit v2”, “Paymaster (gasless UX)”, “Instant Bucket / Queue Auction”
Tone
Familiar + Innovative (“user-friendly staking, tech-driven execution”)
🧭 Guiding Sentence (for Team Use)
Quantus bridges two worlds: the familiarity of staking with the innovation of execution-layer yield. Every line of copy, UI label, and visual identity should communicate both — accessibility for users and technical integrity for the ecosystem.
Last updated