---
# System prepended metadata

title: Lite Client Demo Video Overview

---

# Lite Client Demo Video Overview

## General Points

Let's use testnet only for the whole demo - no regtest as that is to much to learn about at the same time.
Separate out the components differently:
 - LiteClient = headersv & payd
 - ProxyServer = dp3 & peer-channels & paymail
 - Strip out the Miner folder, too complicated

pipe json output to jq to view more clearly

show that it can be used without paymail and paymail is just a layer of service discovery. We can have 2 chapters, one without paymail and one with

explain they don’t need to run the proxy servers themselves and in future can pay for those services

peer channel is so that wallets don’t need to run a server themselves to receive the callback from the miner. The cherry on top is that multiple people can get the merkle proof but not the main reason

max 5 to 10 min video overview will be good enough

Host the Cat Store (we already do this) but in testnet mode. Then get people to use it by grabbing funds from the Faucet, sending to the Customer Wallet and purchasing a random cat.

## Topics to cover & in what order, check as recording is complete

- [ ] Overview of the Lite Client components working together
- [ ] Block Headers Client
- [ ] Payd
- [ ] Setting up testnet credentials with TAAL console
- [ ] DP3
- [ ] Paymail
- [ ] Peer Channels
- [ ] Cat Store Demo

# Rough Script

## Overview of the Lite Client components working together

As BitcoinSV blocks become larger, and transaction throughpout increases respectively, the associated cost of running a full node for application or exchange purposes only becomes intolerable. The full node software is really only suitable for block producing nodes, known as miners.

Entities who do not plan to produce blocks themselves should run the Lite Client tools in order to facilitate *their businesses' use* of the blockchain; rather than running the full node software, which is predominantly designed to process transactions for *others*.

Big picture is we want to create and validate transactions without keeping the whole utxo set and entire blockchain. 

This can be achieved by maintaining a copy of the block headers only, and when sending transactions, including their ancestry, and their merkle proofs. Ancestry refers to the full transactions associated with each input. Merkle proofs attest to their inclusion within a valid historic block.


## Block Headers Client



## Wallet

Other things to say

### PayD

Other things to say

## Setting up testnet credentials with TAAL console

Other things to say

## DPP

Other things to say

## DP3 (DPP Proxy)

Other things to say

## Paymail

Other things to say

## Peer Channels

Other things to say

## Cat Store Demo

Other things to say