Sergi Delgado
Sergi Delgado
A system monitor based on logs should be created so the system state can be checked. The goal is to be able to check: - The number of requests received...
In the current version of BOLT13, appointment deletion can be requested by the user in order to free slots that may match an already closed channel. Given a user has...
Following the current version of [BOLT13's draft](https://github.com/sr-gi/bolt13/blob/master/13-watchtowers.md#the-delete_appointment-message), the user should be able to delete appointments from the tower. The goal of deletion is to free space in ongoing subscriptions for...
Continuing #154 here
At the moment the tower is free of charge. However, in order to offer the tower as a service payments for storage + monitor is most likely going to be...
Currently the tower service is offered for free. However, the goal is integrate BOLT11 invoices in the response of the register message as a payment wall if subscriptions are being...
At the moment we're offering the service over HTTP/HTTPS. Eventually we should move to having it offered both via LN and HTTP over Tor. The former is more challenging since...
TEOS accepts multiple appointments with the same locator and handles them. This is desired since not doing so would make TEOS susceptible to appointment replacement and appointment front running attacks:...
When the `zmq_subscriber` was adapted from the [Bitcoin Core example ](https://github.com/bitcoin/bitcoin/blob/master/contrib/zmq/zmq_sub.py) the async approach was taken out and replaced by a threaded-based approach (each instance of the `zmq_subscriber` is created...
As discussed in #22, jobs are retied if the transaction associated to the job misses too many confirmations. A special behaviour should be defined in case this retry counter becomes...