You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Rosetta implementation is flawed, because it accesses the archive database directly, which means any change to the database's schema is prone to break Rosetta. For this and also other reasons, we consider rewriting it, maybe on top of mina-indexer by Granola. I had a brief look at it previously and thought it would make a perfect backend for Rosetta, but at the moment it lacks some functionality. I was told Granola engineers are actively looking for use cases for this tool to handle. If we could prepare a list of requirements Rosetta has in advance, they could start working on them, so that we can migrate to mina-indexer more quickly.
The text was updated successfully, but these errors were encountered:
Current Rosetta implementation is flawed, because it accesses the archive database directly, which means any change to the database's schema is prone to break Rosetta. For this and also other reasons, we consider rewriting it, maybe on top of mina-indexer by Granola. I had a brief look at it previously and thought it would make a perfect backend for Rosetta, but at the moment it lacks some functionality. I was told Granola engineers are actively looking for use cases for this tool to handle. If we could prepare a list of requirements Rosetta has in advance, they could start working on them, so that we can migrate to mina-indexer more quickly.
The text was updated successfully, but these errors were encountered: