Skip to content

WEB3_101.md

CeloHT edited this page Aug 10, 2026 · 1 revision

CeloHT Web3 101

Document Type: Web3 Fundamentals
Project: CeloHT
Status: Active / Evolving
Last Updated: August 2026
Authors: Johnny Dubic & CeloHT Community


1. Introduction

Web3 refers broadly to applications and services built around decentralized technologies, including blockchains, digital wallets, smart contracts, and decentralized networks.

This guide introduces the concepts users need to understand before interacting with CeloHT's Web3 services.

No previous blockchain experience is required.


2. What Is Web3?

Web3 is commonly used to describe a generation of internet applications that give users greater control over:

  • Digital assets

  • Wallets

  • Identity

  • Transactions

  • Data

  • Digital ownership

The term does not refer to one single technology.


3. Web2 vs Web3

A simplified comparison:

Web2 | Web3 -- | -- Accounts often controlled by platforms | Wallets can control user accounts Centralized services | Decentralized networks Platform-controlled databases | Blockchain-based records Password-based access | Cryptographic authorization Platform-mediated transactions | Blockchain transactions

In practice, many modern applications combine Web2 and Web3 technologies.


4. What Is a Blockchain?

A blockchain is a distributed system that maintains a shared record of transactions or other state changes.

Instead of relying on one database controlled by one organization, blockchain networks use a distributed set of participants to maintain and verify the system.


5. Why Blockchain Matters

Blockchain technology can provide:

  • Transparent transaction records

  • Cryptographic verification

  • Programmable assets

  • Decentralized infrastructure

  • Portable digital accounts

These properties can be useful for financial and community applications.


6. The Celo Blockchain

CeloHT is designed around the Celo ecosystem.

Celo is a blockchain network designed to support decentralized applications and payments.

CeloHT uses Celo-related infrastructure where appropriate for its applications and community programs.


7. Blockchain Networks

A blockchain network provides the infrastructure on which transactions and applications operate.

A network typically includes:

  • Nodes

  • Consensus mechanisms

  • Accounts

  • Transactions

  • Smart contracts

  • Network rules


8. Mainnet and Testnet

Mainnet

The production blockchain network where real assets and transactions operate.

Testnet

A testing environment used to experiment without relying on production assets.

Users should always verify which network they are connected to.


9. Wallets

A blockchain wallet is a tool for managing cryptographic keys and interacting with blockchain networks.

A wallet can allow users to:

  • Hold assets

  • Send assets

  • Receive assets

  • Sign transactions

  • Connect to decentralized applications


10. Your Wallet Address

A wallet address is a public identifier for a blockchain account.

It can generally be shared when someone needs to send you an asset.

Example format:

0x1234...abcd

Always verify the complete address before sending funds.


11. Private Keys

A private key is a cryptographic secret used to authorize actions from a blockchain account.

Anyone who obtains your private key may be able to control the associated assets.

Never share your private key.


12. Recovery Phrase

A recovery phrase, also called a seed phrase, is typically a sequence of words used to restore a wallet.

It is one of the most sensitive pieces of information in a self-custody wallet.

If someone asks for it, do not provide it.


13. Self-Custody

Self-custody means that the user controls the cryptographic credentials required to access their blockchain account.

Advantages may include:

  • Direct control

  • Reduced dependence on intermediaries

  • Portability

Risks include:

  • Lost credentials

  • Phishing

  • Malware

  • Irreversible transactions


14. Custodial Services

A custodial service controls the keys or assets on behalf of the user.

This can simplify some user experiences but introduces dependence on the service provider.

Users should understand who controls their assets before using a service.


15. Transactions

A blockchain transaction is an instruction submitted to the network.

Examples include:

  • Sending assets

  • Calling a smart contract

  • Approving an application action

Transactions are generally cryptographically signed.


16. Transaction Fees

Blockchain networks may charge fees for processing transactions.

On Celo, users may need CELO for applicable network fees depending on the transaction and current network configuration.

