Report Template

Monthly Perp DEX Venue Review Template for Independent Research

This reusable article pattern keeps venue research focused on mechanics, source quality, and risk questions. It is educational research only, not financial advice, not a recommendation, and no trading advice.

Reusable Article Pattern

Each venue review should use the same order so readers see risk before feature enthusiasm. The publication draft should start with source basis, review status, last reviewed date, publication status, and guardrail text.

  • Research boundary: state that the article is educational, not advice, and not a venue recommendation.
  • Source basis: list the kinds of documentation, product screens, and risk notes used for the review.
  • Risk-first summary: describe collateral, liquidation, oracle, bridge, admin, and operational questions first.
  • Mechanics notes: explain execution model, margin design, fees, funding, and withdrawals without ranking venues.

Monthly Review Fields

A monthly review should document what changed and what remains unknown. Avoid converting incomplete research into conclusions about whether users should deposit funds or use leverage.

  • Venue name, network, markets reviewed, timestamp, and version or documentation date if available.
  • Margin, liquidation, funding, collateral, withdrawal, and account recovery changes since the prior review.
  • Operational events, governance changes, oracle incidents, bridge updates, or app availability issues.
  • Open questions that block publication or require an explicit reviewer note.

Publication Guardrails

The final pass should remove promotional framing and make the limits of the research obvious. A draft should not publish if it contains referral assumptions, unsupported claims, venue rankings, or missing source status.

  • Confirm there are no trade calls, price targets, performance promises, referral links, or promotional rankings.
  • Check every external reference manually before publication and record the review date in the article metadata.
  • Make uncertainty visible when source quality, current parameters, or venue operations cannot be confirmed.
  • Link back to the disclaimer and roadmap so readers can distinguish education from execution decisions.