Welcome to this week’s Mosaic Chain developer status update. Below is a quick overview of what the team worked on this week, followed by what we’re planning to move forward with next week.
This week’s progress (Feb. 23–27)
Mosaic Chain source code published on GitHub
We published the Mosaic Chain source code on GitHub, so now Mosaic Chain’s runtime is open source.
Frontend prepared for Runtime 104 changes
We updated the frontend to be ready for the upcoming Runtime 104 changes.
Gateway: broader fixes (deleted node handling)
We continued a more comprehensive round of Gateway fixes, including proper handling of deleted nodes.
Telemetry: simplified peers + RAM charts
We worked on simplifying the peers and RAM charts on the Telemetry page.
Indexer: new features in progress
We continued development on new Indexer functionality.
Mainnet: fixed “unknown state” minting cases
We fixed a few minting flows on Mainnet that ended up in an unknown state.
Next week’s focus (Mar. 02–06)
Gateway fixes (continued)
We’ll keep pushing forward with the Gateway improvements.
Indexer: Runtime 104 support
We’ll continue implementing Runtime 104 support in the Indexer.
Minimum staking amount: UI support
We plan to build a UI for setting the minimum staking amount.
Metrics UI: fund support
We’ll continue work on adding fund support to our Metrics interface.
Hydration Bridge: development + testing (continued)
We’ll continue development and testing of the Hydration Bridge.
Coretime migration (continued)
We’ll keep working on the Coretime transition.
Current status / notes
Mosaic Chain’s code is now public on GitHub, and we’ve made progress across the frontend, Gateway, Telemetry, Indexer, and Mainnet minting stability. Next week we’ll focus on continuing Gateway work, shipping Runtime 104 support in the Indexer, and moving forward on staking, metrics, Hydration Bridge, and Coretime.
