<p>Most thin clients only download, check and keep the block headers. They do not download the transactions of blocks, so they cannot fully verify blocks. </p>

<p>To learn about transactions they request information from full nodes which will send them a Merkle block for each transaction of interest. With the transaction and the Merkle block, the thin client can verify that <a href="https://bitcoin.stackexchange.com/a/32533/5406">the transaction was indeed part of the block</a>. When this transaction gets additional confirmations (i.e. more blocks get found building on the block this transaction was included in), the thin client assumes that the network accepted the block and that the block is valid.</p>

<p>There are also some thin clients that outsource verification to remote services such as mobile wallets of online wallet services.</p>

CC BY-SA 3.0
2016-12-15T17:08:49.887Z
I think the term 'thin client' is also used to refer to clients that outsource everything to a remote server.
Pieter Wuille
CC BY-SA 3.0
2016-12-15T17:10:31.820Z
Ah yeah, I keep forgetting about mobile wallets of online wallet services like blockchain.info…
Murch
CC BY-SA 3.0
2016-12-15T21:14:54.230Z
A thin client wouldn't outsource the safe keeping of private keys no? Whereas a mobile wallet like bc requires you to trust them for the safe keeping of your private key.
rny
CC BY-SA 3.0
2016-12-15T22:56:51.373Z
@renlord: maybe that's the relevant distinction.
Murch
CC BY-SA 3.0
2016-12-15T16:58:34.387Z
2016-12-15T17:16:06.830Z
2017-04-13T12:47:33.583Z
Murch
<p>How a thin node in network verify the validity of the blockchain tree? I think the node must wait for a time period to get the same valid block from some of its peers.</p>

<blockchain><thin-clients>
How a thin node ensures the validity of blockchain?
VaTi
# How a thin node ensures the validity of blockchain?

(Asked by: username_0 on 2016-12-15)

How a thin node in network verify the validity of the blockchain tree? I think the node must wait for a time period to get the same valid block from some of its peers.

**Tags:** blockchain, thin-clients


---

## 1 answers

### Answer by username_1 on 2016-12-15. Score: 3 | Accepted answer

Most thin clients only download, check and keep the block headers. They do not download the transactions of blocks, so they cannot fully verify blocks.

To learn about transactions they request information from full nodes which will send them a Merkle block for each transaction of interest. With the transaction and the Merkle block, the thin client can verify that [the transaction was indeed part of the block](https://bitcoin.stackexchange.com/a/32533/5406). When this transaction gets additional confirmations (i.e. more blocks get found building on the block this transaction was included in), the thin client assumes that the network accepted the block and that the block is valid.

There are also some thin clients that outsource verification to remote services such as mobile wallets of online wallet services.

> **Comments:**
> **username_2**: I think the term 'thin client' is also used to refer to clients that outsource everything to a remote server.  
> **username_1**: Ah yeah, I keep forgetting about mobile wallets of online wallet services like blockchain.info…  
> **username_3**: A thin client wouldn't outsource the safe keeping of private keys no? Whereas a mobile wallet like bc requires you to trust them for the safe keeping of your private key.  
> **username_1**: @renlord: maybe that's the relevant distinction.  

---

