✅Data Verification

Camp leverages zk-TLS to verify data before making it available on-chain.

Getting permissioned data

After users authenticate via Camp Auth Hub or through the SDK, Camp leverages official API's across web2 platforms to retrieve social data. Data is updated 15 - 30 mins.

Verifying data

🚧 in active development

Camp Network uses zk-TLS to securely and efficiently bring verified Web2 data on-chain. This system leverages zero-knowledge proofs (ZKPs) to ensure data integrity and privacy, making it ideal for daily data pulls from various Web2 platforms. Here's how zk-TLS works:

Data Retrieval

Users log in to their Web2 accounts through the Camp Auth Hub. Once authenticated, Camp accesses the platform's API endpoints to fetch the necessary data.

Notarization and Proof Generation

🚧 in active development

The retrieved data includes its TLS certificate. A dedicated notarizing service then signs this TLS certificate and generates a zero-knowledge proof (ZKP), which verifies the data source without revealing the certificate details. The ZKP attests to the authenticity and integrity of the data, confirming it originated from the specified Web2 platform.

On-Chain Integration

🚧 in active development

The data is stored in Camp's storage layer with a content identifier written on-chain. The ZKP is then submitted on-chain, ensuring the data's integrity and source are verifiable.

Timely Data Pulls

Camp Network performs timely (15-30 mins) data pulls from connected Web2 platforms. This process involves scheduled tasks that use authenticated tokens to pull updated data automatically. Each data pull undergoes continuous verification through the notarizing service to generate fresh zero-knowledge proofs (ZKPs). These updated data and corresponding ZKPs are consistently written on-chain, ensuring that dApps always have access to the latest verified data.

Encryption

🚧 in active development

Camp Network employs a hybrid encryption method to ensure data security and efficiency. Symmetric encryption is used to encrypt the data, while asymmetric encryption secures the symmetric keys. Smart contract-based access control policies manage and verify decryption permissions, ensuring that only authorized users can access the data. Decryption keys are securely distributed using public keys, and decryption is allowed only for users who meet specific criteria, verified through cryptographic proofs. More on this in the next section.

Data Storage?

When data is retrieved and encrypted, it is uploaded to IPFS, which generates a unique content identifier (CID) for each data file. This CID acts as a permanent reference to the data stored on IPFS. The CID is then written on-chain, ensuring that the data can always be accessed and verified using its CID.