<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Hyojun Kim on Medium]]></title>
        <description><![CDATA[Stories by Hyojun Kim on Medium]]></description>
        <link>https://medium.com/@therne?source=rss-5d8f4f28ad8a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tD4ZU86J25k_Ft592UuDHg.jpeg</url>
            <title>Stories by Hyojun Kim on Medium</title>
            <link>https://medium.com/@therne?source=rss-5d8f4f28ad8a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:05:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@therne/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Q1 Airbloc Technology Development Update]]></title>
            <link>https://therne.medium.com/q1-airbloc-technology-development-update-3416e8c81607?source=rss-5d8f4f28ad8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3416e8c81607</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[airbloc]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[english]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Hyojun Kim]]></dc:creator>
            <pubDate>Fri, 26 Apr 2019 10:05:52 GMT</pubDate>
            <atom:updated>2019-04-26T10:05:52.703Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ease-of-Integration with Enterprise Data Systems and Improved On-Chain Scalability of Data Exchange Process.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*t-Dz0SyIas9OI0z9T8Yw2Q.png" /></figure><p>Development updates can be dry so here’s what you need to know about Q1’s tech update in 30 seconds!</p><ol><li>Airbloc’s data architecture handling processes have been<strong> revamped to significantly improve the scalability</strong> of data registration and data exchange with <em>Merkle User Dataset (MUD)</em> technology. Cheers for data registration and exchange scalability!</li><li>Airbloc’s revised data architecture and back-end data pipelines are <strong>now</strong> <strong>capable of being integrated with enterprise data systems</strong> to facilitate enterprise-to-enterprise data exchange at scale. Cheers for ease-of-adoption!</li><li>We have <strong>redesigned the way we collect and categorize data</strong> to allow enterprises to register more granular types of user data. This allows Airbloc to collectively group incoming data under specific user profiles with 3 broad categories of Profile Data, User Events Data, and Identity Data, rather than randomized and uncategorized data types. More data types = more Airbloc use-cases.</li></ol><blockquote><strong>NOTE:</strong> The term “Enterprises” is used to refer to companies possessing personal data who are potential data providers or consumers on Airbloc’s consent-based real time data exchange platform.</blockquote><p>Curious about how we did it? Read on to find out more!</p><p><strong>ENABLING enterprise data registration at S-C-A-L-E with Merkle User Dataset Architecture implementation</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/0*BOq87-HVwJlITQV1" /><figcaption>The process of registering data on the blockchain using Merkle User Dataset</figcaption></figure><p>To drastically improve the data registration efficiency, we developed <em>Merkle User Dataset (MUD)</em> technology. MUD adopts a Sparse Merkle Tree (SMT) and a Nested Merkle Tree structure, which enables enterprises to register their data by simply uploading the Merkle Root only on the blockchain.</p><ul><li>Our previous data structure required enterprises to upload the entire list of the data onto the blockchain (which would have exerted tremendous stress on the blockchain), but MUD now has the benefit of allowing data providers potentially bundling millions of user data into 1 SINGLE Merkle Root in byte-sized data.</li></ul><p><strong>EXPANDING the types of data available for exchange through Data Architecture Refactoring</strong></p><ul><li>We are building an entirely new data architecture — one that is user-profile-driven compared to the previous architecture that was randomized and uncategorized. This new architecture allows Airbloc to collectively group incoming data under specific user profiles with 3 broad categories of Profile Data, User Events Data, and Identity Data, rather than randomized and uncategorized data types.</li><li>This new architecture also allows individuals to control their data usage at a more granular level and companies can manage and exchange more various kinds of data sets.</li></ul><p><strong>SIGNIFICANTLY improved data registration performance and speed by </strong><a href="https://github.com/airbloc/airbloc-go/pull/84"><strong>40x</strong></a></p><ul><li>Airbloc now relies on Parallel Data Processing rather than Single-Threaded Processing in its data collection pipeline. We conducted a private test of our new data collection processing capabilities with our enterprise partners in Q1, and found that <strong>data registration speed improved drastically by 4000%</strong>.</li><li><a href="https://github.com/airbloc/airbloc-go/pull/84">You can find more information on our Github</a>.</li></ul><p><strong>ENABLING real-time dynamic data exchange for enterprises with Data Exchange API implementation</strong></p><ul><li>We have introduced API data exchange as an additional method of data exchange. Before the introduction of API data exchange, Airbloc only permitted the exchange of static user attributes or datasets. With this new feature, it has the benefit of <strong>allowing dynamic and real-time and up-to-date data to be exchanged</strong>. This feature was introduced as it is more common for enterprises to exchange data via API, and hence easier for Airbloc to interoperate with existing enterprise data infrastructure.</li></ul><p><strong>ALLOWING Enterprises to Customize Their Data Purchase Request with Data Discovery API Implementation</strong></p><ul><li>We have integrated a Data Discovery API in Airbloc’s exchange platform to allow enterprises to search, build, and customize the data they wish to purchase, and receive a list of curated data available for purchase from a particular user segment.</li></ul><p><strong>ENSURING Consent-Based Data Exchange through Data Controller Node Implementation.</strong></p><ul><li>We have introduced a new <em>Data Controller Node</em> to monitor and ensure that data exchange can only occur when there has been expressed consent approval provided by individual users. This node also ensures that there are mechanisms in place to penalize actors that register and exchange data without proper user consent.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BqUcaMNrNKRmobNs" /><figcaption>Data controller node conducting a verification to ensure that data registered on Airbloc has been expressly consented by users.</figcaption></figure><h3>Join Our Official Community!</h3><ul><li><a href="https://t.me/airblocofficial"><strong>Telegram (KR)</strong></a></li><li><a href="https://t.me/airbloc"><strong>Telegram (EN)</strong></a></li><li><a href="https://open.kakao.com/o/gXIW11J"><strong>KakaoTalk</strong></a></li><li><a href="https://airbloc.org/"><strong>Homepage</strong></a></li><li><a href="https://fb.me/airblocofficial"><strong>Facebook</strong></a></li><li><a href="https://www.twitter.com/airblocofficial"><strong>Twitter</strong></a></li><li><a href="https://docs.google.com/document/d/1-xta_E2t2AHwvFodWg5aueQtcD4isnPHRQ6DscTq0dc/edit#"><strong>FAQ</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3416e8c81607" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Q1 Airbloc Technology Development Update]]></title>
            <link>https://therne.medium.com/q1-airbloc-technology-development-update-73fee27dab6d?source=rss-5d8f4f28ad8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/73fee27dab6d</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[korean]]></category>
            <category><![CDATA[airbloc]]></category>
            <dc:creator><![CDATA[Hyojun Kim]]></dc:creator>
            <pubDate>Fri, 26 Apr 2019 10:05:36 GMT</pubDate>
            <atom:updated>2019-04-26T10:05:36.454Z</atom:updated>
            <content:encoded><![CDATA[<h4>기업 데이터 시스템과의 용이한 연동 및 데이터 거래 확장성 개선</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*opSTkvDLw7xA1pm5mtgcxA.png" /></figure><p>에어블록 1분기 개발 현황을 공유합니다! 하지만 개발에 관한 긴 글을 읽기는 지루하실 수 있는 분들을 위해 20초안에 이해하실 수 있도록 먼저 알려드릴게요 :)</p><ol><li>데이터 등록의 확장성과 높은 볼륨의 데이터 거래를 위해 Merkle User Dataset(MUD)를 활용해 <strong>데이터 구조를 현저하게 개선</strong>했습니다.</li><li>에어블록의 데이터 구조 개선과 백엔드 데이터 파이프라인을 통해 <strong>기업의 데이터 시스템과 손쉽게 연동</strong>할 수 있을 것이며, 이를 통해 B2B 데이터 거래의 확장성을 키울 수 있게 됩니다.</li><li><strong>데이터를 수집하고 분류하는 방식을 재구축</strong>하여 기업이 더욱 세분화된 유저 데이터 타입을 등록할 수 있도록 했습니다. 이를 통해 에어블록은 수집되는 데이터를 프로필 데이터, 사용자 이벤트 데이터, 아이덴티티 데이터라는 3가지 카테고리로 그룹화할 수 있게 됩니다. 더 많은 데이터 타입은 더 많은 에어블록 사용 사례를 의미하겠죠? ;)</li></ol><blockquote><strong>Note</strong>: “기업”이라는 단어는 에어블록의 동의 기반 실시간 데이터 거래 플랫폼에서 데이터 공급자 및 수요자로 활동할 수 있는, 개인 데이터를 보유하고 있는 서비스/회사를 뜻합니다.</blockquote><p>본문에서 더 자세히 알아보세요!</p><p><strong>Merkle User Dataset 구조 개선을 통한 기업에의 데이터 등록 확장성 확보</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/0*Xz5bE5WyxNnDsuvl" /><figcaption>Merkle User Dataset을 통해 데이터를 블록체인에 등록하는 과정</figcaption></figure><p>데이터 등록의 효율성을 극적으로 개선하기 위해 저희는 Merkle User Dataset (MUD) 기술을 개발했습니다. MUD는 Sparse Merkle Tree (SMT)와 이중 머클트리 구조를 채택하여, 기업이 매우 작은 머클 루트 정보만을 블록체인에 올리고도 데이터를 등록할 수 있게 합니다.</p><ul><li>기존 데이터 구조에서 기업은 개별 데이터를 전부 블록체인에 등록해야 했습니다( 블록체인에 너무 많은 양의 데이터가 올라가게 되겠죠). 그러나 이제 MUD 기술을 통해 데이터 공급자 기업은 수백 만 건의 사용자 데이터를 단 1개의 머클 루트로 번들링할 수 있습니다.</li></ul><p><strong>데이터 구조 리팩토링을 통한 거래 가능한 데이터 종류 확장</strong></p><ul><li>대대적인 내부 아키텍쳐 리팩토링을 진행하고 있습니다 — 개별 데이터 중심 모델에서 벗어난 완전한 사용자 프로필 중심의 모델을 구축하기 위해서죠. 이를 통해 에어블록은 수집되는 데이터를 랜덤하고 미분류된 데이터 타입이 아니라, 프로필 데이터, 사용자 이벤트 데이터, 아이덴티티 데이터라는 3가지 카테고리로 그룹화할 수 있게 됩니다.</li><li>사용자는 데이터 활용을 더 자세한 레벨에서 통제할 수 있고, 기업은 더욱 다양한 데이터 셋을 거래할 수 있게 됩니다.</li></ul><p><strong>데이터 등록 속도 40x 증가</strong></p><ul><li>에어블록은 이제 데이터 수집 파이프라인에서 싱글 쓰레드 프로세싱이 아니라 데이터 병렬 처리를 이용합니다. 저희는 1분기에 기업 파트너들과 새로운 데이터 수집 과정으로 프라이빗 테스팅을 진행했으며, 그 과정에서 <strong>데이터 등록 속도가 4000% 개선</strong>되었습니다!</li><li><a href="https://github.com/airbloc/airbloc-go/pull/84">자세한 내용은 Github에서 확인하실 수 있습니다</a>.</li></ul><p><strong>API 형태의 데이터 거래 지원을 통한 기업과의 실시간 데이터 거래 가능</strong></p><ul><li>이제 저희는 동적인 API 형태의 데이터 거래를 새롭게 지원합니다. 이전까지, 에어블록에서는 오로지 정적인 사용자 속성이나 데이터셋만 다루었습니다. 이 기능을 통해 앞으로는 <strong>실시간으로 동적인 데이터를 거래</strong>할 수 있게 됩니다. 또한 기업간의 데이터 교환은 API 형식의 연동이 더 일반적이므로, 기존 기업 데이터 인프라스트럭쳐와 에어블록 프로토콜을 더 손쉽게 연동할 수 있습니다.</li></ul><p><strong>Data Discovery API 도입을 통해 기업의 맞춤화된 데이터 구매 요청 가능</strong></p><ul><li>기업이 구매하고자 하는 데이터를 검색, 맞춤화하고 특정 유저 세그먼트로부터 구매하고자 하는 데이터의 리스트를 받아볼 수 있는 데이터 탐색 API를 개발했습니다.</li></ul><p><strong>Data Controller Node 도입을 통한 동의 기반 데이터 거래 보장</strong></p><ul><li>기존 아이덴티티 프로바이더 노드의 역할을 확장해 데이터 컨트롤러 노드를 새롭게 도입했습니다. 이는 데이터 주체인 사용자의 제공 동의가 있을 때에만 데이터가 거래되는 것을 보장합니다. 또한 사용자의 동의를 제공받지 않고 데이터가 거래될 경우 패널티를 부여할 수 있도록 메커니즘이 설계되도록 하는 역할을 담당합니다.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uPTWSmpxIMyQrfnQ" /><figcaption>에어블록에 등록되는 데이터가 사용자의 명시적인 동의를 받았는지 Data controller node가 검증을 수행하는 과정</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73fee27dab6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Q3–4 Development Progress and Codes Released on Github!]]></title>
            <link>https://therne.medium.com/q3-4-development-progress-and-codes-released-on-github-38101de9088a?source=rss-5d8f4f28ad8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/38101de9088a</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[english]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Hyojun Kim]]></dc:creator>
            <pubDate>Fri, 23 Nov 2018 08:48:48 GMT</pubDate>
            <atom:updated>2018-11-23T09:11:21.108Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vuVHzLJ6kPHrdVLpkHpKmA.png" /></figure><h4>Development Progress Since July 2018</h4><p>For the past few months, our development team has been crunching and rigorously testing out thousands of codes related to the features in our overall network and back-end technology architecture to ensure that every feature in Airbloc is able to function and interact with each other.</p><p>After almost half a year of development and private testing, Airbloc’s codes are now released in the <a href="https://github.com/airbloc">Official Airbloc GitHub</a>!</p><p>Our development priorities have been on our back-end features, chiefly categorized into the following major overarchs:</p><blockquote>Data Management and Warehouse <strong>|</strong> Identity Data Management <strong>|</strong> Data Relay, Exchange and Export <strong>|</strong> Airbloc Web and Mobile SDKs <strong>|</strong> Airbloc APIs <strong>|</strong> Aero Sidechain Development <strong>|</strong> Airbloc Node Development <strong>|</strong> Development Language Migration from Python to Golang <strong>|</strong></blockquote><h4>Data Management and Warehouse</h4><ul><li>Implemented <strong><em>data warehousing</em></strong> functionality.</li><li>Introduced <strong>Bundle</strong> system for storing data — A bundle is a set of data records belonging to the same category. Data on Airbloc will be registered and stored as a bundle altogether, instead of being stored separately.</li><li>Enhanced <strong><em>data ID representation</em></strong> — Data ID is now represented by &lt;Bundle ID&gt;/&lt;User ANID&gt; , which allows easier user-centric data management.</li><li>Integrated <strong><em>data streaming through </em></strong><a href="https://grpc.io/"><strong><em>gRPC</em></strong></a><strong><em> stream </em></strong>— This allows efficient data ingestion and further ability to integrate with continuous data pipeline.</li><li>Improved <strong><em>bulk data management system</em></strong> by introducing <strong>Batch</strong> concept — Batch is a cached set of data record IDs, which enables more memory-efficient data handling by using <a href="https://en.wikipedia.org/wiki/Trie">trie</a>-like data structure.</li><li>Integrated data warehouse with DataRegistry smart contract.</li><li>Integrated data warehouse with our <strong><em>meta-database</em></strong>, <a href="https://bigchaindb.com/">BigchainDB</a>.</li><li>Implemented <a href="https://aws.amazon.com/s3/"><strong><em>Amazon S3</em></strong></a><strong><em> storage driver and protocol</em></strong> — essential for integrating Airbloc into Airbridge’s back-end data pipeline.</li></ul><h4>Identity Data Management</h4><ul><li>Implemented <strong><em>Account Management System</em></strong> — Users can now use Airbloc (e.g. control their own data, withdraw ABL rewards) using either their own private key or password.</li><li>Introduced <strong><em>Proxy Accounts</em></strong><em> — </em>This allows users to use the password instead of using wallet apps or MetaMask, and delegate transaction fees.</li><li>Implemented <strong><em>Temporary Accounts</em></strong>, which can be used during DAuth data collection authentication — Allows users to create a temporary account on Airbloc without the need of Metamask or a private key.</li><li>Implemented <strong><em>DAuth</em></strong> on both server-side and client-side.</li></ul><h4>Data Relay, Exchange and Export</h4><ul><li>Designed an <strong><em>Abstract Exchange System</em></strong> through smart contracts — The new system is designed to support any types of data exchange by enabling data consumers to offer a smart contract according to the type of exchange they want.</li><li>Improved the data exchange process to include three stages of <strong><em>Order, Open and Close</em></strong> — This allows more customizable data exchange process through smart contracts.</li><li>Refactored the architecture of the exchange smart contract.</li><li>Added support of <strong><em>Ricardian Contracts</em></strong><em> — </em>We’re currently researching a better way to use Richardian Contracts for enterprise-level data exchange and will be implemented soon.</li><li>Implemented <strong><em>Data Export Functionality</em></strong><em> — </em>Data consumers can view purchased data by providing re-encryption key for the data.</li></ul><h4>Airbloc Web and Mobile SDKs</h4><ul><li>Implemented our first version of <strong><em>Airbloc Mobile and Website SDK — </em></strong>The SDK contains data collection authentication functionality and can collect multi-variate data types leveraging Airbridge’s data pipeline.</li><li>Developed <strong><em>DAuth UI/UX</em></strong> for both web and mobile.</li><li>Tested Airbloc mobile SDKs on sample applications.</li></ul><h4>Airbloc APIs</h4><ul><li>Introduced <a href="https://grpc.io/"><strong><em>gRPC</em></strong></a><strong><em> and </em></strong><a href="https://developers.google.com/protocol-buffers/"><strong><em>Protobuf</em></strong></a><em> — </em>To ensure Airbloc Protocol is more polyglot and capable of dealing with massive data, gRPC is the best choice for our API implementations.</li><li>Implemented <strong><em>APIs</em></strong> essential for exchanging data.</li><li>Improved API design by separating <strong><em>User-side APIs and Provider-and-Consumer-side APIs.</em></strong></li></ul><h4>Aero Sidechain Development</h4><ul><li>Implemented <strong><em>Plasma Cash proof of concept</em></strong><em> — </em>Our approach is focused on implementing Plasma Cash as a framework by only using smart contracts and watchtower nodes (Validator, Operator).</li><li>Worked on <strong><em>Sparse Merkle Tree</em></strong> implementation which can serialize and cache the tree data.</li></ul><h4>Airbloc Node Development</h4><ul><li>Migrated from <strong><em>Python to </em></strong><a href="https://golang.org/"><strong><em>Go</em></strong></a><strong>.</strong> We were originally working on the first implementation of Airbloc Protocol using Python. However, we decided to switch to Go because it is faster and provides more robust concurrency than Python, which are more suitable properties for a high volume data exchange protocol.</li><li>Switched local database from <em>LevelDB to</em><strong><em> </em></strong><a href="https://github.com/dgraph-io/badger"><strong><em>BadgerDB</em></strong></a>. BadgerDB is embedded key-value store written in pure Go, and about 2 ~ 3x faster than the <a href="https://github.com/ethereum/go-ethereum/issues/15717#issuecomment-374732950">other</a> <a href="https://github.com/dgraph-io/badger-bench">competitors</a>.</li><li>Added P2P networking functionality using <a href="https://libp2p.io/"><strong><em>libp2p</em></strong></a>. Since we have switched to Go, there’s no reason not to use the best P2P networking stack :)</li></ul><h3>Join Our Official Community!</h3><ul><li><a href="https://t.me/airblocofficial"><strong>Telegram (KR)</strong></a></li><li><a href="https://t.me/airbloc"><strong>Telegram (EN)</strong></a></li><li><a href="https://open.kakao.com/o/gXIW11J"><strong>KakaoTalk</strong></a></li><li><a href="https://airbloc.org/"><strong>Homepage</strong></a></li><li><a href="https://fb.me/airblocofficial"><strong>Facebook</strong></a></li><li><a href="https://www.twitter.com/airblocofficial"><strong>Twitter</strong></a></li><li><a href="https://docs.google.com/document/d/1-xta_E2t2AHwvFodWg5aueQtcD4isnPHRQ6DscTq0dc/edit#"><strong>FAQ</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38101de9088a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technical Whitepaper Update]]></title>
            <link>https://therne.medium.com/technical-whitepaper-update-92ab24ca87a0?source=rss-5d8f4f28ad8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/92ab24ca87a0</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[english]]></category>
            <dc:creator><![CDATA[Hyojun Kim]]></dc:creator>
            <pubDate>Thu, 04 Oct 2018 11:56:43 GMT</pubDate>
            <atom:updated>2018-10-04T12:02:52.886Z</atom:updated>
            <content:encoded><![CDATA[<h4>Expanding Enterprise Adoption. Protecting Users’ Data Privacy.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*AGUSJasj84NDOzccULliHQ.png" /></figure><p>Hello Airblocers! We’re so excited to release Version 2.0 of Airbloc’s <a href="http://abr.ge/2ffuu">technical whitepaper</a>.</p><p>Lately, we have been working on the alpha version implementations ever since we released the first version of the whitepaper. During the time, we’ve made a lot of updates to the technical specifications of Airbloc Protocol to build a more feasible product that can eventually be adopted.</p><p>4 major motivations underpin this new technical update:</p><ul><li>Expanding Enterprise Adoption via Second Party Data Exchange</li><li>Real-Time Data Query and Segmentation via Data Relayers</li><li>Improving Scalability via Plasma Sidechain</li><li>Protecting Users’ Data Privacy via Privacy Shield</li></ul><h3>Expanding Enterprise Adoption: Second-Party and Segment-Centric Data Exchange</h3><p>We are expanding Airbloc Protocol to include not just third-party data, but <a href="https://www.lotame.com/1st-party-2nd-party-3rd-party-data-what-does-it-all-mean/">second-party data</a> as well to allow data trading between enterprises.</p><p>Previously in our previous version of the technical paper, we focused mainly on third-party data exchange between data owners and data consumers. Over the past few months, <strong>we have engaged in deep industry consultations with enterprises and we are convinced that there is indeed demand for second-party data exchange services</strong>.</p><p>The importance of second-party data is that there are companies that want to create synergy by exchanging with other enterprise data systems without revealing their data to the public. In the case of second-party data, we foresee that there will be high demand for such data exchange by large companies relying on Airbloc.</p><p>Airbloc Protocol now supports <strong>direct data exchange</strong> and <strong>segment-centric data exchange</strong>. Enterprises can trade data directly with other enterprises without having to trade the data on the public market, and they can also trade user segments— which only contains identity data of the users (e.g. Advertising ID of the 500 users who have installed application A)— instead of trading the full data.</p><p>Meanwhile, users can still track which of their data is traded transparently and the corresponding incentives. We believe that this move can expand the adoption of Airbloc significantly by enterprises.</p><h3>Real-Time Data Query and Segmentation: Data Relayer</h3><p>Originally, Airbloc Protocol only supported the purchase of static data sets created by data providers on the data marketplace. Now, we’re introducing <strong>Data Relayers</strong> to support a more dynamic form of data exchange which is user-centric and real-time.</p><p>Data Relayer is a node which supports data discovery by providing real-time data query services and segmentation. Data Relayer requires anonymized data from data providers to construct a queryable user profile.</p><p>A data consumer can query specific data filters (e.g. Users who are over age 20 and have been installed A application) to data relayers, and data relayers will return data IDs matched with the query in real-time.</p><h3>Improving Scalability: Plasma Sidechain</h3><p>Previously, we planned to use a side chain for computationally intensive tasks in Airbloc. Following this new technical paper update, we will be using <a href="https://plasma.io/">Plasma</a>, a layer-2 scaling solution for Ethereum.</p><p>Ethereum is currently not efficient to handle large amounts of requests due to the low transaction throughput and operational costs due to high transaction fees.</p><p>As such, we are developing our own implementation of Plasma sidechain<strong><em>. </em></strong>The plasma sidechain will be used for running our main business logic for data registration and data exchange in Airbloc Protocol.</p><p>We’re currently building our own sidechain called <strong>Aero. </strong>You can see the source code on Github.</p><p><a href="https://github.com/airbloc/aero">airbloc/aero</a></p><h3>Protecting Users’ Data Privacy: Privacy Shield</h3><p>Since Airbloc Protocol deals with personal data, the highest priority is placed in protecting data owners’ privacy because we consider privacy breaches as data asset theft.</p><p>To hide identity-related information about you on a public blockchain completely, we’re now introducing <strong>Anonymized ID</strong> (ANID) concept— an anonymous ID that prevents tracking of the user from unwanted third parties with malicious intent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EFtLCpVuU5Si2emNc-epGg.png" /></figure><p>Here’s a simple explaination to how Anonymized ID (ANID) work:</p><ol><li><strong>De-Identification</strong>: Users’ identity data is <a href="https://en.wikipedia.org/wiki/Hash_function/">hashed</a> upon data collection. This process prevents identity data (e.g. Email, Phone Number, SSN) from being used for malicious purposes (e.g. Spam Mails) outside of tracking and identification.</li><li><strong>Identity Masking</strong>: When anonymized data of the user is traded or referenced on the public blockchain (e.g. Data Exchange Log), Airbloc generates an Anonymized ID for the user. The ANID, rather than the actual user’s identity data is used during intermediate data trading processes by data relayers or data processors to prevent backtracking from unwarranted parties, thus protecting the user’s privacy.</li><li><strong>Private Identity Matching</strong>: The ANID of the user needs to be converted back to the real user’s identifier after the ANID is used. To prevent the user’s ID from being exposed to the public, Airbloc introduced <em>Private Identity Matching</em>. Powered by <strong>Zero-Knowledge Proofs.</strong></li></ol><p>Aside from the above mentioned points, there are also other updates such as data pipeline revamp, GDPR compliance, and redefined roles for stakeholders in Airbloc’s ecosystem.</p><p>New concepts such as Contribution Graph, Data Availability Challenge, Decentralized Data Warehouse and Re-Encryption Proxy have also been introduced. You can check the rest of the details in our new technical whitepaper.</p><p><strong>You can check the new English technical whitepaper at:</strong></p><ul><li><a href="http://abr.ge/2ffuu">Technical Whitepaper (English)</a></li></ul><p>Alternatively, you can visit our website at <a href="https://airbloc.org/">airbloc.org</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QCUwzgzqwvBFv_17D8igfw.png" /></figure><h3>Join Our Official Community!</h3><ul><li><a href="https://t.me/airblocofficial"><strong>Telegram (KR)</strong></a></li><li><a href="https://t.me/airbloc"><strong>Telegram (EN)</strong></a></li><li><a href="https://open.kakao.com/o/gXIW11J"><strong>KakaoTalk</strong></a></li><li><a href="https://airbloc.org/"><strong>Homepage</strong></a></li><li><a href="https://fb.me/airblocofficial"><strong>Facebook</strong></a></li><li><a href="https://www.twitter.com/airblocofficial"><strong>Twitter</strong></a></li><li><a href="https://docs.google.com/document/d/1-xta_E2t2AHwvFodWg5aueQtcD4isnPHRQ6DscTq0dc/edit#"><strong>FAQ</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92ab24ca87a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>