docs: add DEP docs (#567)

Co-authored-by: tjyoon0324 <102934148+tjyoon0324@users.noreply.github.com>
Co-authored-by: Hansol Lee <38912532+H4NLee@users.noreply.github.com>
Co-authored-by: H4NLee <hansol@medibloc.org>
Co-authored-by: audtlr24 <audtlr24@gmail.com>
Co-authored-by: gyuguen <gyuguen.jang@medibloc.org>
Co-authored-by: InChul <49394875+inchori@users.noreply.github.com>

.gitbook/about-panacea/panacea-ecosystem.md → .gitbook/0-about-panacea/0-panacea-ecosystem.md

@@ -3,12 +3,12 @@
 
 ## Mission
 
-Allow patients to own their data, provide it, and get incentivized.
+Allow patients to own their data, provide the data to data consumers, and get incentivized.
 
 
 ## Goal
 
-Building decentralized healthcare data sharing/exchange protocols
+Build decentralized healthcare data sharing/exchange protocols
 
 
 ## Tech Stack
@@ -18,7 +18,7 @@ Building decentralized healthcare data sharing/exchange protocols
 
 ## Panacea blockchain
 
-The Panacea is a public blockchain based on the Cosmos SDK and the Tendermint.
+Panacea is a public blockchain based on the Cosmos SDK and the Tendermint.
 
 As the Tendermint implements a partially synchronous BFT (Byzantine fault-tolerant) consensus protocol,
 Panacea can provide a high-performance, consistent, and secure decentralized network
@@ -51,11 +51,11 @@ Then, data verifiers (receivers) can verify that the data has been not tampered
 ### Data Exchange Coordination
 
 Panacea provides a feature of coordinating data exchange deals.
-Data consumers can publish deals publicly, specifying which data they want to purchase and how much budget they are willing to pay.
-And, data providers (holders) who agree to provide their data with consumers can provide their data securely and earn rewards in MED.
+Data consumers can publish deals publicly, specifying 1) which data they want to purchase and 2) how much budget they are willing to pay.
+Data providers (holders) who agree to provide their data with the data consumers can provide their data securely and earn MED as rewards.
 
