Mats Jerratsch
Mats Jerratsch
## Describe the issue Since updating to the latest version of bitcoin abc the gettransaction RPC endpoint returns absurdly high values for fees. ### Can you reliably reproduce the issue?...
BlockchainWatcherImpl implements the general behaviour of watching the blockchain and detecting if the anchor has been spent. What is still missing is analysing the status quo when detecting a spent...
# Addresses in LN So far thunder nodes have been quite altruistic when relaying payments. That is, they would not dare to take a payment, even though they perfectly could....
If the connection drops between exchanging `LNPaymentMessageD` the one node that sent and received it already thinks everything is ready to go and done, while the other node does not...
Due to transaction malleability, the commitment transaction that allows refunding the anchor can not reliably built. I discovered there is a branch for SegWit integration into bitcoinJ https://github.com/bitcoinj/bitcoinj/pull/1171 It does...
Closing a channel currently only closes down the payment channel. The rest of the network does not get informed about that channel not being active anymore. We need to broadcast...
Currently everything is just saved in memory using InMemoryDBHandler, which basically just mocks a database. For actual usage we obviously need a way to persist state across application restarts. Possibilities:...
Currently we are directly routing towards a public key, which can easily fail when we don't have a route to a specific wallet in our database. Routing towards a 24/7...
This finishes the move completely away from ConnectionManager doing business logic against the running connections and being responsible only for building and maintaining connections as necessary. I suppose the easiest...
Possibly before doing the encryption handshake we need to have some kind of version handshake. We need to transmit which network the node operates on (main, test3, seg, ...) Furthermore...