3box / 3box

The easiest way for Ethereum apps to manage user data.

Welcome to 3Box Labs!

3Box Labs is a Web3 product studio that creates software to advance a more open, safe, and collaborative web. We are the inventors and a core maintainer of Ceramic, a decentralized network for composable data. Permissionless data composability will inevitably network all of the information on the web, transform the way we build applications, and connect users to their data, and each other, in new and exciting ways. To learn more about 3Box Labs, visit https://3boxlabs.com/.

Getting Started

👤 Visit Ceramic Network to build applications with composable data.

💬 Join Ceramic Community Discord to chat with the core team and developer community

👩‍💻 Explore our blog to learn more about Ceramic, comopsable data and Web3 - and sign up for our newsletter.

3box's Issues

Schedule meetings at Dappcon

Reprioritized List of Value Propositions and Use Cases

Kauri Interview

Interview and document

Customer list and interview schedule --> https://airtable.com/tblFOCJwBGkXqtzCl/viwLYxN3TClyYoX7i

Airswap Interview

Interview and document

Customer list and interview schedule --> https://airtable.com/tblFOCJwBGkXqtzCl/viwLYxN3TClyYoX7i

Portis Interview

Start formalizing research around incentive models for data

How can token models be coupled with data hubs to empower users? Are bonding curves relevant to this?

Research Blockstack storage

Research Blockstack storage and see if some concept apply to this project

Draft functional requirements

Bounties Network Interview

Interview and document

Customer list and interview schedule --> https://airtable.com/tblFOCJwBGkXqtzCl/viwLYxN3TClyYoX7i

Round 3, Interview 5

imToken Interview

Proposal Support

SuperRare Interview

Customer Interview Questions and Capture Form

Investigate whether to use identity hubs, orbit-db, or somehting else for storage backend

There are multiple options availible for us to use as a backend service. We want to be as flexible as possible, but most likely we will have to pick one and stick with it. Our choice should optimize for decentralization, privacy, and user sovereignty.

Option	Comments
DIF Hub	Possibly great synergies as this standard emerges. Unclear exactly how decentralized these services will be.
orbit-db	Uses ipfs and CRDTs. Using this we can utilize infura for ipfs hosting, and a thin service for keeping track of the most recent hash. This can easily be made more decentralized in the future. We would also need to roll our own system for maintaining the database.
swarm	Could be a great alternative, but api is quite hard to use currently
BigchainDB	A premissioned DB system. Could be great if we want a DB that is shared between multiple people, but overkill for a personal data store.

So far I've seen no db with native encryption support.

Draft Architecture Hypothesis

Gitcoin Interview

Interview and document

Customer list and interview schedule --> https://airtable.com/tblFOCJwBGkXqtzCl/viwLYxN3TClyYoX7i

Document Insights from Round 1 of Research

Centrifuge.io Interview

Round 3 Interviews

Proposal Blog Post

TMNT Interview

IIS Interview

Ujo Interview

Interview and document

Customer list and interview schedule --> https://airtable.com/tblFOCJwBGkXqtzCl/viwLYxN3TClyYoX7i

Follow up with leads from dappcon

Attempt to schedule

Measure and report github and npm metrics

Round 5 Interviews

Update GitHub Repo

Revise user journey

Set up google email

Set up webflow site

Design initial architecture

capable of meeting the user journey and functional requirements

Enigma Interview

Launch 3box.io

Synthesize Round 3 Interviews

Investigate usage of different types of hubs

Currently the model we use is one hub for one user with one namespace shared between all dapps.
There are two main other things to explore:

1. Add additional namespaces to users personal hubs
2. Hubs that are shared between multiple parties (shared data)

For 2 there are multiple things that we need to consider, in particular how it affects the requirements from the data backup service.

Draft User Journey v1

MVP Tech Spec

Plan CYC_1 Design Sprint

Develop initial list of value propositions and use cases

To feed Round 3 interview participant selection

FEM Proposal

Metamask Encryption/Decryption

Configure mail chimp signup

RSVP Interview

Interview and document

Customer list and interview schedule --> https://airtable.com/tblFOCJwBGkXqtzCl/viwLYxN3TClyYoX7i

Measure address server usage

v.0.0.2 Build

Round 4 Interviews

Meridio Interview

Interview and document

Customer list and interview schedule --> https://airtable.com/tblFOCJwBGkXqtzCl/viwLYxN3TClyYoX7i

MetaMask checkin

Configure Google Analytics