Open the complete story and reading map
After learning what a shared program can enforce, we need to ask what the balances inside that program mean. A token can be easy to transfer while the claim attached to it remains difficult to understand. That distinction connects Ethereum's early applications, the ICO period and today's tokenized assets.
A standard interface made integration easier
ERC-20, created on November 19, 2015, specifies a common interface for fungible tokens: balances, transfers and allowances, among other operations. Applications can use a familiar set of calls rather than inventing a different integration for every token. The standard describes software behavior; it does not certify reserves, future profits or the enforceability of a promise.
A useful analogy is a standard envelope. Making envelopes fit the same sorting machine does not make every document inside them the same kind of agreement. Similarly, two token contracts may expose compatible functions while their issuers, controls and holder rights differ substantially.
Four meanings that a balance cannot tell you
Suppose four fictional projects each give you 100 tokens. Their wallet displays look similar. The following distinctions would still require separate evidence:
| Possible role | What 100 tokens might represent | Question to verify |
|---|---|---|
| Service access | Credits usable for a defined service. | Does the service exist, and can the issuer change the redemption rules? |
| Governance | Voting weight for specified decisions. | Which decisions are actually executable, and who holds veto or upgrade powers? |
| External claim | A claim connected to assets or cash flows. | Which documents and institutions connect the token to that right? |
| Incentive | A reward for providing a resource or attracting users. | Who funds the reward, and what happens when distribution ends? |
These roles can overlap. None should be inferred just from the ticker, token quantity or the word “utility.” Nor does a token holder automatically own shares in the organization that developed the software.
Why the funding story and the product story can diverge
An initial coin offering, or ICO, describes a token fundraising arrangement. A team might receive funds before a promised network or service works. The sale can therefore succeed as fundraising while the product fails to attract repeat use. Separately, a useful product can exist without sending its revenue to token holders.
Use a fictional storage service to separate these claims. It sells 1,000 credits for $1 each and collects $1,000. Later, users spend 100 credits on storage. The fundraising receipt, service usage and cash available to meet operating costs are different measurements. A credit's market price does not tell you the provider's remaining costs or whether a holder has a right to any surplus.
This is a reasoning example, not a reconstruction of a particular ICO. To evaluate a historical project, record what was promised at the sale date and compare it with what was subsequently delivered. Reading only the latest website can erase the distinction between an original commitment and a later change.
A dated legal boundary, not a universal classification
In its July 25, 2017 investigation report, the U.S. SEC concluded that The DAO's tokens were securities under the facts it examined. That finding belongs to a particular offering and jurisdiction. It should not be rewritten as “every token everywhere has the same legal status.” Current obligations require current, jurisdiction-specific analysis.
For a learner, the enduring distinction is between a software label and the underlying arrangement. Transferability does not settle what was sold, what was promised or who is accountable. The technical and institutional descriptions must be read together.
From fundraising to incentives
Tokens also provide a way to reward participation in a running application. Imagine a pool earns $20 in user fees but distributes rewards worth $80 during the same observation period. The $100 received by participants combines two different sources. Calling all of it “customer revenue” would hide the subsidy.
The next part of the story connects token interfaces with more stable accounting units, exchange pools and lending. Stablecoins can make quoted amounts easier to interpret, but their name does not resolve backing, redemption or custody. DeFi incentives then add another measurement problem: deposits attracted by rewards need not represent lasting demand.
Check your reasoning: a token follows ERC-20 and trades on a market. What rights does that prove?
Neither fact alone establishes a claim on company profits, a right to redeem for cash or control over all application decisions. Read the actual contract permissions and the applicable terms for the specific arrangement.
Related application: Tokenized claims, cash flows and exit risk.