Skip to content

[WIP] migrate rocksdb large forest backend from crypto to node repo#1794

Draft
drahnr wants to merge 3 commits intonextfrom
bernhard-migrate-rocksdb-large-forest
Draft

[WIP] migrate rocksdb large forest backend from crypto to node repo#1794
drahnr wants to merge 3 commits intonextfrom
bernhard-migrate-rocksdb-large-forest

Conversation

@drahnr
Copy link
Contributor

@drahnr drahnr commented Mar 13, 2026

No description provided.

@drahnr
Copy link
Contributor Author

drahnr commented Mar 16, 2026

Need to adjust to 0xMiden/crypto#900 (review)

@drahnr
Copy link
Contributor Author

drahnr commented Mar 16, 2026

CC @iamrecursion

@iamrecursion
Copy link

It seems a bit silly to migrate this one out of the crypto repo while it's still undergoing some evolutionary changes with the API (e.g. 0xMiden/crypto#880). Is there a particular rush to do it?

@drahnr
Copy link
Contributor Author

drahnr commented Mar 16, 2026

I wouldn't call it rush, but I see a need to complete this to be able to fix bugs / iterater rather quickly compared to propagating it through protocol from the node perspective.

What is left that is significantly breaking public API from your pov, today?

There is also another effect of starting the work early - figure out what needs to be exposed publicly in addition to the current API surface of crypto.

@iamrecursion
Copy link

I don't think I have any breaking changes planned. It's more that keeping a copy of the persistent backend in crypto for now is valuable for getting the interface and design of these things right.

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

Successfully merging this pull request may close these issues.

2 participants