Skip to content

Remove dependency on composedb in favour of direct ceramic-one #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
m0ar opened this issue Mar 6, 2025 · 0 comments
Open

Remove dependency on composedb in favour of direct ceramic-one #52

m0ar opened this issue Mar 6, 2025 · 0 comments

Comments

@m0ar
Copy link
Collaborator

m0ar commented Mar 6, 2025

ceramic-one recently got up to speed around schema validation and model versioning. With that, in combination with the query and historical node synchronization capabilities, we should be able to drop the dependency on composeDB and use only C1.

This should greatly simplify the management of a node, as the need for both Kubo and js-ceramic is gone. It is also a required move given the deprecation status of js-ceramic now that C1 is up to speed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant