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
In an ideal world, we’d have the ability to sync from a single binary && be able to reuse a lot of the functionality of the sdk without maintaining a fork or massively vendoring everything. Unfortunately, that’s not the case, and we’re stuck in a trilemma.
The trilemma (pick 2):
Single binary syncs (and single binary upgrades)
Reusing the sdk’s functionality (vs rewriting everything)
Unforking (this includes not vendoring)
In order to help the sdk team, we should write out our requirements to be able to break the trilemma above.
The text was updated successfully, but these errors were encountered:
The current plan is to adopt the cosmos-sdk's yet to be released baseapp that will allow celestia-app to import the old forked cosmos-sdk modules. This means that we don't have to unfork from the current modules
In an ideal world, we’d have the ability to sync from a single binary && be able to reuse a lot of the functionality of the sdk without maintaining a fork or massively vendoring everything. Unfortunately, that’s not the case, and we’re stuck in a trilemma.
The trilemma (pick 2):
In order to help the sdk team, we should write out our requirements to be able to break the trilemma above.
The text was updated successfully, but these errors were encountered: