Difference between revisions of "Watchtowers"

From lightningwiki.net
Jump to: navigation, search
Line 5: Line 5:
 
= Workings =
 
= Workings =
 
At a high level, the lookout service receives input via two sources: block events and it's database. Incoming state updates are continually written to the database, and are made available to the lookout as soon as the tower successfully persists the encrypted blob. As new blocks come in, the tower searches for any breach hints matching the txid prefixes contained in the newly found block. If any matches are generated from the query, the lookout service will dispatch an attempt to decrypt and sweep the transaction on behalf of the user.
 
At a high level, the lookout service receives input via two sources: block events and it's database. Incoming state updates are continually written to the database, and are made available to the lookout as soon as the tower successfully persists the encrypted blob. As new blocks come in, the tower searches for any breach hints matching the txid prefixes contained in the newly found block. If any matches are generated from the query, the lookout service will dispatch an attempt to decrypt and sweep the transaction on behalf of the user.
 +
  
 
== Lookout part==
 
== Lookout part==
Line 11: Line 12:
 
== Watchtower / server , standalone ==  
 
== Watchtower / server , standalone ==  
 
Receives and stores encrypted blobs from clients, this represents that second primary service enabling the tower to act on behalf of the tower's clients.
 
Receives and stores encrypted blobs from clients, this represents that second primary service enabling the tower to act on behalf of the tower's clients.
 +
 +
=  Fees =
 +
Watchtowers have a "sweep fee". The way watchtowers work is that you give them an encrypted Bitcoin justice transaction getting your funds back in the case of a breach. When they see that evil thieving transaction on the chain, that transaction reveals the decryption key and they decrypt and broadcast the transaction.
 +
 +
  
 
= LND =  
 
= LND =  

Revision as of 06:13, 21 August 2019

Watchtowers make mobile wallets more powerful (or wallets that are not online 24x7). They keep track of channels for the client.

There is a nice podcast with Conner Fromknecht about it: https://stephanlivera.com/episode/83

Workings

At a high level, the lookout service receives input via two sources: block events and it's database. Incoming state updates are continually written to the database, and are made available to the lookout as soon as the tower successfully persists the encrypted blob. As new blocks come in, the tower searches for any breach hints matching the txid prefixes contained in the newly found block. If any matches are generated from the query, the lookout service will dispatch an attempt to decrypt and sweep the transaction on behalf of the user.


Lookout part

Handles the responsibility of monitoring the chain for possible breaches and responding by decrypting and broadcasting any justice transactions that its clients had previously uploaded.

Watchtower / server , standalone

Receives and stores encrypted blobs from clients, this represents that second primary service enabling the tower to act on behalf of the tower's clients.

Fees

Watchtowers have a "sweep fee". The way watchtowers work is that you give them an encrypted Bitcoin justice transaction getting your funds back in the case of a breach. When they see that evil thieving transaction on the chain, that transaction reveals the decryption key and they decrypt and broadcast the transaction.


LND

LND had watchtowers since 0.7. You need to add make install tags=watchtowerrpc to your make command to enable the rpc commands.

Status

Template:INFO:LND 0.7-beta has (altruistic) watchtowers