Services
Engineering around the protocol.
Lunor Protocol is infrastructure first. Services exist so ambitious projects can ship when a module is not enough — advisory before decisions get locked in, engineering for genuinely custom requirements, and operational support around a live token. If an existing module covers what you need, we will point you at it instead of writing a proposal.
Market-presence work is partnership-based. We do not guarantee listings, rankings, or exchange outcomes — see the market presence section for what is actually offered.
- Disciplines
- Six
- Scope
- Written, with non-goals
- Delivery
- Review-gated
- Guarantees
- None on third parties
Index
Six disciplines.
Web3 Advisory
Token strategy, chain selection, architecture, utility, security planning, and exchange technology strategy.
Custom Development
Smart contracts, applications, wallet infrastructure, APIs, dashboards, automation, and custom token systems.
Market Presence Improvement
Partnership-based support for market-data and listing operations. We do not guarantee rankings or listings.
Website Development
Product sites, token dashboards, investor portals, and Web3 applications.
Recruitment
Blockchain engineers, smart-contract specialists, product, UI, and technical leadership.
Incubator
Concept, MVP, token infrastructure, launch, and the operational layer around it.
Web3 Advisory
Advisory exists to stop expensive decisions being made in the wrong order. Supply, chain, utility, and market structure constrain each other, and most of them are difficult to reverse once a token is live. Output is written: a scope, a sequence, and the parts we would advise against.
- Shape
- Fixed-scope engagement or retained advisory
- Output
- Written architecture, sequence, and non-goals
- Typical length
- Two to six weeks
- Best before
- Supply is fixed and contracts are deployed
Capabilities
- Token strategy and supply design
- Technology architecture review
- Platform and product strategy
- Blockchain and venue selection
- Token utility modelling
- Infrastructure planning
- Security and permission planning
- Exchange technology strategy
Custom Development
Engineering delivery for the parts the module set does not cover. Same standards as the products: typed boundaries, internal review on every contract change, reproducible builds, and documentation written for the team that inherits it rather than the team that wrote it.
- Shape
- Scoped project or embedded engineering
- Output
- Reviewed implementation with handover docs
- Review
- Internal review on every contract change
- Boundary
- We name what an existing module already solves
Capabilities
- Smart contract design and implementation
- Web3 applications and interfaces
- Blockchain and protocol integrations
- Wallet infrastructure
- APIs and service layers
- Operational dashboards
- Internal systems and tooling
- Automation and scheduled operations
- Custom token infrastructure
Market Presence Improvement
Market-data and listing work is operational: accurate submissions, correct supply and liquidity reporting, and coordination with the right counterparties. It is partnership-based, and outcomes are decided by third parties. Anyone guaranteeing a listing or a ranking is selling you something they do not control.
- Shape
- Partnership-based, scoped per venue
- Output
- Prepared submissions and accurate reporting
- Not offered
- Guaranteed listings, rankings, or placement
- Dependency
- Third-party review timelines
Capabilities
- Market-data submission and correction operations
- Supply and circulating-supply reporting accuracy
- Listing process preparation and documentation
- Partnership-based coordination
- Liquidity and venue readiness review
Website Development
The site is usually the first technical signal a project gives. We build product sites and dashboards to the same standard as this one: performance budgets, accessibility as a build requirement, real content architecture, and a component system that survives the next three campaigns.
- Shape
- Fixed-scope build
- Output
- Production site plus design system
- Included
- Performance, accessibility, and SEO baseline
- Handover
- Documented components and content model
Capabilities
- Product and protocol websites
- Token dashboards
- Landing pages and campaign surfaces
- Investor and stakeholder portals
- Web applications
- Design systems and component libraries
Recruitment
Technical hiring for Web3 roles, screened by people who do the work. Candidates are assessed against the actual requirement — a contract engineer and a frontend engineer fail in different ways, and a generalist screen catches neither.
- Shape
- Per-role or team build-out
- Screening
- Technical assessment by practitioners
- Output
- Shortlist with written assessment
- Scope
- Permanent and contract
Capabilities
- Web3 and blockchain engineers
- Smart contract specialists
- Backend and infrastructure engineers
- Frontend and interface engineers
- Product management
- Product and interface design
- Technical leadership
Incubator
For teams building from a concept rather than adding to a live product. Concept work, an MVP that tests the actual assumption, token infrastructure on the module set, and the operational layer that has to exist before a launch is survivable.
- Shape
- Staged engagement with review gates
- Output
- MVP, token infrastructure, launch runbook
- Gate
- Each stage requires the previous to hold up
- Selective
- We take a limited number at a time
Capabilities
- Concept development and validation
- MVP scoping and delivery
- Token infrastructure on the module set
- Technology strategy
- Product launch execution
- Growth and operational infrastructure
- Ongoing advisory
How we engage
Three rules that shape every engagement.
Scope in writing
Review gates, not milestones
Handover, not dependency
Boundaries
What we will not do.
- Guarantee listings, rankings, or exchange placement outcomes
- Operate live fund-obfuscation or transaction-tracing evasion
- Execute live trading from a public or unaudited surface
- Claim audits, certifications, or clients we do not have
- Rebuild a working system because we did not write it
- Take on an incubator engagement we do not have capacity to finish
Questions
Asked on most first calls.
Are you a development agency?
No. Lunor Protocol is infrastructure first — five live modules with eight more in development. Services exist because a module sometimes does not cover the requirement. If it does cover it, we will sell you the module rather than a project.
Can you guarantee a CoinMarketCap or exchange listing?
No, and nobody honestly can. Market-presence work is operational: accurate submissions, correct supply and liquidity reporting, and coordination with the right counterparties. Decisions belong to third parties on their own timelines.
Do you take equity or token allocations?
Incubator engagements can be structured that way, and it is discussed openly at scoping rather than assumed. Advisory and development are standard engagements by default.
Who does the work?
The same engineers who build the module set. Recruitment screening is done by practitioners in the relevant discipline rather than a generalist process.
What happens when an engagement ends?
You hold the architecture document, the implementation behind documented interfaces, the review record, and runbooks. Continued involvement is an option, not a structural requirement.
Start with a module
If your requirement is generation, vesting, distribution, staking, or market structure, the product set probably covers it. Run it in the sandbox before booking a call.
Start with the job
If you know the outcome but not the components, the solution paths sequence the modules for launching, distributing, adding utility, or expanding chains.
Next step
Start a project intake.
Five steps: what you need, your project stage, requirements, and how to reach you. No call required to get a written answer.