On-Chain Data
Holders, flow, liquidity, and treasury in one pane.
A module still in design, published as a conceptual interface so the lifecycle is visible before the backend exists.
- project
- Lunor Demo
- token
- LUNR
- module
- data
- category
- monitor
- status
- in development
Every figure in this module's demo is fabricated. No wallet connection, no signing, and no broadcast path exists from this site.
The problem
Why this module is on the roadmap
Projects reach this requirement after the basics are in place, and typically solve it with a combination of manual process and a vendor that does not know anything about the rest of their token.
Because it arrives late, it is usually the least integrated part of a project's stack — separate data, separate permissions, separate reporting.
The approach
How it will work
The module is being designed against the same project record, permission model, and service interfaces as the live modules, so it inherits identity and access rather than defining its own.
The interface published in the Console is conceptual. It shows the intended surface and states, without a production backend attached.
Capabilities
What the module does.
Shared project record
Operates against the same project, token, and role model as every live module.
Conceptual interface
The Console preview shows intended states and controls, labelled as conceptual.
Typed service boundary
Interface defined first so a production implementation swaps in without UI changes.
No fabricated timeline
Status is published as research, in development, or private beta — never a date we cannot hold.
How it works
The workflow, step by step.
- 01Open the Console preview
See the intended module surface with sandbox data.
- 02Review the states
Empty, populated, and error states are designed before the backend is built.
- 03Talk to engineering
If you need this module specifically, that changes how we sequence it.
Specification
At a glance.
- Environment
- Conceptual preview
- Data
- Fabricated sandbox values
- Backend
- Not attached
- Timeline
- No published date
Security
No production claims are made for a module that has no production backend.
- No live endpoints behind the conceptual interface
- No fabricated audit or certification claims
- Permission model inherited from the platform rather than invented per module
Full posture, including what we deliberately do not claim, is on the security page.
Use cases
Where it gets used.
Planning
Understanding where this sits in a token lifecycle before committing to it.
Architecture review
Assessing how the module would integrate with systems you already run.
Solution paths
Where this module sits in a bigger job.
FAQ
Questions asked before adopting this module.
When does it ship?
We do not publish dates. Status is shown as research, in development, or private beta, and it changes when the work changes rather than when a quarter ends.
Can we influence the sequencing?
Yes. Modules move up when a real project needs them and is willing to be the first operator. Tell us which one and what you need it to do.
Is the preview functional?
It is an interface, not a system. Controls render real states against fabricated data so the UX can be assessed, but nothing is executed.
Other modules
Same Console, same project record.
Next step
Tell us if you need this one.
Modules move up the sequence when a real project needs them. If this is the one blocking you, that is useful information.