MetaBox

• 

  MetaBox Home page

• 

  DataBox - Personal Data Space

• 

  Profile - Personal Info Space

Inspiration

In the Web3 world, to the C-side， users lack a data space that is completely owned by themselves. As a result, users' privacy data can not be protected by TrustLess contracts but the centralized cloud storage and users run naked in CyberSpace. For B-side, developers lack a programmable storage layer that allows developers to achieve reliable, secure data storage and access rights.

What it does

MetaBox currently involves two boxes: Profile and DataBox; and one protocal: ICSP. Profile is user's personal information Canister, mainly for information integration, domain name access, drawing social graph and other functions, allowing users using MetaBox to connect with each other through Profile, to achieve social relationships driven by data value. DataBox is a user's personal private cloud, users can upload plaintext files and ciphertext files, plaintext files can be shared directly with anyone through HTTP links, and the person being shared can directly obtain the files, or play videos. For ciphertext files, multiple cryptographic protection and security measures can be used to protect the privacy of users' personal data, and users can achieve secure ciphertext sharing through secure key sharing technology, and directly obtain the benefits brought by these data. ICSP is an underlying protocol for ToB storage, providing data storage services similar to IPFS or Arweave, which has unlimited capacity, can be upgraded, supports one-step access to data by HTTP, permission access and other functions. It aims to provide safe, stable, reliable and controllable storage services to the Project Side of Web3, IC ecosystem, and other public chain ecosystems such as ETH. Through ICSP, project parties can fully control the ownership and real-time status of data, so as to obtain a reliable storage service experience.

How we built it

Our technology stack is currently based entirely on the smart contracts of Internet Computer Blockchain, coded by Rust and Motoko. Our front end uses TypeScirpt and JavaScript. In the process of building DAPP, we adopted advanced and secure cryptographic processing schemes to achieve secure key sharing, ciphertext sharing, device synchronization and other functions.

Challenges we ran into

1. We need to overcome the storage limitations of a single Canister smart contract
2. We need to implement secure contract interaction in an asynchronous environment
3. We need to make the DAPP wirelessly scalable by spanning subnets, scalily canister
4. High-speed parallel processing of data to achieve a smooth interactive system

Accomplishments that we're proud of

1. High-speed data transfer, upload and download
2. Secure key sharing, ciphertext sharing and device key synchronization
3. Unlimited scalability of DAPP, safe and reliable storage service To Consumer and To Bussiness

What we learned

1. Improve the scalability of DAPP by using system-level Canister
2. Build Canister with Rust and Motoko in a ore efficient and high-quality way ## What's next for MetaBox
3. Better UI
4. Introduction of payment systems
5. One-step mint Data-NFT
6. Provide IC-based secure, reliable, and controllable storage services for Web3

Built With

• ciphertext-sharing
• coded-by-rust-and-motoko.-our-front-end-uses-typescirpt-and-javascript.-in-the-process-of-building-dapp
• cryptography
• javascript
• motoko
• rust
• typescript
• we-adopted-advanced-and-secure-cryptographic-processing-schemes-to-achieve-secure-key-sharing