How AlfaDAO prepares public research guides

Who publishes the library

AlfaDAO publishes this library under an organization byline.

The articles explain how to check public claims and calculations. They do not assess a reader's financial circumstances or recommend buying, selling or holding an asset. Worked examples use invented inputs; they are not forecasts or records of investment performance. Mentioning a protocol as a technical source is not an endorsement of that protocol.

Start with original sources

For technical behavior, start with the relevant protocol documentation, contract code, deployed addresses, governance proposal or original data. A project announcement establishes what its publisher said; it does not independently prove the claim. A familiar block-explorer label is a lead to investigate, rather than proof of a wallet owner's identity.

The sources linked from a guide let readers check the technical foundation. Match documentation to the network, deployment and version under investigation. Security reviews, dashboards and news reports can add context, but their scope, measurement choices and publication dates matter. A source about one version cannot establish the safety or behavior of every deployment.

Make the investigation repeatable

A useful research note records the question, the evidence used and the limits of the conclusion. When a claim involves a transaction or contract, record the network, address, block or transaction reference, observation time and relevant settings. Preserve the steps or query needed to reproduce a calculation.

Keep observations, assumptions and interpretations distinct. Ask what competing explanation fits the same evidence, what information is missing and what future observation would change the interpretation. Examples in the library use hypothetical inputs where indicated; they should not be read as live market data or forecasts.

• Identity: check the official domain, network and deployment before interpreting activity.
• Evidence: preserve the original link, observation time, definition and calculation.
• Uncertainty: name gaps, conflicts and alternative explanations.
• Follow-up: record the event or new evidence that should trigger another review.

Read dates in context

Each guide displays its publication date and substantive update date. Those dates describe the article, not the freshness of every external reference. Protocol documentation, risk settings and contract implementations can change after publication. Recheck the current original source before relying on a detail.

Adding a new article does not make older articles newly reviewed. If a guide changes materially, its visible update date and search metadata should move together. An archived announcement or old audit can still be useful evidence when its historical scope is explicit.

How AI assistance is used

This public library was prepared with AI assistance for drafting, organization and checking technical references. AI assistance can introduce errors or omit important context. The presence of a source link, an organization byline or a polished explanation is not a substitute for checking the underlying evidence.

Follow the original references and check whether a calculation's assumptions fit the question being investigated. Report a specific error with the source that corrects it.

Suggest a correction with evidence

Use AlfaDAO's official Discord link on this site to raise a correction or a question about a guide. Include the article URL, the specific statement, the original source and why the wording should change. Avoid sending recovery phrases, private keys, confidential account records or another person's private information.

Public guides use public sources. Member conversations, wallet-to-profile associations and private community records are not automatically available for publication. A useful correction can be shared without exposing private information.