Academy topicbeginner

Foundations

Foundations covers the concepts that stop users from treating crypto like a traditional app. It explains chain state, wallets, custody, signatures, gas, and why every onchain action has irreversible properties.

What this topic helps you spot
wallet custody
signatures
gas costs
How to use this topic
Use this page as a concept map across glossary terms, tracks, and product surfaces.
If the concept feels abstract, start with the practical lessons before you go deeper.
Use the highlights below as fast anchors for what should jump out at you in product UI.

Start with these signals

Use these as first-pass anchors. If these signals become easier to spot on live screens, the topic is doing real work.

Signal 1
wallet custody
Signal 2
signatures
Signal 3
gas costs
Signal 4
network selection
Beginner execution check
I know what chain I am using.
I know what token and contract this action touches.
I understand whether this is a quote, an approval, or a final confirmation.
Spot first
wallet custody
Watch for
Treating wallet actions like reversible app settings.
Use live
Translate each key UI element into what it changes onchain.
Core lesson

Start with the practical lessons

Work through the main concept first, then move into applied judgment and next actions.

The three beginner mistakes everything else grows from

Most early crypto mistakes come from carrying Web2 assumptions into an environment where permissions are sharper, support is weaker, and bad clicks are much harder to unwind.

A wallet is not customer support plus password reset. It is direct authority over assets and permissions.
A signature is not a harmless login click. It can authorize spending, routing, or future actions you will only understand later if you rushed now.
Chain choice is not a cosmetic setting. It changes fees, execution speed, explorer context, and what route you are actually taking.
If you rush through those basics, every later trade gets riskier and harder to debug.
Foundations matter because they change how you interpret every product surface after them.

How to look at product UI without fooling yourself

The goal of beginner literacy is not memorizing terms. It is being able to look at a swap, token page, or wallet prompt and understand what is operationally happening.

Chain badges tell you execution context, not branding flavor.
Recipient and router fields deserve separate verification, even if the screen feels familiar.
Fee warnings and approval warnings are decision points, not visual noise.
If a UI element changes what can happen onchain, it deserves attention before you click.
A readable interface is only useful if the user knows what to read as consequential.

Why balances and polished dashboards can still lie to beginners

One of the first expensive beginner mistakes is assuming that a visible balance, a familiar interface, or a platform dashboard means the assets are safe and fully under the user's control.

A visible balance is not the same thing as direct control over assets.
Custody risk often feels invisible because the UI keeps working right until it does not.
A polished account or wallet surface can hide whether authority really belongs to you, a signer group, or a platform.
Beginners get safer fast when they separate what they can see from what they can actually control.
Foundations get real when users stop confusing visibility with control.
Real cases

What actually happened

These are public cases and repeated real-world patterns turned into teachable stories. Use them to see how small shortcuts become expensive outcomes in real product flows.

Public source-backed
Read the story first, then notice the exact decision that made the damage possible.
Case study

Users saw balances every day until the platform owed them $8.7B

Loss: $8.7B owed to customers
Situation

When FTX collapsed, the bankruptcy team said the exchange owed customers about $8.7 billion. The lesson for beginners is brutal but simple: visible balances and a smooth product experience never proved those assets were truly under user control.

Why this case matters

One real-world failure usually teaches faster than ten abstract warnings.

What they assumed

If the dashboard shows my assets clearly and the product works every day, control is basically the same as ownership.

Red flag you would have seen in the UI

A product experience where balances, history, and normal activity are easy to see, but the custody and withdrawal reality stays mentally off-screen.

You would have seen this on

These are the exact product moments where this kind of mistake usually first looks harmless.

StatusWallet prompt
What went wrong
1
Users treated visibility as proof of control.
2
Routine product use made the custody model feel safer than it really was.
3
When the hidden control layer broke, the relevant loss was not one bad trade. It was the asset claim itself.
4
The result was an $8.7 billion hole owed to customers.
Core lesson

Foundations are not abstract. They are what stop a clean balance view from being mistaken for real control.

What they should have done instead

Teach yourself to ask who really controls the assets, who can halt access, and what layer you are trusting before you let a polished dashboard calm you down.

How this topic breaks down

Roadmap
Section 1

Mental models to lock in early

Foundations is less about memorizing definitions and more about building habits that stop users from making Web2 assumptions in an irreversible environment.

wallet is not the chainsigning is not browsingnetwork choice changes execution realityirreversible actions deserve slow thinking
Section 2

What users should recognize in product UI

This topic should make core wallet and network interfaces immediately more legible inside ZeroLyx and similar products.

chain badgeswallet promptsgas and approval warningsrecipient and router fields
Use after the lesson

Before you sign or confirm

This section should help in the moment of risk. Keep one question in mind: what should I check right now before giving authority or sending the route forward?

Check now
Do not think in abstract principles here. Think in checks you can do on this screen before moving forward.
Do now
Translate each key UI element into what it changes onchain.
Treat signatures and approvals as authority, not convenience.
Use chain and contract context to understand what environment you are really in.
Pause at the wallet layer until you can explain the prompt in plain English.
Do not continue if
Do not assume product polish removes the need to verify.
Do not treat chain selection like a cosmetic filter.
Do not click through wallet prompts as if they were login modals.
Red flag if this feels routine
If this step feels like harmless friction, that is already the red flag.
1
Treating wallet actions like reversible app settings.
2
Reading UI labels without connecting them to onchain consequences.
3
Confusing polished product design with reduced execution risk.
4
Feeling ready to continue before chain, contract, and authority are actually clear.
Before first serious use
If these checks are not clear yet, you are not in a good position to rely on speed or instinct.

Beginner execution check

1
I know what chain I am using.
2
I know what token and contract this action touches.
3
I understand whether this is a quote, an approval, or a final confirmation.
4
If I cannot explain the prompt in one sentence, I should slow down.
Continue learning

Keep building the topic

Once the core lesson is clear, use these paths to widen the mental model or go deeper where the concept matters most.

Continue learning

Go deeper from here

Once the core lesson is clear, use these paths to widen the mental model or go deeper where the concept matters most.

    Foundations | ZeroLyx Academy