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
Your migration strategy is insightful and thorough. However, I'd like to propose an alternative: distinguishing games from the leaderboard.
By doing so, each game or set of games can have its distinct realm. The leaderboard realm can then aggregate results from these individual game realms. This approach might streamline our system and minimize potential issues.
As we're coming close to Gophercon, we have to be ready for the possibility of having to implement some late last-minute fixes on the backend realm.
So I propose the following for a good system to plan for future realm migration, which could pave the way for future migrations in the gno ecosystem.
Migrate(password, newRealm string) RealmState
function.panic("Realm-Upgrade: $newRealm")
.The new, upgraded package calls Migrate() in it, and builds its initial realm state on the data of RealmState.
The text was updated successfully, but these errors were encountered: