Registros distribuídos
Estado compartilhado
Registros distribuídos é uma aula grátis de Web3 & DApp Development Fundamentals no CoddyKit. Esta é a aula 4 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Web3 & DApp Development Fundamentals, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Web3 & DApp Development Fundamentals inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
What Is a Distributed Ledger?
A distributed ledger is a database that is replicated and synchronized across many independent computers called nodes.
There is no single master copy — every node holds the full ledger and helps keep it consistent.
Centralized vs Distributed
A traditional ledger lives on one server controlled by one party. A distributed ledger removes that single point of control and failure.
- Centralized: one owner, one copy, one trust anchor
- Distributed: many peers, many copies, shared trust
Nodes and Peers
A node is any computer running the blockchain software and storing a copy of the ledger. Nodes connect directly to each other as peers in a network.
There is no central server to ask — peers gossip data among themselves.
Node A <-> Node B
^ ^
| |
v v
Node D <-> Node CReplication
Replication means every full node keeps an identical copy of all blocks.
If many nodes go offline, the data survives on the rest. This redundancy gives blockchains their famous resilience.
Shared State
The ledger represents a shared state — for example, every account balance. All honest nodes must agree on this state.
When a new block is applied, each node updates its state the same way, so they stay in sync.
Shared state (account balances):
Alice: 12 ETH
Bob: 5 ETH
Carol: 8 ETHPropagating Transactions
When you submit a transaction, your node broadcasts it to its peers, who relay it onward. This gossip protocol spreads it across the whole network in seconds.
Pending transactions wait in a pool called the mempool.
Reaching Agreement
Because anyone can propose blocks, nodes need a way to agree on a single version of history. This is the job of a consensus mechanism.
Consensus ensures all honest nodes converge on the same ordered chain of blocks.
Trustless by Design
Distributed ledgers are often called trustless — not because trust is absent, but because you do not need to trust any single party.
You trust the protocol and the math (hashing, signatures, consensus) instead of an intermediary.
Permissionless vs Permissioned
Ledgers differ in who may join:
- Permissionless (Bitcoin, Ethereum) — anyone can run a node
- Permissioned (enterprise chains) — only approved participants
Both are distributed, but they differ in openness and trust assumptions.
Resilience and Censorship Resistance
Because copies live everywhere and no one controls them all, distributed ledgers resist censorship and downtime.
Shutting one node down does nothing; the network simply routes around it.
Putting It Together
A distributed ledger is a replicated, peer-to-peer database where nodes maintain a shared, agreed-upon state.
Replication gives resilience, gossip gives reach, and consensus gives a single source of truth without a central authority.
Quick Check
Test your understanding of distributed ledgers.
Recap: Distributed Ledgers
You learned that:
- A distributed ledger is replicated across many peer nodes
- All nodes maintain a shared state
- Transactions gossip across the network
- The system is trustless and resilient
- Consensus keeps everyone on one chain
Next course: how consensus actually works.
Perguntas Frequentes
A aula “Registros distribuídos” é grátis?
Sim — o texto completo de “Registros distribuídos” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Web3 & DApp Development Fundamentals, atualize para CoddyKit PRO. O curso de Web3 & DApp Development Fundamentals inclui 4 aulas no total.
O que vou aprender em “Registros distribuídos”?
Estado compartilhado Você pratica Web3 & DApp Development Fundamentals com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar Web3 & DApp Development Fundamentals?
Nenhuma experiência prévia é necessária. Web3 & DApp Development Fundamentals no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 4 de 4.
Quanto tempo leva a aula “Registros distribuídos”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de Web3 & DApp Development Fundamentals?
Sim. Cada aula de Web3 & DApp Development Fundamentals inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- Blocos e cadeias
- Árvores de Merkle
- Hashing em blockchain
- Registros distribuídos