Hi Zach,
I am working on a POC for a decentralized DBaaS, using Fluence network and ComposeDB.
The previous version had a two-sided marketplace with node+db-providers and users. From a frontend you can select a db-provider, which each is a fluence node paired with ceramic & ipfs nodes. The index on node is generated with a hardcoded pk of a did:key.
The new version i am working on has node-providers, index creators/owners/controllers and users. Node-providers offer infrastructure. Index creators can create composites + start indexes on that infrastructure and let ‘their’ users use them. All within a decentralized marketplace for decentralized services. From a different perspective it could be seen as a ComposeDB playground. (permanence of data of course not being guaranteed … yet). Or think of the UX for a headless CMS with non-devs being able to design content architecture.
Within such a context it would be good UX for index creators to able to create composites and operate indexes from a wallet/did:pkh
Joera