TOPIC GUIDE / Evidence before inference

LLM DeFi Altcoin

Use a language model to structure DeFi questions, inspect supplied material, and identify gaps while keeping verification tied to independent evidence. A useful result distinguishes documented facts from interpretation and missing information. Build the workflow around claims that can be checked, with source versions and observation dates preserved alongside the answer.

Read the full Lab guide

Turn broad interest into testable claims

Choose a question with an observable answer, such as which account controls a deployment’s upgrade mechanism or which steps a documented withdrawal requires. Specify the network, contract, version, and relevant date. This limits the opportunity to combine details from unrelated deployments into a plausible but inaccurate explanation.

NIST identifies confidently stated false content as a generative-AI risk and includes source verification among its management actions. Build a claim ledger with the statement, evidence, scope, and status. Allow entries to remain unresolved. A completed-looking table should not take priority over an accurate record of missing information.

Match the evidence to the question

Use the actual deployment and contract state for questions about current onchain configuration. Use governing documents for questions about an offchain obligation. Preserve the relevant source section and its version. Ask the model to identify supporting passages, then inspect whether they establish the precise claim being made.

Evaluate arithmetic with a calculator or reviewed script, keeping input units and observation boundaries explicit. In a hypothetical withdrawal comparison, a correct formula cannot compensate for missing fees or a quote from another network. Leave unknown inputs visible and describe any result as conditional on the assumptions it uses.

Deliver a bounded finding

Prepare a short memo containing verified findings, reasoned inferences, conflicting evidence, and unanswered questions. Explain what new evidence would change the conclusion. For changing onchain observations, preserve a block reference when available so someone can distinguish a new state from an earlier interpretation mistake.

Keep research access separate from wallet execution, and treat retrieved text as material to examine rather than new instructions. Review the final draft for conditions lost during summarization. Another model can suggest checks, but agreement is still a hypothesis until the underlying sources and calculations support the finding.

Primary reference: NIST AI 600-1: Generative Artificial Intelligence Profile. Read the current documentation for the exact network, asset, or product you are researching.

Keep exploring

Questions
worth asking.

What if the model gives a source URL?

Open the source and inspect the relevant passage. Confirm its identity, date, version, and scope; a plausible citation does not establish that it exists or supports the claim.

Can model agreement replace verification?

Agreement may help identify a point to investigate, but it does not establish accuracy. Check the primary evidence and calculations, especially when the answer concerns a particular deployment or transaction.

How should missing evidence appear?

Label the claim unresolved and identify what would answer it. Preserve conditions and uncertainties in the final memo instead of asking the model to fill gaps with likely-sounding details.

From the DeFi Altcoin Lab

Go one layer deeper.

Put the concepts to work with a detailed guide, concrete research steps, and the questions to ask before acting.

LLM DeFi AltcoinAI DeFi AltcoinAgent DeFi Altcoin
DeFi AltcoinAgent DeFi AltcoinRWA DeFi Altcoin