<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1063935717132479&amp;ev=PageView&amp;noscript=1%20https://www.facebook.com/tr?id=1063935717132479&amp;ev=PageView&amp;noscript=1">


A virtual wallet & investor app for Bitcoin and Equibit cryptocurrencies using blockchain technology.

The Equibit Group formed with a focus on making capital markets more widely accessible with blockchain backing. So when they decided to create a full service trading platform for Initial Coin Offerings (ICOs), they knew they needed a partner who could help them see that vision come to life. Bitovi's team provided the ideal combination of user experience, design, and technology expertise to design and build the entire web interface that would make Equibit the platform of choice for trading.

The Project Goals

Our work on Equibit started by taking the time to understand and prioritize the high level product requirements and customer needs. This allowed us to map out a design and implementation plan to focus in the following areas:

  1. Create a robust way for users to access the application, without sending passwords or any login information to the server
  2. Design the user experience for trading securities based on an "Atomic Swap", in which users exchange one cryptocurrency for another without the need of a third party

Our Design Process

Style Guide Driven Design

The first priority for the design was to define the authentication flows, including login, registration and forgot password. For this we sketched flow maps and iterated until landing on the right approach. To aid this process we created interactive prototypes that simulated what the user would see at every step of the process. Because we were more interested in the interactions than in the look and feel of the application, we used simple wireframes. This kept us focused on the flow, eliminating discussions about branding that weren’t relevant yet.

With the authentication flows defined, developers started to work on the implementation. During this time, our design effort turned to define the overall look and feel of the application using the Style Guide Driven Development approach - where a style guide is built as part of the application to drive the design and development process. Design decisions were documented in a living style guide as the styles were written, so as developers implemented the front-end, the application design fell into place naturally.

Equibit Style Guide

Equibit Style Guide

Equibit App

Equibit App Modal

Behavior Driven User Stories

With the UI requirements covered by the living style guide, we decided to use Behavior Driven User Stories to communicate UX requirements. This approach focuses on describing the requirements needed for a feature from the user’s perspective, adding details that would be traditionally left out by simple user stories and yet are critical for implementing and testing a feature.

Behavior Driven User Stories describe: 1) the scenario the user is in, 2) the actions the user can do in the given scenario, and 3) the outcomes such actions will trigger. This made it easier for the developers to understand and implement the user flows because they were more aware of the intended design. QA engineers also used them for testing user scenarios. This approach was also effective at filling gaps in the design. As our designer was documenting the interface, they had to break down each one into every applicable scenario, revealing areas that weren't accounted for. Overall, using behavior driven user stories was an efficient approach for our team to collaborate on the design and implementation - making life easier along the way.

Github Stories

Enhanced User Security & Privacy

As a platform where high-value assets are held and traded, Equibit understands that going the extra mile for security is key to building consumer confidence in it's product. The security features implemented in the Equibit wallet reflect a philosophy of minimal knowledge of sensitive information: The server should never receive user passwords and should refrain from tying addresses to user accounts except where necessary.

In Equibit's wallet, passwords are validated on the client side by signing a challenge token from the server. Even if the network channel can be decrypted by a third party, no password or reusable login information is broadcast over it. Working closely with the Equibit core development team, one Bitovi developer implemented this strategy from scratch in about 6 weeks.

Reset Password 2nd Auth
Backup Recovery Phrase

Example of UI mechanisms used in the application to communicate security features.

While trades of assets must tie users to Bitcoin addresses for legal and practical reasons, users still maintain privacy protections for any transfer and management of assets that do not involve public securities trades, even if the entire database is leaked to hackers or investigators. No keys are held in the clear on Equibit servers; transaction signing and key derivation are done exclusively in the browser. Addresses are only stored on the server as part of trade offers, so any other addresses found on the blockchain cannot be identified to relate to any user in Equibit. As an ongoing concern, Bitovi developers are careful to not introduce features or implementations which would threaten this privacy protection.

Atomic Trades Across Blockchains

A key innovation on the Equibit platform is the "atomic swap," or the ability for two parties to trade assets that sit on two different blockchains, without one party being able to exploit the blockchain's lack of knowledge about either one. The key technology enabling this is the Hash- & Time-locked Contract (HTLC), in which each party first locks assets on the two blockchains and then collects the other party's assets. Below is an example conversation of how two actors named Alice and Bob might communicate a hash-locking trade in plain English:

  1. Alice: "Bob can spend these Equibits if he proves he knows this secret."
  2. Bob: "Alice can spend these Bitcoins if she proves she knows that same secret."
  3. Alice: "OK. Here's the secret. I'm spending those Bitcoins."
  4. Bob: "Cool. Here's the secret that Alice revealed. I'm spending those Equibits."

But if either party can't complete the transaction, or the secret is lost, those assets could never be spendable again. To protect against this, a time lock is added to each of the locking scripts that lets Alice or Bob collect refunds from only the assets they themselves have previously locked.

Atomic Trade

Because of the importance of users seeing this process through to completion, our team focused on ensuring that the presentation of information is current, polished, and easy for users to understand. Despite the size and complexity of this feature, our team converted a technical demo of the underlying transaction construction into a complete feature ready for user acceptance testing in three months.

  1. Alice: "In addition to Bob & the secret proof, I can spend these Equibits instead if too much time passes."
  2. Bob: "In addition to Alice & the secret proof, I can spend these Bitcoins instead if half as much time as Alice's interval passes."
  3. Time passes, Bob's time lock expires.
  4. Bob: "I'm spending those Bitcoins now that enough time has passed."
  5. More time passes, Alice's time lock expires.
  6. Alice: "I'm spending those Equibits now that enough time as passed."


Bitovi’s expertise allowed the Equibit Group to built a feature rich application in the blockchain that is scalable and maintainable. The next step is to complete additional features that will further empower issuers and investors, such as passport restricted trades, in-app communication with investors, and the ability issue, manage and pay distribution to shareholders.

Can we help you make an amazing app too?

Contact us and let's create something amazing.