Fees can change.


17. Transaction Confirmation

A submitted transaction generally moves through stages such as:

Created
   ↓
Signed
   ↓
Submitted
   ↓
Pending
   ↓
Confirmed / Failed

A transaction should be considered successful only after appropriate confirmation.


18. Transaction Hash

A transaction hash uniquely identifies a blockchain transaction.

It can be used to inspect information such as:

  • Status

  • Sender

  • Recipient

  • Amount

  • Block

  • Contract interaction


19. Smart Contracts

A smart contract is software deployed to a blockchain.

It can automatically execute predefined logic when users or other contracts interact with it.

Smart contracts can support:

  • Payments

  • Exchanges

  • Governance

  • Registries

  • Decentralized applications


20. Smart Contract Risks

Smart contracts can contain vulnerabilities.

Risks may include:

  • Bugs

  • Incorrect logic

  • Unauthorized permissions

  • Economic exploits

  • Upgrade risks

Users should verify contracts before interacting with them.


21. Decentralized Applications

A decentralized application, or dApp, typically combines:

  • User interface

  • Blockchain

  • Smart contracts

  • Wallet

  • Supporting infrastructure

A dApp may not be completely decentralized in every component.


22. Wallet Connection

When a dApp asks to connect to your wallet, it may request permission to identify your public account.

Connection does not necessarily mean that the application can automatically spend your assets.

However, users should always review the requested permissions.


23. Transaction Signing

Signing a transaction authorizes a specific blockchain action.

Before signing, verify:

  • Application

  • Network

  • Contract

  • Function

  • Amount

  • Recipient


24. Message Signing

Some applications request a cryptographic signature that is not a blockchain transaction.

Users should still understand what they are signing.

Do not sign arbitrary messages when their purpose is unclear.


25. CELO

CELO is the native asset associated with the Celo blockchain.

Depending on the network and application, CELO may be used for:

  • Network fees

  • Transfers

  • Ecosystem participation

Its market value can fluctuate.


26. cUSD

cUSD is a stable-value asset in the Celo ecosystem.

It is designed to maintain a value relationship with the U.S. dollar, but users should not interpret "stablecoin" as meaning completely risk-free.

Risks can include:

  • Market conditions

  • Liquidity

  • Protocol risks

  • Issuer or reserve-related risks where applicable

  • Smart-contract risks


27. Stablecoins

A stablecoin is a digital asset designed to track the value of another asset, commonly a fiat currency.

Different stablecoins use different mechanisms.

Users should understand the specific mechanism behind the asset they use.


28. CeloHT and Tokens

CeloHT does not require users to purchase a proprietary CeloHT token to participate in its ecosystem.

The project follows a NO_TOKEN_POLICY approach.

See:

NO_TOKEN_POLICY.md


29. Gas and Network Fees

"Gas" generally refers to the computational resources required for blockchain operations.

A transaction may require payment for network resources.

The exact mechanism depends on the blockchain and transaction type.


30. Blockchain Explorers

A blockchain explorer allows users to inspect public blockchain activity.

Users can generally search for:

  • Addresses

  • Transactions

  • Blocks

  • Smart contracts

  • Token transfers

Explorers are useful for verifying transactions independently.


31. Blockchain Transparency

Blockchain data can be publicly visible.

This means users should be careful about associating personal information with public addresses.

A public address should not automatically be assumed to be anonymous.


32. Decentralization

Decentralization describes the distribution of control across multiple participants rather than concentrating control in one entity.

Different systems have different degrees of decentralization.

A project should not claim complete decentralization without evidence.


33. Consensus

Consensus mechanisms allow blockchain participants to agree on the state of the network.

Different blockchains use different consensus designs.

Users do not need to understand every technical detail to use a blockchain, but understanding the basic concept is useful.


34. Nodes

Nodes are computers participating in a blockchain network.

Depending on their role, nodes may:

  • Store blockchain data

  • Validate information

  • Relay transactions

  • Participate in consensus


