DISCUSSION: MAPPING POTENTIAL USE-CASES TO CONDUIT'S DEVELOPMENT GOALS

[kcelestinomaria]

Problem

Hi Algorand Conduit Dev Team. I lead the team at jasiriprotocol.org , an Algorand Foundation Grantee project, and we've been having some technical issues and constraints, since last year, trying to push a full mainnet solution.

One of the issues was the lack of a robust data layer that is native to the Algorand network.

For our dAPP(which bridges Web2 data to Web3 and vice versa), we couldn't avoid using AWS or Azure DBs, in as much as we tried to 'decentralize' our solution. This limits our goal of putting data and assets in 100% control of the users on our protocol, despite it being a design principle.

Storage on Algorand is expensive, and in most cases Algorand is simply a state machine, just timestamping data on the go and then storing it in a local DB.

Solution

An iteration on Conduit that optimizes it for almost-free event streaming, crucial for data-centric applications. Simply think of it as decentralized Kafka, natively on Algorand, at web scale.

Someone could then use Conduit, in this scenario, for:

1. Distributed compute pipelines
2. Open, decentralized, and composable databases on Algorand... very helpful for applications that rely on NFTs or just any use case that is reliant on data, or solving a data problem at scale.

Dependencies

This could potentially be merged with DIDs on Algorand, mapping user auth to the data. But that is just an idea.

I think one-click, downloadable relay nodes are needed so as to make the high-level idea a reality.

IPFS might be needed as well, but this one can come as an option for the developer leveraging conduit for their data solution

Urgency

This will help further scale Algorand, from the data storage standpoint, by enabling:

• Cheap decentralization of data storage for apps, negating the need to store on-chain data(very expensive for users and developers alike) or using centralized DBs.
• Rich NFT apps, social media, or any other data-centric apps will be able to deploy on Algorand, especially apps that send(stream) data on-chain in real-time. We are one of those projects, and so pushing for this will help us deploy a high-performing, complete experience for our esteemed users.
• It could also power additional developer tooling, like graph DBs natively on Algorand through Conduit, or say a decentralized cloud platform, built natively on Algorand, among many other non-financial asset applications.

[winder]

Hi @kcelestinomaria, conduit is designed to be extended by builders like you for accessing on chain data. You can build an exporter for your application that stores just the data you want in a format convenient for your use case.

I would be interested in hearing more about what you're trying to do, could you message me on discord? My handle is will#0709.

[winder]

Conversation moved to discord.