aljaz/python-teos
1
0
Fork 0
mirror of https://github.com/aljazceru/python-teos.git synced 2025-12-17 14:14:22 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fixes format for line breaks

Browse Source
This commit is contained in:
Sergi Delgado Segura
2019-12-09 19:23:57 +01:00
parent a8f4bfc1ee
commit 6a5a23a1d6
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
pisa/appointment.py
View File

@@ -9,12 +9,12 @@ class Appointment:
Args: Args:
locator (str): A 16-byte hex-encoded value used by the tower to detect channel breaches. It serves as a trigger locator (str): A 16-byte hex-encoded value used by the tower to detect channel breaches. It serves as a trigger
for the tower to decrypt and broadcast the penalty transaction. for the tower to decrypt and broadcast the penalty transaction.
start_time (int): The block height at which the tower is hired to start watching for breaches. start_time (int): The block height at which the tower is hired to start watching for breaches.
end_time (int): The block height at which the tower will stop watching for breaches. end_time (int): The block height at which the tower will stop watching for breaches.
dispute_delta (int): The `to_self_delay` encoded in the CSV of the HTLC that this appointment is covering. dispute_delta (int): The `to_self_delay` encoded in the CSV of the HTLC that this appointment is covering.
encrypted_blob (EncryptedBlob): An `EncryptedBlob` object containing an encrypted penalty transaction. The tower encrypted_blob (EncryptedBlob): An `EncryptedBlob` object containing an encrypted penalty transaction.
will decrypt it and broadcast the penalty transaction upon seeing a breach on the blockchain. The tower will decrypt it and broadcast the penalty transaction upon seeing a breach on the blockchain.
""" """
# DISCUSS: 35-appointment-checks # DISCUSS: 35-appointment-checks
@@ -86,8 +86,8 @@ class Appointment:
Args: Args:
triggered (bool): Whether the dispute has been triggered or not. When an appointment passes from the triggered (bool): Whether the dispute has been triggered or not. When an appointment passes from the
`Watcher` to the `Responder` it is not deleted straightaway. Instead, the appointment is stored in the DB `Watcher` to the `Responder` it is not deleted straightaway. Instead, the appointment is stored in the
flagged as triggered. This aims to ease handling block reorgs in the future. DB flagged as triggered. This aims to ease handling block reorgs in the future.
Returns: Returns:
appointment (str): A json-encoded str representing the appointment. appointment (str): A json-encoded str representing the appointment.