Origin Cohort Grant Proposal: Omnio

Grant/Project Name: Omnio
Proposer(s): Armie Soto / Lucas Demaría
Grant Category: Application

ELI5 Project Summary:
We’re using ComposeDB to develop an open standard for Web3-native digital product identity, and with this standard in place — building a minimum viable product (MVP) to demonstrate the business value of self-custodial purchase data.

Project Description:
Currently, product data is siloed across fragmented e-commerce platforms.

To enable the interoperability of future retail applications, we’re using ComposeDB to develop an open standard for pairing real-world products with a Web3-native digital identity that is: authentic so that product data is cryptographically verifiable; composable so that brands, consumers, and retailers can contribute to a product’s overall reputation; and permissionless so that third parties have access to a globally-readable source of trusted product information.

Lastly, we envision a future in which self-custodial purchase data is widely adopted — empowering users to leverage their shopping history cross-platform.

Relevant Links:

Ceramic Ecosystem Value Proposition:

  • What is the problem statement this proposal hopes to solve for the Ceramic ecosystem?
    We believe many ecosystem projects have been limited to specific use cases (e.g., social).
  • How does your proposal offer a value proposition solving the above problem?
    Our goal is to build infrastructure that will jump-start new, enterprise-grade retail applications on the Ceramic network.
  • Why will this solution be a source of growth for the Ceramic ecosystem?
    Besides easy onboarding for both Web2 brands and Web3 developers, we plan to be the first Web3-native project to incorporate GS1 standards — providing built-in trust guarantees and foundational data for over 200 million verified consumer products globally.

Funding Requested (USDC): [$50,000/65,000]


  1. Milestone #1: System Architecture (100 Hours) - [$10,000]
    First, we plan to work closely with the Ceramic engineering team to determine feasibility and scope.
  • [Technical Requirements] - [60 Hours @ $100/Hour]
    • Defining Ceramic data models, integrations (e.g., Lit Protocol), product attributes, etc.
  • [UX Design] - [40 Hours @ $100/Hour]
    • Conducting research, mapping user stories, wireframing, etc.
  1. Milestone #2: Design/Prototyping (40 Hours) - [$4,000]
    A user-friendly interface is critical for onboarding any Web2 brand that might be hesitant to adopt a Web3 solution, so we’re taking design inspiration from existing no-code development platforms (e.g., Canva).
  • [UI Design] - [40 Hours @ $100/Hour]
    • This includes using Figma to plan common design elements, input controls, layout, etc.
  1. Milestone #3: Fullstack v.1 Development / Brand-Facing (200 Hours) - [$20,000]
    Our brand-facing deliverables will include the following.
  • [Brand Portal] - [160 Hours @ $100/Hour]
    • A brand owner can sign in, create a product identity (either individually or by uploading product inventory in bulk), and manage verifiable credentials (VCs) issued to customers representing proof of purchase.
  • [ComposeDB Data Modeling] - [40 Hours @ $100/Hour]
  1. Milestone #4: Fullstack v.1 Development / Consumer-Facing (160 Hours) - [$16,000]
    Our consumer-facing deliverables will include the following.
  • [Consumer Dashboard] - [80 Hours @ $100/Hour]
    • A consumer can sign in and view their self-custodial purchase data — product identity, time of purchase, amount spent, etc.
  • [E-Commerce Site] - [40 Hours @ $100/Hour]
    • A mock e-commerce site to simulate online purchases with product listings configured to read from published Ceramic data streams.
  • [All Necessary Lit Protocol Integrations] - [40 Hours @ $100/Hour]
  1. Milestone #5 (Optional): GS1 Integration (25 Hours) - [$15,000]
    GS1 is the multi-national, not-for-profit industry standard for product identifiers. Web2 incumbents — Amazon Seller Central and Google Merchant Center, for example — require GS1 standards for all products listed on their platforms.

    We’ve been in contact with the GS1 innovation team over the past several months, and our goal is to integrate with their global registry.

  • [Back-End Infrastructure and Connected APIs] - [$13,500]
  • [Development] - [15 Hours @ $100/Hour]

I accept the 3Box Labs Grants Terms and Conditions: [Yes]
I understand that I will be required to provide additional KYC information to 3Box Labs to receive this grant: [Yes]

Hi @armiesoto, thank you for your proposal! We will be in touch with an update once we have completed our initial review (1-2 weeks).

1 Like

Congratulations @armiesoto, I’m delighted to inform you that your grant proposal has been accepted! :tada:

We would like to award you a Ceramic Builders Grant.

We will follow up shortly with more details via email.

Omnio Updates: Road to ETHDenver 2023

Project Background:
Over the past couple of months, we set out to build a minimum viable product (MVP). Our mission is to empower consumers through private, self-custodial data, and Ceramic, as our technology partner, has an important role to play in achieving this.

Relevant Links:

Update #1: Our Technology Stack
We’re using Ceramic to store data — both from brands and consumers. As mentioned in our grant proposal, we ultimately decided to integrate with Lit, given that user-held credentials will require a privacy layer.

Update #2: Omnio Brand Studio
Our brand-facing solution is Omnio Brand Studio — taking inspiration from Web2 platforms such as Amazon Seller Central and Google Merchant Center.

  1. Creating a Digital Product Identity on Ceramic

Rather than uploading product information onto a single, non-interoperable marketplace (i.e., walled gardens), any brand with an Ethereum wallet can use Omnio Brand Studio to create a digital product identity (published on Ceramic).

This is particularly relevant to brands with existing wallet keys, but we hope to provide utility to a broad spectrum of future Web3-native retail applications by maintaining this data model over time.

Update #3: Omnio
Our consumer-facing solution is Omnio — our first iteration of a full-scale consumer data protocol.

  1. Collecting, Encrypting, and Issuing Consumers’ First-Party Data

Our grant proposal highlighted self-custodial purchase data as our main proof of concept. However, as we progressed in our build, it made sense to incorporate additional touch points across the retail customer journey.

  • Interacting with an Omnio-Integrated Site
    • To demonstrate this user flow, we built a mock e-commerce site (available here). A user signs in with their wallet — initiating a session with the Ceramic network.
    • We based our demo on common event-based tracking methods (e.g., Meta Pixel) and decided to collect the following consumer touch points: View Product, Favorite Product, Add to Cart, and Initiate Purchase.
    • As the user interacts with the site, these events are collected and encrypted using Lit before the write to Ceramic even takes place.
    • From Omnio, the user can delete these credentials — demonstrating how consumers will manage their private, self-custodial data as they shop online.

  1. Managing Self-Custodial Purchase History

Lastly, a proof of purchase is generated and issued after a user completes the checkout process.

Update #4: Our Roadmap
There are several products today enabling brands to collect and activate data collected directly from their customers, but we believe we’re one of the first projects to issue an encrypted copy of that data back to consumers.

Our focus now is leveraging these concepts to solve real-world problems. If you want to connect, write us an email here or set up a user discovery call here!

1 Like

Looks great! Do you have links to your code repositories or maybe a SDK containing the composite for your data model please?

Hey Paul! Here’s our code repository. Thanks!

Looks like you’re using the Glaze DID DataStore rather than ComposeDB for your data model? Do you have any plan to migrate to ComposeDB please?

That’s right. We couldn’t build the functionality we needed to using ComposeDB before the conference. We’ll be migrating to ComposeDB in our next release.