An example:

get_market_history BTS USD 3600 "2017-07-01T00:00:00" "2017-07-02T00:00:00"
Output:
get_market_history BTS USD 3600 "2017-07-01T00:00:00" "2017-07-02T00:00:00"
[{
    "id": "5.1.1768216",
    "key": {
      "base": "1.3.0",
      "quote": "1.3.121",
      "seconds": 3600,
      "open": "2017-07-01T00:00:00"
    },
    "high_base": 283,
    "high_quote": 6,
    "low_base": 129072761,
    "low_quote": 3173899,
    "open_base": 427095301,
    "open_quote": 10000000,
    "close_base": 129072761,
    "close_quote": 3173899,
    "base_volume": 1645300312,
    "quote_volume": 39864423
  },{
...
You have to be connected to a FULL node.

I'm also having the same problem now. None of the listed Full Node API servers are working. All are giving the "failed to sync with the API" error message.

There was an issue with the network couple hours ago. It's coming back up, my FULL node is being rebuild and should be back up shortly.

July Witness Update

Witness performace:



As a reminder from @abit to reduce RAM usage for witness nodes, set these parameters in config.ini (since version 2.0.170531)
track-account = "1.2.1"
partial-operations = trueThe witness RAM requirements are now under 2GB RAM.

Full Node:



The node was completely updated over the weekend. Additional parameters in config.ini (since version 2.0.170606) set to:

[code]partial-operations = true
max-ops-per-account = 1000
In the Peerplays telegram channel few days ago JB mentioned that Poloniex complained about the memory usage on their BitShares Full Node. I am not sure if this continues to be an issue (I would think that they should be able to afford a decent server to run BTS) but once again they are displaying their " BTS is currently under maintenance or experiencing wallet/network issues. Deposits and withdrawals will remain disabled until a solution is found, which may require an update from the BTS team. Any updates must be tested and audited before enabling." banner. As you can see from my snapshot above the Full Node runs at about 27.4GB RAM. As we continue to grow and with the latest mods to decrease the memory usage on witnesses, the Full nodes will have to do the heavy lifting for the infrastructure.

Haven't stopped into the referral system so far. With your own faucet you become the default registrar/referer for account create/upgrade, if there's no LTM account (or enough funds?) present in the wallets that uses your node to interface with the blockchain?

For the moment I have not switched to my own faucet. I use the OL's atm.  Setting up a faucet is on my to do list.

Witnesses aside, If the above is true, couldn't we use committee or worker proposals as a temporal fix by choosing full nodes to be included in upcoming light-wallet and bitshares.org/wallet releases?

I have already created an update to bitshares-ui on github for this. All new wallets should include the API access for my node. Some web wallets (OL) take only select updates and might not have it included.

Would that be incentive enough to run public full nodes and web wallets without running a business nor marketing, just the required infrastructure?

There is no incentive for it. For now only gateways really need them. But we definitely need more to provide a better experience for the users.

Last month there were no takers for my 1K BTS giveaway. So here is another chance:
Rules:
1. You have voted for my witness: sahkan-bitshares and kept your vote through at least 31 July 2017.
2. Giveaway runs through 31 JUL 2017
3. Be the FIRST to post below: "I'LL TAKE THE 1,000BTS!" and PM me your BTS account name.
4. I will send your BTS sometime during the first week of August.
5. If you are using a Proxy and the Proxy is voting on my witness you are eligible!
5. Good Luck!

Have a great BitShares July!

Let me rephrase this..

The help section states about the brainkey :

"If you never manually imported an account key into your wallet, you can alternatively backup your accounts and their funds by exporting the brainkey, a string of words from which your keys are derived deterministically"

What im trying to do is create a new wallet where i can determine my own brainkey and import the private of my existing account so that i could at the very least always restore my wallet on a new computer by simply remembering a phrase. However, according to the above statement i cant do that after importing the key to my new wallet.

I guess i could just transfer from one account to another, but is there a way to change the brainkey on an existing wallet?

I have not tested this myself, but under the light Wallet, SETTINGS, WALLET there is an option to reset your brainkey sequence. Maybe that will do what you need?

When running my self-compiled witness_node (the process of which also had certain issues I had to tediously correct manually) and pointing the Bitshares Light Client to it, I get a "Failed to sync with the API server" message.

The computer clocks are correct.

How do I fix this?

Is the message showing up because the blockchain has yet to sync to the latest available blocks?

Wait till your node syncs with the network then when you open your Light Wallet you should see an output from your node that it has opened a new DB or something similar. That way you will know that you connected to your node.

IMPORTANT

Sometime this weekend I will be running updates on my FULL node - API & web wallet server (dexnode.net). Please make sure that your wallets are backed up! It almost quadrupled in user connections since last update.

Quote from: iHashFury on June 26, 2017, 06:21:18 pm

I may set my proxy to bitcrab if you provide a price feed for bitBTC!

https://roelandp.nl/bitshareswitnesslog/?witness=jerryliu

With OPEN.BTC, bitBTC is not really needed. I believe that's his point, somewhat valid since we are duplicating BTC on the DEX.