You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noticed then when elecrtum was returning an error (missing tx probably due to electrum node being out of sync) the channels just never become usable. If any of the promises fetching tx data return an error should we should flag the whole sync as a fail? In some cases the tx might not have propagated yet I guess.
Also should we force getTransactionData to differentiate between an error and a missing tx?
'Unable to retrieve transaction data from the getTransactionData method.',
Electrum response: {"id":0.21657926857935722,"error":false,"method":"getTransactions","data":[{"jsonrpc":"2.0","error":{"code":2,"message":"daemon error: DaemonError({'code': -5, 'message': 'No such mempool or blockchain transaction. Use gettransaction for wallet transactions.'})"},"id":8,"param":"2b9eb794af7793290e999d9c66d2f48a391e8575adfd7a8114f5a2fe159eda01","data":{"tx_hash":"2b9eb794af7793290e999d9c66d2f48a391e8575adfd7a8114f5a2fe159eda01"}}],"network":"bitcoinRegtest"}
The text was updated successfully, but these errors were encountered:
Noticed then when elecrtum was returning an error (missing tx probably due to electrum node being out of sync) the channels just never become usable. If any of the promises fetching tx data return an error should we should flag the whole sync as a fail? In some cases the tx might not have propagated yet I guess.
Also should we force
getTransactionData
to differentiate between an error and a missing tx?react-native-ldk/lib/src/lightning-manager.ts
Line 371 in 49109e2
Electrum response:
{"id":0.21657926857935722,"error":false,"method":"getTransactions","data":[{"jsonrpc":"2.0","error":{"code":2,"message":"daemon error: DaemonError({'code': -5, 'message': 'No such mempool or blockchain transaction. Use gettransaction for wallet transactions.'})"},"id":8,"param":"2b9eb794af7793290e999d9c66d2f48a391e8575adfd7a8114f5a2fe159eda01","data":{"tx_hash":"2b9eb794af7793290e999d9c66d2f48a391e8575adfd7a8114f5a2fe159eda01"}}],"network":"bitcoinRegtest"}
The text was updated successfully, but these errors were encountered: