-
Notifications
You must be signed in to change notification settings - Fork 25
Open
Open
Copy link
Labels
backlogTo organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.To organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.
Description
Problem / Why
New developers often don’t understand what a node is in TON, who operates nodes (validators vs non-validators), and how apps actually reach the network (wallets, APIs, liteservers). This causes confusion early in onboarding.
What to do
Add a beginner-friendly section that explains:
- What a node is (stores/serves blockchain data, participates in propagation/validation)
- Who runs nodes (validators, infrastructure providers, explorers/indexers, projects, community)
- How users/apps interact (wallet/app → API/liteserver → TON nodes)
Diagram to be added
A simple diagram showing flow, e.g.:
User / Wallet / DApp
→ API provider / Liteserver (gateway)
→ TON Nodes (Full nodes)
→ Validators (subset that produces blocks)
Acceptance criteria
- The page contains a clear definition of “node” + “who runs it” in plain language.
- Includes one diagram that matches the text and helps a beginner visualize the system.
- Links to deeper reading (Nodes / Validators / Liteservers) as optional follow-ups.
Metadata
Metadata
Assignees
Labels
backlogTo organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.To organize the backlog into a hierarchy. Should never be closed, no assignees, no milestones.