New editorial guide, published 17 October 2026. The historical sources linked below are preserved separately and are not represented as current product or service information.
A short symbol is convenient on a screen. It is not enough to establish which asset a screen describes. Two interfaces can show the same letters while referring to different contracts, networks or entirely different kinds of record. The old Nikola Trader captures do not establish a verified token contract for this domain, and this edition does not invent one. This guide explains a narrower technical habit: record an asset’s context before interpreting its label. The examples use fictional identifiers, not real contracts, purchase recommendations or instructions to send funds. Nikola Notes is a reading site, not a token issuer or exchange.
Treat the symbol as a label
The ERC-20 specification defines a standard token interface and treats name, symbol and decimals as optional methods. The presence of a familiar symbol therefore should not be confused with an authentication mechanism. A label improves usability; it does not independently identify an organisation or prove that a contract belongs to the project a reader has in mind. When taking notes, record the network and contract address separately from the display name. Keep the distinction even when a particular interface makes the label much larger than the address.
In a fictional example, two contracts both display the symbol LEAF. One is an exercise contract on a test network; the other is a separate deployment elsewhere. The matching label does not make their records interchangeable. Do not describe this example as an actual duplicate-token incident. Its purpose is to show why a display field cannot carry all the identity work. A report that says LEAF moved should identify which record was observed before discussing the movement, its amount or any interpretation of its significance.
Record the network and address together
An address string needs a network context. A copied hexadecimal value alone does not tell a reader which chain’s state was queried. Record the network identifier, contract address and observation source as a bundle. If the source is an explorer, check what network it is displaying rather than inferring that from a familiar page layout. If the context cannot be established, mark the observation incomplete. Do not resolve uncertainty by choosing the most popular network or the deployment that makes the surrounding story appear plausible.
Keep raw identifiers intact in working evidence. A shortened address is useful for a compact display but cannot establish equality when only its beginning and ending are visible. Compare complete values in the appropriate technical context. Do not paste credentials or recovery words into an identity worksheet; they are not needed for this public-record task. The worksheet should identify what was observed, not collect control over an account. A public contract reference and a private signing secret have fundamentally different roles and should never be treated as interchangeable evidence.
Separate identification from endorsement
Finding a contract address associated with a website is not the same as verifying the website’s operator, the contract’s behaviour or the asset’s economic claims. Those are separate questions. A source can establish that a page displayed an address at a particular time without proving the address was authorised by a claimed organisation. Record who supplied the association and what additional evidence supports it. Avoid using the word official merely because an address appears on a polished page or is repeated by several sites relying on the same statement.
Likewise, identifying a deployed contract does not establish that its code fulfils a promotional promise. A familiar interface can expose standard methods while containing other behaviours that require separate examination. This guide does not perform a contract audit or establish safety for any asset. Its task comes earlier: ensure the object being discussed is actually identified. A clear identifier makes a later investigation possible. It should not be presented as a badge that substitutes for that investigation or as evidence of a current service’s solvency, availability or legitimacy.
Keep display precision separate from quantity
A raw integer and its formatted display can look very different. In a fictional interface using two decimal places, a raw quantity of one hundred and twenty-three may display as 1.23. Changing the formatting assumption changes the displayed amount without changing the raw value. Record the scale used by the interface and where that scale came from. Do not infer it from a symbol or apply a familiar asset’s precision to another contract. A comparison of two displays is incomplete if their formatting rules are unknown.
Avoid turning a formatting observation into a valuation claim. A token quantity is not a currency price, and a price label does not establish an executable sale value. This reading edition provides no price feed. In an investigation, preserve the raw value, display rule and observation context before discussing a monetary interpretation. If one of those fields is unavailable, report the gap. A precise-looking screen amount can still be based on an unsupported assumption about the asset, its scale or the market information attached to it.
Attach identity to every exported record
An export can lose the context that made a screen understandable. A spreadsheet row containing a symbol, amount and timestamp may omit the network or contract field. A screenshot may crop the explorer’s network label. A copied paragraph may retain the asset name but drop the address reference. Review each handover format for those losses. The necessary identifiers should travel with the record or be linked through a stable reference, not depend on a person remembering which browser tab was open when the observation was made.
Use an invented comparison exercise. Give a reviewer two records with the same symbol and ask whether they refer to the same asset. Supply network and complete contract fields only after the reviewer identifies the missing information. The exercise demonstrates the evidence requirement without requiring a real transaction. Then inspect a real project’s public documentation if that is within scope. Do not fill missing fields with invented addresses. An explicit unknown is more useful than a complete-looking table that points to an object nobody actually established.
Write the conclusion at the identified level
A careful note can say that a particular contract on a named network returned a particular label at an observed point. That is narrower than saying a named company issued an asset or that a token is verified. Keep stronger organisational and historical claims tied to their own evidence. For this domain, the early captures identify Nikola Trader pages but do not establish a token contract. The new catalogue preserves that limit. This guide does not repair the missing history by assigning a plausible symbol, issuer or deployment.
Before publication, check the title, tables and captions for context loss. If a shortened display is used, provide access to the complete public identifier without exposing private information. State which claims remain outside the examination. The repeatable habit is to separate label, identifier, behaviour and endorsement. They can be related, but one does not automatically establish the others. A short symbol helps a reader recognise a screen element. A properly contextualised identifier helps a reader know which technical object the evidence is actually about.