Issue with transaction on load balanced bitcoin back-end servers

We have setup two same bitcoin back-end server for load balancing purpose. We are facing an issue on transaction. Consider that a user X is going to perform a bitcoin transaction. user X is able to perform transaction successfully using SERVER 1 . When user X calls get our balance API he gets

bitcoinj and Lightning network

Hi everyone, currently I work on a Lightning network implementation which is intended to be used on lite clients such as mobile phones, a repo can be found here: https://github.com/btcontract/lnwallet and also recently I've made a demo if anyone is interested:

Get vps free - mine bitcoin free: 100 USD/day

100 usd/day - Bruteforce VPS and mine bitcoin with VICUMI 1.0 - Too easy to earn 100 usd/day! https://www.youtube.com/watch?v=iaR6rhrrgHQ https://drive.google.com/open?id=0B9cNZ8crZh57aFIzMG13R0xHT3M -- You received this message because you are subscribed to the Google Groups "bitcoinj" group.

Get vps free - mine bitcoin free: 100 USD/day

100 usd/day - Bruteforce VPS and mine bitcoin with VICUMI 1.0 - Too easy to earn 100 usd/day! https://www.youtube.com/embed/iaR6rhrrgHQ; frameborder="0" allowfullscreen> -- You received this message because you are subscribed to the Google Groups

Re: ECDSA compact signature

ECDSA signatures are expected to be different, because of the semi-random k-factor. Have you cross-checked your sigs for validity, so a sig produced with Intels library checked by bitcoinj and the other way round? On 06/29/2017 02:03 AM, Ghadi Shayban wrote: > Thank you for the bitcoinj library,