DVN Update 4

September 5, 2018 – As of September 5, 2018 we have added 4 batches of super data sources to our DVN. Please see below links for details on each batch uploaded.

DVN Update 4: https://medium.com/banyannetwork/banyan-network-dvn-update-4-77e11986d9cb

DVN Update 3: https://medium.com/banyannetwork/banyan-network-dvn-update-3-8a0e26e217b6

DVN Update 2: https://medium.com/banyannetwork/banyan-network-dvn-update-9efc0b3728dd

DVN Update 1: https://medium.com/banyannetwork/banyan-network-dvn-update-9c9edf9a55d1


First Paying Customer Landed

August 31, 2018

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.

Banyan Network fans can follow the BBN income at the following address: https://etherscan.io/address/0x358fbc8e5368956c9308b17fa5f054771d365b98

Customer Interface — Due to customer’s wishes, we have blanked out some information

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

Banyan Network Ambassador Program

August 22, 2018

Banyan Network hopes to become the world’s first Global Data Fusion Network, where large data sources will be fused and will be able to flow easily to customers who can benefit from this data.

Banyan Network has built a strong tightknit community that trusts us and truly believes in the project and we would like to continue growing our community globally by spreading word about our platform, which is why we are launching our new ambassador program.

Become an Ambassador

We are looking for people who are enthusiastic about Banyan Network and who also share our belief in the future of blockchain technology. Specifically we are looking for:

1. Video makers and Article writers to spread awareness of Banyan Network;

2. People to help us recruit other ambassadors;

3. People to host and attend meetups within the local community and lead social marketing events;

And any crypto enthusiasts, traders, and influencers who believe they can help us promote our platform in other ways.

Benefits of Being a Banyan Network Ambassador

  • Rewarded with BBN
  • Access to the Banyan Network team
  • Attend conferences and events with the Banyan Network team (We are planning global road shows in the near future)
  • Other BBN goodies and much more…

If you are interested, please apply to be a Banyan Network ambassador here.

Product Release of the Multi-Trust Connector

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

  1. 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.
  2. 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.
  3. The data source/service SVR verifies the authorisation key by requesting an authorised SVR → permission granted.
  4. The authorising SVR also saves the user’s authorisation request by making use of a smart contract that saves it on the blockchain.