<p>In order to correctly show balance and be able to create new transactions, a thin client needs the following information:</p>

<ul>
<li>Current block number</li>
<li>OutPoint information - hash of the incoming transaction and position of the output relevant to the client.</li>
<li>Signature script, as it needs to be included in a Tx</li>
<li>Amount of Bitcoins send/received in the given transaction</li>
<li>Block number in which the transaction was included (for knowing the amount of confirmations)</li>
</ul>

<p>(Does anyone have an idea what else could be useful or needed?)</p>

CC BY-SA 3.0
2011-12-30T19:26:48.223Z
2011-12-30T19:26:48.223Z
ThePiachu
<p>What are the bare data necessities that a lightweight client would have to get from a server client in order to perform basic wallet tasks (show balance, transaction history, number of confirmations, send coins)?</p>

<p>For example, a simple, light client could store all Txs where any of the given addresses from the wallet were used, but one could also try trimming all data from those Txs that aren't related to their addresses.</p>

<p>What is the bare minimum of data a client needs in order to function?</p>

<transactions><client><thin-clients>
Lightweight client, bare necessities
ThePiachu
# Lightweight client, bare necessities

(Asked by: username_0 on 2011-12-30)

What are the bare data necessities that a lightweight client would have to get from a server client in order to perform basic wallet tasks (show balance, transaction history, number of confirmations, send coins)?

For example, a simple, light client could store all Txs where any of the given addresses from the wallet were used, but one could also try trimming all data from those Txs that aren't related to their addresses.

What is the bare minimum of data a client needs in order to function?

**Tags:** transactions, client, thin-clients


---

## 1 answers

### Answer by username_0 on 2011-12-30. Score: 2 | Accepted answer

In order to correctly show balance and be able to create new transactions, a thin client needs the following information:

* Current block number
* OutPoint information - hash of the incoming transaction and position of the output relevant to the client.
* Signature script, as it needs to be included in a Tx
* Amount of Bitcoins send/received in the given transaction
* Block number in which the transaction was included (for knowing the amount of confirmations)

(Does anyone have an idea what else could be useful or needed?)


---

