Branding progress

We are getting closer to the launch of the branded version of BCShop. More than 50 pages of the platform were redesigned or added. Our goal, besides making BCShop look better, is to improve every aspect of users experience and simplify learning curve for users not very much familiar with Ethereum blockchain.

Today we want to share some of the branded pages with you.

The main page

As you can see, it is much more easier to understand what is the platform about as well as navigate different functionalities.

Personal zones

With the visualization of every menu item, personal zones (dashboard in the past) look less cluttered up and appealing. We introduced two separate personal zones: for buyers and for sellers so every visitor of the platform can see BCShop functions relative to his/her role and can easily switch it, if needed.

How it works

As an implementation of the feedback of the current version, comes new How It Works section. The purpose of the section is to provide the easiest way to transform users’ intentions into actions. At the same time we aim BCShop to be newbies friendly so there will be separate blog post covering each topic in accessible and detailed way.

Growth hacking launched

In March we launched our cooperation with the growth hacking partners. The 5 months cooperation covers many topics including marketing and sales, PR coverage, SEO, community growth strategy and referral strategy.

In the following months, as technical development is reaching the release milestone, we expect a lot more activities coming for BCShop!

Conference attendance

In March we visited two conferences in Zug, crypto capital of the world. The global shift from speculative to fundamental values in blockchain industry becomes more and more obvious. Compared to events we visited last year, there were many more representatives from foundations, regulators, banks as well as lawyers and established projects who have or are about to have working products.

A lot of networking with dedicated people supports our beliefs in blockchain tech becoming wider adopted as time goes on.

Receipts

New feature to be implemented in near future is called Receipts. It is a notification (an email, to be exact) that merchant receives when purchase is completed and no actions could be made to change its state.

Such situations may include:

1. Simple, non-escrow-protected purchase. When customer makes a payment, it becomes completed;

2. If deal is escrow-protected, receipt is sent when

2.1 Customer confirms the offer or product was received

2.2 Complaint was resolved with any result.

2.3 Complaint time expired and merchant can withdraw the payment.

In all these cases a special email is sent to the merchant that contains a deal’s time and date, an offer or product purchased and amount paid.

Product links

So far all the links to offers and products contained a number identifying the product (https://bcshop.io/buy/2). That approach has its benefits: the link is quite short and readable, it is easy to memorize. But there are some drawbacks too. For example, you open information about your project’s inner structure to outer world. So we decided to change the link’s format. Instead of number it will contain a symbol code that maps to the old numeric identifier, for example https://bcshop.io/buy/zdy38d3c. Please don’t forget to update this information if you shared your offers with customers.

Cache layer improvements

This month we introduced another upgrade for the Caching layer. As you might know, earlier it was expanded to cache not only events, but also purchase states: back sync process updates purchase records until they become ‘final’, and it also creates new purchase state records when specific event is detected. You may read our January report for more information on that topic.

Our tests showed that such straightforward way can easily become very slow if number of ‘non-final’ purchases grows. And that is what can be expected in real-life circumstances.

When new purchase appears in the blockchain, back sync puts it into a queue to wait for updating its state.

If the queue is rather long, then it can take long time to process it all and detect a new record waiting to be cached. However adding new records is way more important than processing old ones. For example, adding new purchase to the list of purchases on website is more prioritized task to compare with changing status from Paid to Complain. That’s why processing of new purchases was moved to separated task.

Now new purchase first goes to so-called ‘new purchases’ queue where back sync process caches it and later it may appear in the ‘non-final purchases’ queue, if it is escrow protected and is in Paid state, for example.

That is the way to achieve better performance and make the website more responsive.

About BCShop.io

BCShop.io project aims to reinvent the way digital commerce and payments work today. Focusing on digital goods and services area project’s goal is to enhance it with fast-growing opportunities blockchain technologies and cryptocurrencies have to offer. In January 2018 BCShop.io hit hard cap of 2000 ETH at its token sale.

Website: https://bcshop.io/

Twitter https://twitter.com/BCShop_io

Telegram https://t.me/bcshopio

Facebook https://www.facebook.com/BCShop.io/

Business Inquiries [email protected]