We are very excited to announce that we have acquired our first customer paying with BBN.
The customer will be paying with BBN for use of our DVN to serve the financial sector.
Our customer deposited a one time payment of 1.1 million BBN to access the following 13 data sources on the Banyan Network. (We have plugged in more data sources to our DVN that are not yet updated on our Medium. We will provide detailed information on these data sources in our DVN update 4 tomorrow.)
Query of Personal Consumption Portrait
Authentication of Bank Card
Authentication of Mobile Phone Number
Query of Positioning Spacing (Designated Address)
Query of Positioning Spacing (Designated Latitude and Longitude)
Query of Debt Information
Query of Lending Blacklist
Query of Lending Whitelist
Query of Overdue Loans
Comprehensive Loan Report
Loan Application Behaviour Report
Loan Credit Status Report
Loan Behaviour Report
The BBN income generated by our customers will enter a smart contract and will be locked for 1 year. At the end of the lock up period, the community gets to decide the fate of these BBN, either they re-enter to circulate in the market or become destroyed.
The above image is our customer user interface displaying a summary of our first customer’s expenditures. This page shows which data sources have been accessed, the number of times each data source has been accessed and the BBN paid per data source. Due to our customer’s wishes, we have blanked out some information including the company name and the detailed breakdown of the data sources they are accessing.
Full Update here: https://medium.com/banyannetwork/first-paying-customer-landed-5fd327daba28
August 23, 2018 – Banyan Network (BBN) has now been listed on both Bitfinex and Ethfinex as a result of finishing #1 on the Ethfinex Token Voting Round. Trading will commence with ETH/BBN and USD/BBN trading pairs.
Please see more information here: https://www.bitfinex.com/posts/273
May 8, 2018 — The Multi-Trust Connector (MTC) is a technical solution for user data permission and authorisation, which is the most important regularisation related module in our data service network. The MTC records every user’s data permission and writes the metadata (Merkle tree root node) on the blockchain, ensuring the transparency, tamper resistance as well as privacy protection.
For example, when user ‘C’ applies for a loan from a financial institute ‘B’, the institute would request personal data of the user from credit agency ‘D’ in order to assess and manage risks. Such data request (from ‘B’ to ‘D’) needs permission from ‘C’ beforehand, in order to gain access to the data. The traditional way of doing this is for ‘B’ to acquire authorisation and keep the record themselves, usually relies on (paper) documents. Hence ‘D’ is not able to verify it in real-time and can’t be ensured of the record authenticity. MTC provides authorised technical solutions for user ‘C’, financial institution ‘B’ and credit agency ‘D’, saving the authentication and authorisation data on the blockchain. All the user’s data authorisation behaviour is written on the blockchain through smart contracts . To ensure that the authorisation is open and irrevocable.
We’ve collaborated closely with MTC’s pilot clients on the product design and development. There are two modules of MTC:
1. the permission management SaaS tool; and
2. authorization service API infrastructure.
The development of the first version of the above two are finished.
In this month, we will release the beta version of MTC, and integrate the product with our pilot clients. We will also open the source code of MTC, test the product with our industry partners, and develop smart contracts for MTC.
Mutual Information Technology Framework
The authorisation Software Devlopment Kit (SDK) provides the authorisation interface and the application. With the app, the user sends an authorisation to the authorised server (SVR). Through the SDK authorisation interface, the user will on their turn receive the authorisation key.
When the application extracts a user’s data to the data source/service SVR, it needs to comply with the authorisation key at the same time.
The data source/service SVR verifies the authorisation key by requesting an authorised SVR → permission granted.
The authorising SVR also saves the user’s authorisation request by making use of a smart contract that saves it on the blockchain.