Error when transferring BTC from one address to another address

Error when transferring BTC from one address to another address

While creating bitcoin exchange, when transferring BTC from one address to another address, I got the following error:

[root@mail4 ~]# curl "http://localhost:3030/merchant/b95d272b-34fa-4cb5-8ca5-d5c1e0e29a97/payment?password=@1234567890#&to=b84a2cf1-fb7a-45dd-975c-3542ea1af64e&amount=10000&from=b95d272b-34fa-4cb5-8ca5-d5c1e0e29a97&fee=100100"
No destination set.
No origin set.
1515140164672 - error: ERR_BUILDTX
http://ift.tt/2Fu0p70

Comments

Post a Comment

Popular posts from this blog

Why the Coinbase customer support 1(855)750-0786 is always busy?

Why the Coinbase customer support 1(855)750-0786 is always busy? My account has been freezed. Last month i had same issue and support staff helped me to recover my money.But since two days i am facing same issue cannot transfer my funds.I tried calling Coin base support 1(855)750-0786 but all lines are busy and busy tone i am getting right now. https://ift.tt/2qbzPts
Read more

Activation of SegWit v1

Activation of SegWit v1 The segregated witness soft fork of August 2017 included a versioning field which would allow for future incrementation. Anthony Towns has recently posted an early draft of the proposal for the SegWit v1 upgrade to the mailing list . Although the devil is of course in the details, how could such an upgrade process look like? What are the different upgrade mechanism for the major [v1 - v16] and minor [v1.0 - v1.127] version changes? How is the soft fork signaled? How is the consensus change enforced? Is the v1 change as "contentious" and time consuming as v0 was? What are the tasks of node operators and miners? Thank you in advance for the answer! https://ift.tt/2VrPDpG
Read more

Coinbase Pro historical data not working

Coinbase Pro historical data not working I'm trying to pull historic data from the Coinbase Pro api using Python with the cbpro package. For some reason I either hit an error, or can only pull data from the last 350 days. If I run the following: import time import cbpro import csv import json import shutil import os start_time = time.time() end_time = start_time-(86400*300) public_client = cbpro.PublicClient() public_client.get_product_historic_rates('ETH-USD') data = public_client.get_product_historic_rates('ETH-USD', granularity=86400, start = start_time, end = end_time) Then I get an "invalid interval" error. If however I remove either the "start = start_time" or "end = end_time" part of the code I get the last 350 days worth of historic data. No matter ISO 8601 time I list as "start" or "end," I'm always get...
Read more