DX-078: Write /concepts/risk

[IbrahimIjai]

Context

An honest enumeration of what can go wrong. The content map is explicit about
why this page exists: a risk page that only lists upside teaches readers not to
trust the rest of the documentation
(docs/dx_1/003_content_map.md §1).

Scope

• Market risk: leverage, liquidation, gap moves, funding costs over time.
• Protocol risk: smart contract bugs, upgrade authority, admin capabilities —
  state who can change what, verified against the contracts.
• Oracle risk: source failure, staleness, manipulation, and the consequences.
• Liquidity risk for LPs: adverse trader flow, exit conditions, withdrawal
  limits if any.
• Operational risk: RPC and indexer availability, front-end availability, and
  what a user can and cannot do if the interface is down.
• Audit status stated accurately, including if unaudited.

Acceptance criteria

• Admin and upgrade capabilities are verified against contract source, with
  file paths named in the PR.
• Audit status is accurate and unhedged.
• The "interface is down" section describes a real recovery path or says
  plainly that none exists.
• Reviewed by a maintainer before merge.

Out of scope

• Legal terms (DX-097).

---

Spec: docs/dx_1/003_content_map.md §3 · Depends on: DX-077

[Kappa16]

HI i can work on this issue FAST AND ACCURATE. expect PR IN LESS THAN 4HOURS

[chibuezeozowara]

@chibuezeozowara has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please, assign me to this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @chibuezeozowara to this issue.

[nursetechie]

@nursetechie has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Interested in contributing to this issue, please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @nursetechie to this issue.

[Prudentdev-xyz]

@Prudentdev-xyz has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on this issue because it aligns with my current learning and development goals, and I’m interested in making meaningful contributions to open source. I have experience with JavaScript, TypeScript, Git/GitHub, and blockchain development, and I’m comfortable learning and working through existing codebases. I’m ready to understand the project’s architecture, implement the solution, and contribute a well-tested and maintainable fix.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Prudentdev-xyz to this issue.

[drips-wave]

Congratulations, @Prudentdev-xyz! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Prudentdev-xyz: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