35. Cryptography

Cryptography provides many of the security mechanisms used by blockchain systems.

Important concepts include:

  • Public keys

  • Private keys

  • Digital signatures

  • Hash functions


36. Public-Key Cryptography

A simplified model is:

Private Key
     ↓
Cryptographic Operation
     ↓
Digital Signature
     ↓
Network Verification

The private key should remain secret.


37. Hashes

A hash is a cryptographic representation of data.

Changing the original data generally produces a different hash.

Hashes are widely used for:

  • Transaction identification

  • Data integrity

  • Block structures

  • Cryptographic verification


38. Digital Signatures

Digital signatures allow a network to verify that an authorized private key approved an action without revealing the private key itself.

This is fundamental to blockchain transactions.


39. Web3 Identity

Web3 identities may be represented through wallet addresses and cryptographic credentials.

A wallet address is not necessarily equivalent to a legal identity.

Applications may still use additional identity mechanisms when required.


40. Decentralized Identity

Decentralized identity systems aim to give individuals more control over digital identity credentials.

They may use:

  • Cryptographic credentials

  • Verifiable credentials

  • Decentralized identifiers

These technologies are evolving.


41. NFTs

NFT stands for Non-Fungible Token.

An NFT represents a unique blockchain-based asset or record.

Potential applications include:

  • Digital collectibles

  • Certificates

  • Membership

  • Tickets

  • Digital identity

Not every NFT has financial value.


42. DeFi

DeFi stands for Decentralized Finance.

It refers broadly to financial applications built using blockchain infrastructure.

Examples include:

  • Lending

  • Trading

  • Payments

  • Liquidity protocols

DeFi can involve substantial technical and financial risks.


43. DAOs

DAO stands for Decentralized Autonomous Organization.

DAOs generally use blockchain technology and governance mechanisms to coordinate participants.

Not every organization calling itself a DAO is equally decentralized.


44. Governance

Blockchain governance determines how certain protocol or community decisions are made.

Governance may involve:

  • Voting

  • Delegation

  • Councils

  • Proposals

  • Smart contracts

CeloHT maintains its own governance framework for project-level decisions.


45. Web3 Payments

Blockchain payments can allow users to transfer digital assets without relying exclusively on traditional payment infrastructure.

Potential advantages include:

  • Global accessibility

  • Programmability

  • Faster settlement in some situations

  • Transparent transaction records

Users must still consider fees, compliance, volatility, and security.


46. Remittances

Blockchain-based systems can potentially support cross-border transfers.

A typical flow may look like:

Sender
  ↓
Digital Asset
  ↓
Blockchain
  ↓
Recipient / Agent
  ↓
Local Currency or Digital Asset

Actual availability depends on the service, jurisdiction, liquidity, and applicable regulations.


47. Agents

Community agents can help users access supported services.

Agents may provide:

  • Education

  • Onboarding

  • Transaction assistance

  • Local support

Agents should never take control of a user's private credentials.


48. Financial Inclusion

Financial inclusion means improving access to useful and affordable financial services.

Web3 may contribute through:

  • Digital payments

  • Wallet access

  • Stable-value assets

  • Lower barriers to certain services

  • Community-based financial education

Technology alone does not guarantee financial inclusion.


49. Web3 Education

Effective Web3 education should prioritize:

  1. Financial literacy

  2. Security

  3. Practical understanding

  4. Risk awareness

  5. Responsible participation

Users should understand risks before using financial applications.


50. Common Web3 Scams

Users should be cautious of:

  • Fake airdrops

  • Fake support accounts

  • Phishing websites

  • Fake investment opportunities

  • Wallet-draining applications

  • Fake token launches

  • Impersonation

  • "Guaranteed profit" claims


51. Phishing

Phishing attempts to trick users into revealing sensitive information or approving malicious actions.

Before connecting a wallet, verify:

  • Domain

  • Application identity

  • Source of the link

  • Requested permissions


