Two different jobs
IceRoot is designed to give digital assets a durable home under post-quantum keys. A project can create an asset there, bring one from another blockchain, or use IceRoot while preparing its own network. The asset’s life can extend beyond the chain where it began.
That calls for a deliberately small protocol: native assets, ownership, transfers, and explicit migration paths. IceRoot has no smart-contract virtual machine.
Monolythium is the programmable side of what I’m building: a network for applications and execution, with its own architecture and ecosystem. Keeping those responsibilities distinct gives each project a clear purpose.
Where LYTH fits
The plan is for LYTH, Monolythium’s token, to launch as a native asset on IceRoot. It can operate there while Monolythium’s own network is prepared. When that destination is ready, holders can move through the same migration path available to other projects.
The intended sequence is simple:
- Launch LYTH on IceRoot.
- Use it while Monolythium’s network is built.
- Open migration when the destination is ready.
LYTH uses IceRoot’s ordinary asset rules, fees, and operations. ROOT remains IceRoot’s own token, used for fees and voting. They are distinct assets; launching LYTH on IceRoot does not turn it into ROOT.
This is a concrete use for the continuity that IceRoot offers every project.
How I’m approaching the engineering
My work with Solar gave me experience with an existing delegated proof-of-stake network. For Heartwood, IceRoot’s node software, the development sequence starts with a pinned TypeScript reference, reproduces its behavior in Rust, then introduces IceRoot’s protocol changes in separate stages.
That sequence makes it easier to understand which changes come from a new implementation and which come from a new protocol rule. Established foundations provide a starting point; the new work has to stand on its own.
Mono Labs builds both projects, including their wallets and developer tools. The networks keep their own architecture, assets, and responsibilities. IceRoot serves asset continuity; Monolythium serves programmable applications. LYTH gives us a reason to use that relationship ourselves.