I do agree an alternative, simpler interface is needed. Perhaps you'd like to build something on my recently released new wallet template?

https://steemit.com/bitshares/@svk/new-simple-wallet-template

Using my graphenejs-lib I've made a new very basic wallet template. This wallet makes use of a new feature I've added to the graphenejs-lib: Account login. This is the same type of login used by Steemit, where a private key is generated on the fly from your account name and password. This means nothing is stored in your browser, and no private data is sent over the wire. This login feature could be reused by any number of wallets and you could then login everywhere using the account name and password.

Since your account name and password become your brain key in this case, it is important that you use a very long password, 16 characters at least. Remember: there's no centralised method of recovery so make sure you remember your password!

For more info, please see this post on steemit: https://steemit.com/bitshares/@svk/new-simple-wallet-template

You can find the source here: https://github.com/svk31/bitshares-wallet-template

And a live preview on the testnet here: http://svk31.github.io/bitshares-wallet-template

Can you go into the wallet management console under settings and check if you have multiple wallets there? If so, try changing between them and do a refresh to see if your account comes back.

When you only see the "Create account" button instead of Home, it means you have a wallet but no accounts.

In an attempt to make Bitshares/Graphene development more accessible for JavaScript developers, I've extracted the api and crypto libraries from the graphene-ui repo into a separate package. This package will allow anyone to easily connect to and interact with the Bitshares blockchain through either a public or local API server.

All the transaction creation/signing code used by graphene-ui is included, which means you can easily create a trading bot in node.js for example using this library. That bot would only need access to a private key and an api server, no cli_wallet required. This library should also make it very easy to implement alternative front-ends for Bitshares.

The library is available through NPM using npm install graphenejs-lib.

The open source code is available here, this repo also includes some basic examples:

https://github.com/svk31/graphenejs-lib

I intend to expand on the examples, so if there's anything you'd like to see an example for let me know.

Quote from: svk on June 03, 2016, 12:18:38 pm

No the wallet already handles fee pools and lets you pay the fee either in BTS or the asset you're looking to sell. If you have enough funds then I'm not sure what's going on here, perhaps try to switch the fee asset back and forth?


Sent from my iPhone using Tapatalk

Where do you see the "fee asset"? It doesn't give me the option when I try to place an order and I don't see anything similar in the settings section except "Preferred Unit of Account" (which I thought would only affect what "equivalent value" I have for each asset I hold).

Click on the asset name where you see the trading fees, it's a selector.

You can just ignore the verify thing, it doesn't actually do anything, just checks if you've typed the same as what was shown to you. As long as you write down the key and store it safely you're good, you have your backup.


Sent from my iPhone using Tapatalk

Yes the documentation is conflicted in more than one way ...

Anyhow I managed to setup the wallet and now bitshares-2 is syncing. When I do get_account bytemaster I can get the details so thats great. However I have an account registered for ex. bitshares3030 and it has a balance of 200+ BTS (account name is not real, just an example)

When I do get_account bitshares3030 account I can't see it. Should I upgrade my account to another type of membership to see it from my CLI and run my faucet on it? IF so how do I go about doing that? The account is accessible on openledger.info

Thanks again

If you're still syncing it could simply be because that account hasn't been created yet at the current state of your blockchain.

Thanks for the help!

In the guide that xeroc posted it says that I should run this code

Code: [Select]

git clone https://github.com/cryptonomex/graphene
mv graphene/ graphene-testnet
cd graphene-testnet/
git branch testnet
git remote set-url origin https://github.com/BitSharesEurope/graphene-testnet
git push origin testnet

Is this the right one or should I continue with Bitshares-2.0? I have also compiled from bitshares-2.0 before and had the same issue.

That example is only for the graphene testnet, it's a different blockchain used only for test purposes. If you're looking to connect to the Bitshares blockchain, you need to use the bitshares-2 repo I linked.