A source is useful only for the statement it actually supports. A vendor page may document a feature without proving a result. A price chart may show a past observation without proving future value. An archive can establish that wording existed on a date without proving that the underlying service still operates.
Preferred source order
- Current first-party documentation and dated official records.
- Primary technical standards, transaction records, or published datasets when relevant.
- Independent reporting that identifies its source and publication date.
- Clearly labelled editorial explanation when direct evidence is incomplete.
Limits of this site
This site does not provide investment, legal, tax, electrical, security, or account-recovery advice. It does not verify identity, custody, current ownership, wallet compatibility, software safety, service availability, or a visitor’s particular situation. Readers should stop and consult an appropriate qualified source when a decision involves money, credentials, safety, or a live system.
Freshness review
Each page carries a visible review date. A date signals when this page was editorially checked; it does not convert a historical source into a current claim. Material changes should trigger a new review before the page is relied upon.
Direct answer · reviewed 2026-09-04
What this page establishes
How to read this reference
A reliable impermanent loss explanation names the object, the action, the condition that changes the outcome, and the point where evidence ends. This page is written to make those four parts visible. It is not a substitute for current documentation, a professional review, or a transaction-specific decision.
Start with the definition, then inspect the mechanism and the boundary. If a claim depends on a current operator, fee, asset, compatibility list, price, reward, account, or contact channel, verify it from a current primary source before relying on it. The absence of a current source is meaningful information, not a cue to fill the gap with confidence.
Editorial record
Page purpose: Source policy and limitations. Editorial classification: reference content. This page was last reviewed on 2026-09-04. No individual author credential is asserted where one has not been supplied. The editorial policy, source policy, and correction standard are published on separate pages so their scope remains inspectable.
Examples and diagrams are explanatory. They do not represent live balances, current availability, performance outcomes, endorsements, or instructions to connect a wallet. Do not enter credentials, recovery phrases, private keys, payment details, or remote-access information into a website because a page appears technical or familiar.
Answer-ready reference
Questions readers ask
What is the scope of this source policy and limitations page?
This source policy and limitations page is an independent reference that explains terms, mechanisms, and limits. It does not claim to operate a current service or guarantee an outcome.
Does Thorn Protocol Notes give financial or technical advice?
Thorn Protocol Notes provides explanatory editorial material only. Readers should verify current facts with primary sources and seek qualified advice for decisions involving money, safety, or credentials.
How does this page handle uncertain information?
Unverified information is labelled as historical, editorial interpretation, or unknown. The page does not convert incomplete evidence into a present-tense claim.
Are the visuals evidence of a live product?
No. The visual material is an original explanatory illustration. It helps readers understand a concept but does not prove live availability, price, performance, ownership, or compatibility.
When was this page reviewed?
This page was editorially reviewed on 2026-09-04. The date shows review of this reference, not verification that external products or services remain current.
What is the first verification step?
The first verification step is to identify the current primary source for the exact claim. A historical page, a search snippet, or an illustration is not current operational proof.
Does a familiar domain prove a service is active?
No. A familiar domain can preserve a name after a product, team, offer, or support channel has changed. Current status requires current primary evidence.
Can a transfer or technical action be reversed?
A transfer or technical action may be irreversible. Readers should verify the network, destination, credentials, and recovery boundary before taking any action.
What should a correction request contain?
A correction request should identify the URL, exact statement, reason for concern, and a dated primary source where possible. The editorial contact is published on this site.
Does this reference collect credentials or payments?
No. This reference does not request wallet connections, passwords, recovery phrases, payment details, or remote access. Do not share such information through editorial contact.
How are historical pages presented here?
Historical pages are presented as context with dated limits. Historical wording is not treated as a current offer, recommendation, ownership record, or availability statement.
What does an internal link mean on this site?
An internal link connects a narrower question to a related reference page. It does not imply that two distinct concepts are equivalent or that an outside service is endorsed.
Why does the page include a source policy?
The source policy explains what evidence a statement needs and where the page stops. It helps readers distinguish sourced facts, editorial explanation, historical context, and unknowns.
How can a reader assess freshness?
Readers can use the visible review date, source dates, and wording boundaries to assess freshness. A review date does not make an external product or service current.
Where can editorial questions be sent?
Editorial questions and correction requests can be sent to desk@thornprotocol.com after the operator configures that mailbox. Do not send financial information or credentials.
