Frequently Asked Questions

Below you will find answers to our most frequently asked questions for the Moonstone wallet.
  • Technical

  • Comparisons: What does Moonstone offer that blockchain.info doesn't? Blackcoin? Counterwallet? Omniwallet?

    Well, access to BitShares of course! But beyond that we have a timeline to add native Bitcoin support and through the integration of Metaexchange in-wallet cross-chain exchange. For V2 or 3 which is pretty close down the line we want to make it possible to verify your ID on the BitShares blockchain so you can trade legal fiat, stock, and bond IOUs from around the world.

  • Does Moonstone rely on a traditional centralized server, ever?

    The full blockchain is stored in our server (or any server you wish if we reach our goal). We cannot forge any transactions and cannot steal your funds. So yes, with V1 it relies on a central server-client setup.

    Yes. You will be able to import your existing wallet securely.

  • Will Moonstone allow me to access my existing BTS account info? Will Moonstone allow me to import my BTS (from Linux) json backup file?

    Yes. You will be able to import your existing wallet securely.

  • Will Moonstone allow me to stop using the Linux BTS client software and migrate to Moonstone exclusively?

    V1 of Moonstone won't support TITAN names. So complete migration will only be possible if you are ok with that. Future versions of Moonstone will be capable of doing TITAN transfers. There are some technical challenges we need to resolve first.

  • Do you intend to eventually allow the client to poll multiple independent servers in future versions so that any one server cannot lie to the client without getting caught?

    Yes. We intend to add this possibility down the line (V2 or 3).

  • Is this the same wallet you showed us last year, not sure when, in September maybe?
    What is the current status of the development, do you have a working implementation or are we only seeing mockups?

    The wallet design we showed in September was the first design iteration we had finished. I think this would be a good time to mention what the development/iteration process has been like so far:

    1. Initial design concepts based on Google's newly released Material Design guidelines. Frontend work on the Angular app with Famo.us. Famo.us made it possible to have a buttery smooth UI for browsers as well as on the phone. The premise is "build it once, it works on all devices like a native app". It worked really nicely but Famo.us was at version 0.2 back then and once they upgraded up to 0.4 we had to abandon our plans as it broke too many things. In this iteration we still used the current wallet RPC interface.

    2. This is when we started our second iteration of the design with complete overhaul. We put on a second designer and things went a lot faster. We switched from Famo.us to native Angular Material Design frameworks which also helped us a lot. The drawback is of course that for the mobile wallet we'll need to redo it again. We still used the current wallet RPC interface, though now server side as we changed plans for Moonstone to become a light wallet. This is also when we started doing extensive user testing with the half baked interface. We discovered that there would be a 80% drop in likelihood for anybody to use our wallet for every 2 minutes of waiting/loading time (this would include blockchain syncing if this was a full client).

    3. After wrangling with for over a month with the BitShares RPC interface and trying to get it to be a scalable backend for the light wallet, we decided that the whole current wallet architecture (including the deserializer) was simply not intended for large scale deployment. It was rather build with the ideological backdrop of everybody downloading the whole blockchain. This was when we made the announcements on the forum and started working on our own RPC interface and deserializer. Right after making the forum announcements we got the client-side universal transaction builder working, though there are still bugs that need to be worked out. We are currently working on the RPC interface/deserializer and the market interface. These two parts are also our two main milestones for the 0.9 release. Once fully tested we will release 1.0 for general use.

    What you saw in the demo video all works and is real, however the universal transaction builder needs work and testing as well as the RPC interface/deserializer. The current demo still runs on the current wallet RPC.

    It is important to note that we think Moonstone can spur the Startup/project econsystem around BitShares by providing a similar architecture to Bitpay's Bitcore Wallet Suite. That is our intention for our RPC interface. If it works out anything like Bitcore, you'll see many startups use it as the go-to BitShares/DPOS wrapper. Most Bitcoin startups we have worked with have used at least parts of Bitcore, which I think says a lot.

  • Is Moonstone a smartwallet?

    If I am not mistaken the smartwallet proposal includes automatic trading on your behalf. Things like that won’t be possible until V2 with the extension SDK. Then it will be possible to have a wallet daemon running on your computer or a remote server executing trades for you aromatically. Till then this is a simple wallet which awaits your commands.

  • So is this like a bridge from the bitshares decentral exchange to other central exchanges?

    It is the interface which combined the Bitshares exchange and external exchanges in one coherent interface.

  • Mobile

  • Is this wallet going to be tailored for mobile?

    Version 1 is going to be a web and desktop light wallet. However, the overall design and UI is mobile ready. We plan to start working on the mobile implementation right after V1 is crowdfunded and released.

Close