mirror of
https://github.com/aljazceru/python-teos.git
synced 2025-12-17 22:24:23 +01:00
80 lines
3.6 KiB
Python
80 lines
3.6 KiB
Python
from pisa.rpc_errors import *
|
|
from pisa import bitcoin_cli
|
|
from pisa.logger import Logger
|
|
from pisa.utils.auth_proxy import JSONRPCException
|
|
from pisa.errors import UNKNOWN_JSON_RPC_EXCEPTION
|
|
|
|
logger = Logger("Carrier")
|
|
|
|
|
|
class Carrier:
|
|
class Receipt:
|
|
def __init__(self, delivered, confirmations=0, reason=None):
|
|
self.delivered = delivered
|
|
self.confirmations = confirmations
|
|
self.reason = reason
|
|
|
|
def send_transaction(self, rawtx, txid):
|
|
try:
|
|
logger.info("pushing transaction to the network", txid=txid, rawtx=rawtx)
|
|
bitcoin_cli.sendrawtransaction(rawtx)
|
|
|
|
receipt = self.Receipt(delivered=True)
|
|
|
|
except JSONRPCException as e:
|
|
errno = e.error.get('code')
|
|
# Since we're pushing a raw transaction to the network we can get two kind of rejections:
|
|
# RPC_VERIFY_REJECTED and RPC_VERIFY_ALREADY_IN_CHAIN. The former implies that the transaction is rejected
|
|
# due to network rules, whereas the later implies that the transaction is already in the blockchain.
|
|
if errno == RPC_VERIFY_REJECTED:
|
|
# DISCUSS: what to do in this case
|
|
# DISCUSS: invalid transactions (properly formatted but invalid, like unsigned) fit here too.
|
|
# DISCUSS: RPC_VERIFY_ERROR could also be a possible case.
|
|
# DISCUSS: check errors -9 and -10
|
|
# TODO: UNKNOWN_JSON_RPC_EXCEPTION is not the proper exception here. This is long due.
|
|
receipt = self.Receipt(delivered=False, reason=UNKNOWN_JSON_RPC_EXCEPTION)
|
|
|
|
elif errno == RPC_VERIFY_ALREADY_IN_CHAIN:
|
|
logger.info("Transaction is already in the blockchain. Getting confirmation count", txid=txid)
|
|
|
|
# If the transaction is already in the chain, we get the number of confirmations and watch the job
|
|
# until the end of the appointment
|
|
tx_info = self.get_transaction(txid)
|
|
|
|
if tx_info is not None:
|
|
confirmations = int(tx_info.get("confirmations"))
|
|
receipt = self.Receipt(delivered=True, confirmations=confirmations)
|
|
|
|
else:
|
|
# There's a really unlikely edge case where a transaction can be reorged between receiving the
|
|
# notification and querying the data. In such a case we just resend
|
|
self.send_transaction(rawtx, txid)
|
|
|
|
else:
|
|
# If something else happens (unlikely but possible) log it so we can treat it in future releases
|
|
logger.error("JSONRPCException.", error_code=e)
|
|
receipt = self.Receipt(delivered=False, reason=UNKNOWN_JSON_RPC_EXCEPTION)
|
|
|
|
return receipt
|
|
|
|
@staticmethod
|
|
def get_transaction(txid):
|
|
tx_info = None
|
|
|
|
try:
|
|
tx_info = bitcoin_cli.getrawtransaction(txid, 1)
|
|
|
|
except JSONRPCException as e:
|
|
# While it's quite unlikely, the transaction that was already in the blockchain could have been
|
|
# reorged while we were querying bitcoind to get the confirmation count. In such a case we just
|
|
# restart the job
|
|
if e.error.get('code') == RPC_INVALID_ADDRESS_OR_KEY:
|
|
logger.info("transaction got reorged before obtaining information", txid=txid)
|
|
|
|
# TODO: Check RPC methods to see possible returns and avoid general else
|
|
# else:
|
|
# # If something else happens (unlikely but possible) log it so we can treat it in future releases
|
|
# logger.error("JSONRPCException.", error_code=e)
|
|
|
|
return tx_info
|