The context
With the rise of digitalisation, the amount of transactions you can do on Internet has been growing exponentially. So has been the need for trust. Online trust depends merely on two conditions: to prevent fraud, we need to prove that we are the person we pretend to be. And then we need to prove that we can meet our part in the contract (payment, delivery,...) 
From certificate chains to social rating, a lot of solutions have emerged over time in this domain. But each company, each actor, is setting up its own strategy in a separated way. As a result, we end up dealing with endless amount of passwords and accounts. Initiatives are emerging to simplify this and to build trust between services. People can for example login to many websites using their Facebook or Google account.
But this is not secure, and not fair. The more we mutualise our accounts, the more we feed vast databases. And behind them, we supply machines controlling what advertising we see, what news reach us, who are our friends... Databases that can sometimes get attacked, creating gigantic data leaks and related fraud.
The project
Brickchain offers a decentralised infrastructure to improve trust and security. 
Example - In countries where alcohol consumption is restricted, people need to prove their age online before they can buy a bottle of wine. In store, you would show your ID card, but online, how do you prevent fraud? And why would you share your full identity with the online shop every time?
In the Brickchain ecosystem, people get their identity verified once by an official authority. Then the identity proof is divided in smaller information pieces. To buy alcohol online, people share their age proof signed by the official authority.
In this example, the signing authority becomes more important than the information itself. This is the key of the infrastructure. Another example. If two banks decide to trust each other, making online payment or opening an account becomes much simpler and cost-efficient. For businesses, this approach is also very beneficial. It reduces maintenance costs, fraud risks, and legal responsibilities.

The challenge
Integrity is the mobile application at core in this infrastructure. It works like a digital wallet. People keep their verified information in their phone, and only share what is necessary to access services. It is somewhat the door to our service infrastructure. 
The challenge for us with Integrity was to design and sell a product that will function with a network of players yet to come. How to explain to non-technical people the value of decentralisation, data portability or advanced cryptography? How to sell an application that will access services non built yet? How to address three different target audiences: the potential business partners, the developer community and our potential end-users?
We decided to divide our communication through three channels: the Brickchain website describes the infrastructure and the protocol, the developer portal contains all the open-source documentation, and the Integrity website provides explanations and articles to a less technical audience.
To be more pedagogic on the website, we decide to develop some illustrations that will explain our different usecases. This exercise also forces us to describe practical situations.
We believe that using illustration on our site has reinforced our identity, and helped us creating context around our different usecases. It roots our project in everyday situations and enables us to tell stories people can relate to. 
at a more personal level, this decision was a little bit of a bet, as I did not have a strong illustration or branding background. It remains a great occasion for me to practice on my visuals skills, deepen my culture and my craft. 
Back to Top