• 0
Sign in to follow this  
deadthings

sendmany API call not working since ATLAS

Question

Ever since the ATLAS release at the end of August, I haven't been able to get sendmany to work properly with alqo-cli. It always throws the error...
 
error: {"code":-4,"message":"Insufficient funds."}
...even though I know with 100% certainty that the amounts being passed to it should be leaving 2 XLQ buffer for fees - which should be way more than enough, right? Has anybody else run into this issue and found a solution or workaround?
 
To reiterate - my sendmany script worked for many months just fine prior to the first ATLAS release, and then never again since.

Share this post


Link to post
Share on other sites

14 answers to this question

  • 0

FYI, even a series of sendtoaddress calls fails in the same way. The first few will go through, but the last ones will error out with the Insufficient funds message.

Share this post


Link to post
Share on other sites
  • 0

Your thread somehow was not marked as unread, therefore I must have missed it, sorry. I‘m not familiar with that command, but it might have changed since the Atlas update, due to the many changes in code. I‘ll check it and get back to you!

Share this post


Link to post
Share on other sites
  • 0

So sendmany is the cli equivalent of a multi-recipient transaction using the Qt. However, while a multi-recipient transaction using the Qt works perfectly well with the Atlas update, it does not using the cli. For some reason, it seems to misallocate inputs or fees, preventing the transaction from going through due to insufficient funds (even though, in reality, the funds are there). 

The same is also true of the much more common sendtoaddress  - which is just a good old fashioned send command. Works on the Qt, but not in the cli, with the same error as mentioned above.

edit - I should note that perhaps a contributing factor is that one of the inputs in the address from which I am attempting to send is locked for masternode collateral, in case you are trying to reproduce the error. But that's just a hunch, really - I have no evidence to support that.

Edited by deadthings

Share this post


Link to post
Share on other sites
  • 0

Checking in on the status of this inquiry. FYI, we are thinking of including Alqo as one the cyrptocurrencies accepted by a new online service we hope to launch in Q1 2019, but if we cannot automate send functions using alqo-cli, then we won't be able to integrate it. FWIW, send functions using bulwark-cli work fine, and Bulwark is based on a very similar codebase as Alqo. Also, as I noted previously, send functions using alqo-cli also worked fine until the Atlas release.

Share this post


Link to post
Share on other sites
  • 0

Hi deadthings,

 

Thanks for reporting this issue. I'll ask the team about it and try to get a clear answer. I know for sure that the team is totally focused on Bitfineon and the roadmap though, I understand that this bug could affect you and probably some other people but compared to Bitfineon, it has a low priority.

 

Thank you

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this