52. Wallet Drainers

A malicious application may attempt to trick a user into approving transactions that transfer assets away.

Always read wallet approval requests carefully.


53. Irreversible Transactions

Many blockchain transactions cannot simply be reversed.

If you send assets to the wrong address, recovery may be impossible.

Always verify the recipient.


54. Investment Risk

Blockchain assets can experience significant volatility.

CeloHT educational materials should not be interpreted as financial advice or a guarantee of profit.

Users should make independent decisions.


55. Legal and Regulatory Considerations

Web3 services can be subject to laws and regulations depending on:

  • Country

  • Service

  • Asset

  • Transaction

  • User

  • Business model

Users should follow applicable laws and seek qualified legal advice when necessary.


56. Privacy

Blockchain transparency can conflict with expectations of traditional financial privacy.

Users should avoid putting unnecessary personal information into public blockchain transactions.

See:

DATA_PRIVACY.md


57. Security Checklist

Before using a Web3 application:

[ ] Verify the official application
[ ] Verify the domain
[ ] Verify the network
[ ] Verify the wallet
[ ] Review permissions
[ ] Review transaction details
[ ] Never share private keys
[ ] Never share recovery phrases
[ ] Confirm the transaction afterward

58. Learning Path for Beginners

A recommended CeloHT learning path is:

Web3 Basics
     ↓
Blockchain
     ↓
Wallets
     ↓
Private Keys
     ↓
Transactions
     ↓
Celo
     ↓
CELO / cUSD
     ↓
Smart Contracts
     ↓
dApps
     ↓
Security
     ↓
Practical Participation

59. Recommended Practice

Beginners should start with low-risk educational activities.

For example:

  • Learn wallet concepts.

  • Explore a blockchain explorer.

  • Understand a transaction.

  • Learn how signatures work.

  • Practice on a test environment when available.

Do not begin with significant financial exposure.


60. Web3 Glossary

Address

Public identifier for a blockchain account.

Blockchain

Distributed ledger/network maintaining shared state.

Block

A group of blockchain records processed together.

CELO

Native asset associated with the Celo network.

cUSD

Stable-value asset in the Celo ecosystem.

dApp

Decentralized application.

Gas

Resources/fees associated with blockchain computation.

Hash

Cryptographic representation of data.

Private Key

Secret cryptographic credential controlling an account.

Smart Contract

Program deployed to a blockchain.

Stablecoin

Digital asset designed to track another asset's value.

Wallet

Tool for managing blockchain keys and signing transactions.

Web3

Broad term for decentralized and user-controlled internet technologies.


61. CeloHT Web3 Philosophy

CeloHT promotes practical Web3 education rather than speculative hype.

The objective is to help people understand:

  • What the technology does

  • What it does not do

  • How to use it safely

  • Where it can create practical value

  • What risks remain


62. Related CeloHT Documentation

Continue learning through:

  • QUICK_START.md

  • USER_GUIDE.md

  • TUTORIALS.md

  • SECURITY.md

  • SMART_CONTRACTS.md

  • NO_TOKEN_POLICY.md

  • DATA_PRIVACY.md

  • GOVERNANCE.md

  • RESEARCH.md


63. Final Statement

Web3 is not simply about cryptocurrency.

It is a collection of technologies that can change how people interact with digital assets, applications, communities, and financial systems.

The most important skill is not knowing every technical term.

It is knowing what you are signing, what you are using, who controls it, and what risks you are accepting.

Learn first. Verify second. Interact carefully. Never surrender your private keys.


Document Status: Active / Evolving
Maintained By: CeloHT Community
Founder: Johnny Dubic
Primary Principle: Practical Web3 education, financial awareness, security, and responsible participation

CeloHT

Community-powered Web3 for real-world impact.

CeloHT is an open-source community initiative building practical solutions around Web3, financial inclusion, education, decentralized services, and environmental impact.

Learn. Build. Participate. Impact.

Clone this wiki locally