This proposal is part A of 2 proposals that tackles the same problem-solution definition below.
Litentry is currently missing end-to-end usecase enabled by the IdentityHub. Litentry is an identity aggregator but is experiencing bottlenecks at both ends of it’s product journey. Therefor not being able to deliver on it’s value proposition. The first one located at the start of the product journey where data forms the input for identity based usecases and the second one being at the end of the product journey where data output in the form of identity insights unlocks usecases.
Additional context for this specific proposal
To generate verifiable credentials there is the need to receive clean and structured on-chain data which requires an indexer to make sense of the raw blockchain data. Structuring and labeling tha data so it provides an insight or ‘truth statement’ about the subjects identity or characteristics.
Objective: Develop a Litentry Data Adapter that facilitates the creation of verifiable credentials through API endpoints, allowing projects and indexers to easily structure and deliver on-chain data for credential generation. This could be in the form of a small web app or interactive documentation.
Description:
The Litentry Data Adapter will address the bottleneck of input data by defining a standardized logic and data format for receiving raw blockchain data via API endpoints. It aims to empower projects and indexers with the ability to structure, label, and provide meaningful insights about subjects' identities or characteristics, facilitating efficient credential creation.
Features:
- API Endpoint Standardization: Define a standard API endpoint format for projects and indexers to deliver structured data for credential creation. Making it easy for TEE workers to hit the endpoint and extract the necessary data for assertion creation.
- Data Segment Examples: Provide examples of request and response bodies for different types of data segments to guide projects in formatting their data accordingly to formats that are easy to integrate by the Litentry team.
- Customizability: This tooling allow projects to customize the type of data they want to use for credential creation, giving them flexibility and agency over the credentials they generate without the need to rely on dedicated services from the Litentry team.
Benefits:
- Streamlined process for projects and indexers to contribute structured data for credential creation.
- Increased agency over the verifiable credentials used within the Litentry ecosystem.
- Expanding the scope and diversity of verifiable credentials available for users within Litentry's profile feature, Discord bot, and future use cases.
By executing these proposals, Litentry can overcome the challenges it currently faces in delivering its value proposition by addressing data input and output bottlenecks, ultimately enhancing the overall user experience and utility of the platform.
1yr ago
Love the idea! In case Litentry doesn't develop a data adaptor, what alternative options could we explore?