-This on-chain data exchange coordination must work with some off-chain components to verify data validity/integrity and securely deliver data.
-For example, some malicious data providers can try to sell data that data consumers don't want or data that was generated by themselves (not by trusted issuers).
+This on-chain data exchange coordination must work with some off-chain components to verify data validity/integrity and to deliver data securely.
+For example, some malicious data providers ccould try to sell data that the data consumers don't want or that was forged by themselves (not by trusted issuers).
 Therefore, data should be validated by off-chain data validators before being delivered to data consumers, as described in the [Data Exchange Validation](#data-exchange-validation-with-confidential-computing) section.
 
 
@@ -67,30 +67,26 @@ Using [Panacea Verifiable Credential SDK](https://github.com/medibloc/vc-sdk), d
 Since [Verifiable Credential](https://www.w3.org/TR/vc-data-model/) is a standard format defined by W3C, any data receivers can verify credentials without any compatibility issues using the data issuer's (holder's) cryptographic public key that is corresponding with their DID.
 In other words, the Verifiable Credential SDK works with DID management features of the Panacea blockchain.
 
-In addition, data holders can present their data by masking privacy-sensitive fields that don't need to be revealed.
-That can be achieved by Zero-knowledge Proof using BBS+ signatures so that data receivers can verify data integrity even though some fields in the data are masked (technically, ' tampered').
+In addition, data holders can present their data while masking privacy-sensitive fields.
+This can be achieved by Zero-knowledge Proof using BBS+ signatures so that data receivers can verify data integrity even though some fields in the data are masked (technically, ' tampered').
 
 ### Data Exchange Validation with Confidential Computing
 
 As described in the [Data Exchange Coordination](#data-exchange-coordination) section, Panacea blockchain provides data exchange coordination. However, data that is exchanged between providers and consumers cannot be validated/delivered through a public blockchain because all transaction data is exposed to everyone.
 Even if transaction data is encrypted, validator nodes should be able to decrypt data to verify data validity/integrity.
 That could be a huge vulnerability, allowing data to be leaked to anyone other than intended data consumers.
-To avoid this vulnerability, we could implement this data exchange validation as smart contracts run on [Secret Network](https://scrt.network/), but still, we didn't want to expose private data on the public blockchain even if all data is encrypted.
+To avoid this vulnerability, we could have implemented this data exchange validation as smart contracts run on [Secret Network](https://scrt.network/), but still, we didn't want to expose private data on the public blockchain even if all data is encrypted.
 
 Instead of solving this problem on chain, we have introduced an off-chain decentralized oracle powered by confidential computing ([Intel SGX](https://www.intel.com/content/www/us/en/developer/tools/software-guard-extensions/overview.html)).
 Like Secret Network, all oracle nodes are run in the secure enclave. All data is encrypted so that only oracle nodes can decrypt it to verify data validity/integrity. If data is verified successfully, it is re-encrypted by oracle nodes for the data consumer.
 Because this process is executed in the secure enclave, decrypted data cannot be stolen by anyone, even oracle node operators.
 
-To avoid the Byzantine problem between decentralized oracle nodes, oracle nodes borrow the voting power from the Panacea blockchain.
-Only operators who are running validators on Panacea can run oracle nodes. Then, an oracle node has the same voting power as a corresponding validator.
-If an oracle node acts maliciously, its validator's stake is slashed.
-
 ### Secure Data Storage
 
-Based on DIDs, Verifiable Credentials, and Data Exchange Coordination/Validation, it seems that applications that handle privacy data can be implemented.
-However, to actually implement applications, it must be decided specifically how data will be stored and how it will be transmitted in decentralized environments.
+Based on DIDs, Verifiable Credentials, and Data Exchange Coordination/Validation, it seems that applications that handle privacy data can be implemented on top of Panacea.
+However, to actually implement applications, the specific method on how data will be stored and how it will be transmitted in decentralized environments should be decided.
 
 Thanks to [IPFS](https://ipfs.io/), data can be transmitted by [content addressing](https://docs.ipfs.tech/concepts/content-addressing/) in environments where ecosystem participants don't know each other's IP addresses and ports.
-But, IPFS is also a public network basically that is unsuitable for storing privacy data even if it is encrypted. IPFS also provides a way to set up private clusters, but it is not flexible enough to be used for data exchange based on public blockchains.
+However, IPFS is also a public network, which is unsuitable for storing privacy data even if it is encrypted. IPFS also provides a way to set up private clusters, but it is not flexible enough to be used for based on public blockchains.
 
-MediBloc team is researching many secure decentralized data storages including edge databases.
+To solve this problem, MediBloc team is still researching many secure decentralized data storages including edge databases.

.gitbook/about-panacea/roadmap.md → .gitbook/0-about-panacea/1-roadmap.md

@@ -8,13 +8,15 @@ Now, MediBloc would like to shift its focus to boosting the potential of Panacea
 
 Nowadays, many businesses and technologies are data-driven. Many companies are already familiar with handling large dataset and deriving new values by analyzing sets of data. But, secure data exchange is still the one of the hardest area for data-driven industries. Data requesters want well-refined data or fine-grained raw data for successful data analysis. But, data owners (individuals) don’t want their privacy exposed and abused. Additionally, Web3 users are already aware that proper rewards should be guaranteed for their data and actions transparently on Web3. Traditional systems in Web2 have solved this issue in various ways, but MediBloc believes that we all can build more transparent and reliable systems for secure data exchange in Web3 ecosystem. 
 
-Our data exchange protocol has the concept of data Pool, so that anyone can specify the type and the quantity of the data they want. Also, they can specify how much cryptocurrency they are willing to pay for the data. All of these data pools are recorded in Panacea and everyone who wants to sell their data can see all data pools. Data sellers can choose data pools by checking how many parts of their data to be shared to data buyers. Then, they sign the consents for data exchange. Verified off-chain data validators validate whether data provided by data sellers conforms to criteria that data pool creator has specified. If all the requirements are met, the data is provided to data buyers via secure connections and the promised amount of cryptocurrency is transferred to data sellers. In this entire protocol, data is not recorded on any blockchain such as Panacea. All data transmissions are performed off-chain and Panacea guarantees all agreements for data exchanges and transparent payments.
+Our data exchange protocol has the concept of data Pool, so that anyone can specify the type and the quantity of the data they want. Also, they can specify how much cryptocurrency they are willing to pay for the data. All of these data pools are recorded in Panacea and everyone who wants to sell their data can see all data pools. Data providers can choose data pools by checking how many parts of their data to be shared to data consumers. Then, they sign the consents for data exchange. Verified off-chain data validators validate whether data provided by data providers conforms to criteria that data pool creator has specified. If all the requirements are met, the data is provided to data consumers via secure connections and the promised amount of cryptocurrency is transferred to data providers. In this entire protocol, data is not recorded on any blockchain such as Panacea. All data transmissions are performed off-chain and Panacea guarantees all agreements for data exchanges and transparent payments.
 
 This data exchange protocol is being developed to be as general as possible, so that not only the healthcare data but also all the other types of data can be handled by the protocol. Since Panacea and data exchange protocol is publicly opened, any service providers can build their own services on the top of the data exchange protocol, so that their users can exchange their data securely and get proper rewards. As the first use case, MediBloc is going to build a healthcare data marketplace service based on this protocol.
-Well, it sounds like the protocol should work well, right? However, there are so many issues that we have to resolve. For privacy and security, data sellers should be able to expose only a small part of their data that is really desired by data buyers. Data transmission must be secure, so that anyone cannot steal data. In order to guarantee the right of data buyers, all criteria that data buyers specified has to be validated clearly before the payment is finalized. In addition, the ecosystem should be attractive enough for many data sellers and buyers to join. 
+Well, it sounds like the protocol should work well, right? However, there are many issues that we have to resolve. For privacy and security, data providers should be able to expose only a small part of their data that is really desired by data consumers. Also, data transmission must be secure, so that no one can steal or intercept the data. In order to guarantee the right of data consumers, all criteria that data consumers specified has to be validated clearly before the payment is finalized. Last but not least, the ecosystem should be attractive enough for many data providers and consumers to join. 
 
 In order to resolve these challenges, the team is developing this data exchange protocol with several latest technologies.
-The detailed tech stack of the data exchange protocol is described in the [Panacea Ecosystem](./panacea-ecosystem.md) document.
+The detailed tech stack of the data exchange protocol is described in the [Panacea Ecosystem](./0-panacea-ecosystem.md) document.
 
-There will be more details that we have to solve, and we know that all of them cannot be achieved in one step. Hence, we will complete this big task step by step. In 2022, MediBloc will release the v0 of data exchange protocol as a proof of concept that includes only essential features. Also, a data marketplace web service will be introduced as a simple example service based on the protocol. Based on this proof of concepts, the data exchange protocol will be improved as v1 from 2023 with enhanced security and interoperability. MediBloc has already opened all source codes and progresses publicly on GitHub. We encourage anyone to join the project and share your insights. 
+There will be more detailed issues that we would have to solve, and we know that all of them cannot be solved in one step. Hence, we will complete this big task step by step. In 2022, MediBloc have released the v0 of data exchange protocol as a proof of concept that includes only essential features on testnet. Based on this proof of concepts, the data exchange protocol will be improved as v1 in 2023 with enhanced security and interoperability. Also, MediBloc will be introducing dApps for data providers using data exchange protocol and keep designing the services that go on top of data exchange protocol. MediBloc has already opened all source codes and progresses publicly on GitHub. We encourage anyone to join the project and share your insights. 
 We are so excited and thrilled to share our vision to achieve our goal to become the world’s best patient centric health data platform. Thank you for your continued support! 
+
+--

.gitbook/1-users/3-data-exchange/0-about-dep.md

@@ -0,0 +1,43 @@
+# About Data Exchange Protocol
+
+Data Exchange Protocol (hereafter 'DEP') is a communication layer for sharing and exchanging various types of data
+between two parties in decentralized environments.
+
+
+## What can you do with DEP?
+
+Data consumers can open data deals by specifying the type, the quantity, and the pricing of the data that they are willing to consume. 
+
+Data providers can choose and participate in the deals that match the data that they have when they are willing to provide.
+
+To guarantee data consumers only receive the data that match the criteria specified by them,
+decentralized oracles verify and issue certificates for all data being provided by the data provider.
+
+Panacea manages the status of all data deals and data sharing consents,
+ensuring data providers and ecosystem operators are rewarded appropriately.
+
+
+## Motivation and Goals
+
+### Data Ownership and Sovereignty
+
+The ultimate goal of owning our own data is having a control about how our data is used.
+
+### Decentralized off-chain data validation
+
+o guarantee data consumers only receive the data that match the criteria specified by them,
+decentralized oracles verify and issue certificates for all data being provided by the data provider.
+
+### Privacy
+
+Throughout the entire process of data verification and transmission,
+the data content must not be exposed to anyone other than the consumer intended by the data provider.
+
+### Generalized data exchange
+
+Not only healthcare data, but various types of data should be covered through this protocol.
+
+### Open-sourced protocol
+
+All protocol specifications and implementations must be open-sourced, so any participants can understand
+how data is exchanged and how privacy is guaranteed.