Skip to content
This repository has been archived by the owner on Feb 10, 2022. It is now read-only.

QBitNinja adn NBitcoin not working #71

Open
TarasKryvko opened this issue Aug 5, 2018 · 5 comments
Open

QBitNinja adn NBitcoin not working #71

TarasKryvko opened this issue Aug 5, 2018 · 5 comments

Comments

@TarasKryvko
Copy link

TarasKryvko commented Aug 5, 2018

I have lots of user addresses, and when i want to check address transaction i use QBitNinja like this:

       foreach (var uAddrModel in userAddresses)
        {
            BitcoinAddress btcAddr = BitcoinAddress.Create(uAddrModel.Address, CurrentBtcNetwork);
            BalanceSelector balSel = new BalanceSelector(btcAddr.ScriptPubKey);
            BalanceModel btcModel = client.GetBalance(balSel, false).Result; //here i get result which says 
            //that balance does not have operations, but i just recharged this specific address


            if (btcModel.Operations.Count == 0)
            { continue; }
            foreach (var operation in btcModel.Operations)
            {
                if (operation.Amount <= 0)
                { continue; }
                bool isApproved = await CheckIfTxApprovedAsync(operation.TransactionId.ToString());
                if (!isApproved)
                {
                    isSuccess = await ApproveOperationAsync(operation, uAddrModel);
                }
            }
        }

The problem is not with my code, it worked ok, but in some reason today it is not working, i really do not know what to do, and also i do not know other ways to send bitcoin.

Also when i want to send bitcoin i get this very strange result
nbitcoin issue

Please help.

@NicolasDorier
Copy link
Contributor

NicolasDorier commented Aug 6, 2018

I am right now migrating QBit on a new server. Other function, except broadcast should work right now.

@TarasKryvko
Copy link
Author

So that's why i could'nt send transaction yesterday? Because i have just tried and it worked.

@NicolasDorier
Copy link
Contributor

Maybe. My server is very flaky and very old, will migrate today to a new one.

@TarasKryvko
Copy link
Author

Got it, thanks. So when you migrate to new one, such problems shouldn't appear, right?

@NicolasDorier
Copy link
Contributor

yep

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants