LUNORPROTOCOL

Lunor / Protocol

Infrastructure for ambitious Web3 products.

Token infrastructure, distribution, liquidity, and monitoring — plus the engineering to wire it into your stack. One Console, five live modules, one permission model across all of them.

Explore ProductsBuild With Us

Open sandbox — no signup, no wallet connection, no call required.

lunor › terminalsandbox
lunor protocol cli · sandbox build
type `help` for commands, `ls` for modules
Lunor / protocol mapBLOCK 21,482,190SANDBOX
PROJECTPROTOCOLNETWORKLunor DemoGenerationVestingAirdropStakingMarketsRiskChainsWalletsExchangesCommunities
ModuleToken Generation
Live

Configure, review, and deploy from one workflow.

Hover a node to inspect · click to open

01
Web3 infrastructure.
02
One protocol.
03
Create.
04
Distribute.
05
Lock.
06
Stake.
07
Manage liquidity.
08
Monitor.
09
Scale.
10
Build custom infrastructure.

Product suite

One protocol. Everything your token needs.

Modules share a project, a token, and a permission model. Not thirteen disconnected tools with their own logins, their own data, and their own idea of who your holders are.
GeneratorDemo Data

Configure, review, and deploy from one workflow.

Network selection, token parameters, permissions, and a simulated deployment pipeline — the same surface a production launch will use.

Launch DemoExplore Product
Generator · Base
TokenLunor Demo Token / LUNR
Supply10,000,000
FeaturesMint · Burn · Pause
Step 5 of 6 — Review

Why a protocol

The difference is not feature count.

Any of these modules can be assembled from parts. What cannot be assembled afterwards is the thing that makes them operable two years later.

One project record

A token, its schedules, its campaigns, its pools, and its activity are the same record. Not five exports that have to be reconciled by hand every time someone asks a question.

One permission model

Roles are granted per project and environment across every module. When someone leaves, access is revoked once — not in five systems, three of which nobody remembers.

Controls in the interface

Pause, spend ceilings, treasury guards, and emergency stop are operator-accessible surfaces. A kill switch that requires a support ticket is not a kill switch.

Typed integration boundary

Modules sit behind typed service interfaces, so an existing contract or backend stays where it is and a demo implementation swaps for a production API without touching the interface.

Architecture

Project, then protocol, then chain.

Lunor Protocol sits between your project and the venues it has to talk to — chains, exchanges, wallets, communities — so each of those integrations is configured once rather than per tool.
Project
Lunor Protocol
Token infrastructure
Distribution infrastructure
Liquidity infrastructure
Utility infrastructure
Monitoring infrastructure
BlockchainsExchangesWalletsCommunities

Lifecycle

LUNR, through the stack.

A fictional demo token moving through Lunor modules: deployed, locked, distributed, staked, market structure configured, monitoring armed. Every figure is sandbox only.
  1. 01Generator

    Contract created

    LUNR deployed from the sandbox generator with ownership on a multisig.

    10,000,000
    supply
  2. 02Markets

    Liquidity allocated

    Initial market inventory set aside before any distribution runs.

    15%
    1,500,000 LUNR
  3. 03Vesting

    Allocations locked

    Contributor and investor schedules with cliffs and monthly unlock.

    20%
    2,000,000 LUNR
  4. 04Airdrop

    Community distribution

    Validated recipient set executed in idempotent batches with retries.

    10,000
    wallets
  5. 05Staking

    Staking activated

    Term pools live against the same project and token record.

    4
    term pools
  6. 06Markets

    Market structure configured

    Books, spread, and treasury guards armed with withdrawal disabled.

    3
    venues
  7. 07Risk

    Monitoring armed

    Unlock proximity, concentration, and treasury movement watched.

    6
    signals

Solutions

Organized by what you need to do.

Products are modules; solutions are jobs. Each path sequences the modules in dependency order, because applying them out of order is where the expensive mistakes happen.
01Launch a tokenGeneration, tokenomics, site, vesting, airdrop, and staking — sequenced as one launch path.View path →02Manage token distributionEmployee, investor, and community allocations with lockups, claims, and campaign records.View path →03Build token utilityStaking, gamification, swap, campaigns, and community bots on the same project.View path →04Improve market infrastructureSimulated market making, liquidity tooling, analytics, and monitoring.View path →05Migrate or expand chainsToken generation, bridging, eligibility, and risk controls for multi-chain expansion.View path →06Build custom Web3 productsArchitecture, contracts, APIs, and dashboards when the module set is not enough.View path →

Trust

What we haven't put on this page.

Lunor Protocol is new. The honest way to establish credibility is a product you can use and a clear statement of what is missing — not a wall of logos we did not earn.

No fabricated proof

There are no client logos, partner badges, volume figures, or testimonials on this site, because we have not earned them yet. What is here instead is a working sandbox.

No claimed audits

We do not list audits, certifications, or attestations we have not completed. The security page includes an explicit absence list stating what is missing.

Simulation labelled as simulation

The market-making public surface executes nothing, holds no keys, and connects to no venue. That is stated on the interface, not in a footnote.

Open sandbox

Every claim on this site can be checked in the Console without a signup, an email, or a wallet connection. Use it before you talk to us.

Read the security postureOpen the Console

What we’re building next

More modules. Same Console.

Published as conceptual interfaces so the lifecycle is visible before the backends exist. Status is honest, and there are no dates — modules move up when a real project needs them.
EngageIn Development

Token Gamification

Quests, XP, and on-chain achievements around your token.

UtilityIn Development

Token Swap

Project-branded swap infrastructure.

CreateResearch

Token Bridge

Cross-chain migration with eligibility controls.

CreatePrivate Beta

Tokenomics Builder

Allocations, unlocks, and circulating supply — modelled.

MonitorIn Development

On-Chain Data

Holders, flow, liquidity, and treasury in one pane.

EngageComing Soon

Community Bots

Telegram and Discord modules for live token operations.

MonitorResearch

Risk Monitoring

Concentration, liquidity, unlocks, and admin privileges.

EngageComing Soon

Raffle & Predictions

Community campaigns with transparent result history.

Services

When the modules aren’t enough.

Advisory, custom development, market-presence operations, sites, hiring, and incubator work — around the same infrastructure. If a module already covers your requirement, we will point you at the module.

Web3 Advisory

Token strategy, chain selection, architecture, utility, security planning, and exchange technology strategy.

Details →

Custom Development

Smart contracts, applications, wallet infrastructure, APIs, dashboards, automation, and custom token systems.

Details →

Market Presence Improvement

Partnership-based support for market-data and listing operations. We do not guarantee rankings or listings.

Details →

Website Development

Product sites, token dashboards, investor portals, and Web3 applications.

Details →

Recruitment

Blockchain engineers, smart-contract specialists, product, UI, and technical leadership.

Details →

Incubator

Concept, MVP, token infrastructure, launch, and the operational layer around it.

Details →

FAQ

The questions that come first.

What is actually built versus planned?

Five modules are live products with working interfaces you can use in the Console right now: token generation, vesting and locking, airdrop distribution, market-making simulation, and staking. Eight further modules are published as conceptual interfaces labelled research, in development, or private beta.

Is the Console connected to a real chain?

No. Every figure, address, and transaction hash in the sandbox is fabricated. There is no wallet connection, no signing, and no broadcast path from this site. Production deployment happens on separate authenticated surfaces.

Can we start with one module?

Yes, and most projects do — usually vesting or airdrop. Modules share a project record when several are in use, but none of them require the others to function.

How does this fit systems we already run?

Through typed service interfaces. An existing token contract, distribution record, or market-making arrangement can stay in place while modules are added around it. We would rather integrate than argue for a rewrite.

Are you a product company or an agency?

Products first. Services — advisory, custom development, market-presence operations, sites, hiring, and incubator work — exist around the same infrastructure for when a module genuinely does not cover the requirement.