How Lynx Learn is made.

Purpose and audience

Lynx Learn helps crypto-aware readers understand perpetual futures without assuming they already know derivatives. Glossary pages are reference and explanation, not trading recommendations, market forecasts, or personalized advice.

Source standard

We prefer regulators, standards bodies, market-structure educators, protocol documentation, oracle documentation, and original Lynx implementation material. Secondary sources may provide context but should not carry a technical claim when a primary source is available.

Each glossary page displays the sources used for its definition and mechanics. Venue-specific rules are attributed to that venue and are not presented as universal.

Writing and technical review

An author drafts each entry and checks its worked example. A separate reviewer checks terminology, arithmetic, venue caveats, and any Lynx-specific statement. Author and reviewer records are shown on the page with the last review date.

Risk language

We do not describe leverage as free capital, minimize liquidation risk, promise outcomes, or imply that one metric predicts price. Worked examples exclude costs only when that exclusion is explicit. Every glossary entry reminds readers that formulas and liquidation procedures vary by venue.

Updates and freshness

Core glossary entries are reviewed at least quarterly. We review a page sooner when protocol mechanics, source documentation, terminology, or a material example changes. Meaningful changes update the visible review date and the page’s structured metadata.

Corrections

Report a factual, mathematical, or attribution issue through the official Lynx support contact shown inside the Lynx app. Include the page URL, the disputed passage, and a supporting source. Confirmed corrections are made promptly and trigger a new review date.

Editorial disagreements that do not change the accuracy of a definition may be clarified without silently changing the underlying claim.