Lemniscate

Abstract

Lemniscate is a messenger in which private communication and digital value share a single client. Every conversation is end-to-end encrypted on the user's device before it leaves it; the delivery infrastructure routes ciphertext, stores it transiently, and is designed so that it cannot read message content. Every account carries a self-custody wallet derived from a standard BIP-39 seed, so identity, encryption keys, and on-chain signing capability all originate from key material that never leaves the user's hardware.

Underneath the messenger, Lemniscate operates its own EVM-compatible chain. The network is live as mainnet (chain ID 800000), using Clique Proof-of-Authority consensus with block times of roughly four seconds and a genesis supply of 250,000,000 LMNS. The chain provides integrity anchoring, payment settlement, and the LRC-20 token standard — an ERC-20-compatible standard native to the network. During the presale, chain access runs exclusively through the Lemniscate app while the block explorer remains publicly readable; public node access opens after the presale.

LMNS, the network's native coin, is a utility token. It pays for in-app features, subscriptions, file passes, boosts, and token listings inside the Lemniscate ecosystem. It is not offered or promoted as an investment, and this document makes no promise of profit, yield, or appreciation.

This whitepaper describes the system as it exists in September 2026 and the path ahead of it. Where a component is complete, we say so; where a component is still being finalized or rolled out, we say that too. Honesty about the current state of the system is a deliberate design constraint of this project, not a disclaimer bolted on at the end.

Introduction & Problem

Daily digital communication has consolidated onto a handful of centralized platforms. This concentration created three structural problems that Lemniscate is built to address.

2.1 Messaging is centralized

The major messaging platforms are operated as closed services. The operator controls account existence, message routing, retention policy, and feature access, and can change any of these unilaterally. Even where message content is encrypted, metadata — who talks to whom, when, and how often — typically accumulates on infrastructure the user neither controls nor can inspect. Users cannot verify server behavior; they can merely trust it.

2.2 Monetization sells the user

Most large communication platforms are financed by advertising or by the commercial exploitation of behavioral data. The economic incentive of such a platform is to observe as much as possible: profiling improves ad targeting, and ad targeting pays for the service. A platform whose revenue depends on knowing its users is structurally in tension with a platform that promises privacy. Lemniscate's answer is a different business model: paid subscription tiers and in-app utility purchases, denominated in the network's own utility token — so the product is financed by people who use it, not by information about them.

2.3 Crypto UX lives apart from daily communication

Digital assets, meanwhile, live in a separate world of standalone wallet apps, browser extensions, seed-phrase rituals, and block explorers. Sending value to a friend usually means leaving the conversation, opening another application, copying an address, and hoping nothing was mistyped. The result is a strange split: people talk where they cannot transact, and transact where they cannot talk. For most users this friction is high enough that on-chain value transfer never becomes part of everyday life.

2.4 The Lemniscate thesis

Lemniscate merges the two worlds into one product with a small set of non-negotiable principles:

• Encryption happens on the client, always. Servers route and store ciphertext; plaintext is never available to infrastructure.
• Storage is transient by design. The relay is a delivery pipe with short retention windows, not an archive of user lives.
• Keys belong to the user. One standard seed phrase backs identity, encryption, and the wallet; there is no custodial account to seize or leak.
• Value transfer is a message away. The wallet is not an add-on; it is part of the same client, the same identity, and — as integration completes — the same chain.
• Say what is real. What is live is called live, what is still in development is called in development, and preliminary numbers are labeled preliminary.

The Lemniscate Messenger

The messenger is the face of the project: a full-featured communication client for Web/PWA, Android, iOS, and desktop, built from one shared codebase. It is designed to feel familiar to anyone coming from a major messaging platform — while being private by default and token-native throughout.

3.1 End-to-end encryption

All private conversations in Lemniscate are end-to-end encrypted. Key handling and cryptographic operations run exclusively on the client, implemented on top of the browser-grade WebCrypto API with NIST P-256 elliptic-curve keys for key agreement and authenticated symmetric encryption for message payloads. The properties that matter:

• Client-side only. Plaintext exists on the sender's device and the recipient's device. It is encrypted before transmission and never decrypted in transit or on the server.
• The server never reads content. The relay handles opaque ciphertext. It cannot render, scan, index, or moderate the content of private messages — a property that follows from the architecture, not from a policy promise.
• Keys never leave the device. Private keys are generated and stored locally. Account recovery works through the user's own encrypted, seed-based backup (Section 3.3), not through server-side escrow.
• Group re-keying. Group conversations re-encrypt their history keys when membership changes, so departed members do not retain access to future messages.

3.2 Feature overview

Lemniscate deliberately curates the features people actually love across the messaging landscape, rather than accumulating every feature ever shipped by anyone. The current client includes:

3.3 Seed-based encrypted backup

Chat history backup is optional, client-encrypted, and derived from the user's own seed: a BIP-39 mnemonic feeds an HKDF key-derivation step, and the resulting key encrypts backups with AES-256-GCM before anything is uploaded. Write access to a backup slot is authorized by a signature from the user's own key. The storage side is zero-knowledge: it holds ciphertext it cannot open. The same mechanism powers device transfer — a new phone restores identity and history from the seed without any server ever seeing readable data.

3.4 Ephemeral relay storage

The relay is engineered as a delivery system, not an archive. Encrypted messages are held until all linked devices of the recipient have fetched them, then deleted. Status/story objects expire automatically according to the author's tier (24 hours on Free, 48 hours on Premium, 30 days on Business), and the author can withdraw a status for all recipients at any time. Large encrypted files travel through a chunked media store with a bounded network retention window measured in days. This retention posture minimizes what could ever be disclosed, leaked, or subpoenaed — data that no longer exists cannot be exposed.

3.5 App screens

Lemniscate Encrypted

Search chats

N NovaVoice note · 0:12 09:412

D Design GuildMara: final logo vote is live 09:125

L LMNS Updates ✓Mainnet block #1,204,551 sealed 08:47

Z Zeynep+25 LMNS received Yesterday

S SupportTicket #1042 resolved ✓ Yesterday

Chat list — encrypted by default, value inline

Wallet Self-custody

Mainnet

Total balance

1,284.50 LMNS

≈ $321.13 at presale reference price

0x7A3f…9c21 · BIP-39 self-custody

SendReceiveHistory

L LMNSLemniscate · native 1,284.50≈ $321.13

T LTTLRC-20 · chain token 5,000.00no monetary value

Wallet — one seed, multiple networks

3.6 Tiers & pricing

Lemniscate is financed by its users, not by their data. Subscriptions are paid exclusively in LMNS; there is no card checkout inside the app. Prices below are denominated in USD and converted to LMNS at the current in-app rate at purchase time.

Business introductory pricing applies for the initial three months after launch. All prices are subject to change before public launch; the LMNS conversion rate is displayed at checkout.

The Lemniscate Chain

Lemniscate runs its own layer-1 blockchain rather than renting block space elsewhere. The chain is EVM-compatible: it speaks the same JSON-RPC interface, address format, and transaction semantics as other EVM networks, and can be added to any standard EVM wallet by entering its chain ID and RPC endpoint — exactly as users already do for other EVM networks.

4.1 Network parameters

4.2 Consensus and decentralization path

The chain uses Clique Proof-of-Authority: a small, known set of sealer nodes signs blocks in rotation. PoA is a pragmatic choice for this stage — it yields fast, predictable blocks, requires no energy-intensive mining, and lets the network operate reliably while the ecosystem is small. It is also, unambiguously, a centralized consensus model, and we describe it as such.

Two properties temper that centralization today, and a roadmap reduces it tomorrow:

• Anyone can verify. The public block explorer exposes every block and transaction. After the presale, full nodes will be runnable by anyone: a full node independently validates every block and transaction; it does not seal blocks (there is no stake or mining), but it removes the need to trust the operator's word about chain state.
• Validator expansion. The roadmap foresees widening the sealer set to additional independent operators, with the longer-term goal of a broader validator model after mainnet. Concrete milestones will be published as they are committed.

4.3 LRC-20 — the native token standard

LRC-20 is the chain's fungible-token standard. It is intentionally ERC-20-compatible: the same interface, events, and tooling assumptions, so existing EVM libraries and wallets work without modification. On top of the raw standard, Lemniscate adds a product layer:

• In-app token creation. A guided creator lets users deploy an LRC-20 token signed from their own device — no contract code to write.
• Paid token listing. Listing a token in the wallet's curated directory costs a one-time fee of $2,500, paid in LMNS in-app. The fee funds review and keeps the directory free of drive-by spam. Users can always add any token manually by its symbol or address at no cost — the fee applies to the curated listing, not to the standard itself.
• Block explorer. A public explorer shows blocks, transactions, supply, and every LRC-20 token on the network in real time.

4.4 Interoperability — ERC-20, BEP-20, SPL and beyond

A chain is only useful if it connects to the ecosystems people already use. Lemniscate approaches interoperability in two tiers: native compatibility inside the EVM family, and cross-chain swaps toward everything else.

• EVM family — native. LRC-20 implements the ERC-20 interface, and BEP-20 on BNB Smart Chain is itself an ERC-20 derivative — the three standards share one interface family, one address format, and one key-derivation path. In practice: the same BIP-39 seed that runs a Lemniscate account controls the same address on Ethereum, BNB Smart Chain, and every other EVM network, and any standard EVM wallet can add the Lemniscate chain by entering its chain ID and RPC endpoint.
• External EVM assets today. The in-app wallet already manages assets on external EVM networks alongside the Lemniscate chain — the swap rails to external networks have been exercised end-to-end; production swaps open when the presale ends.
• Non-EVM standards — via swaps. Standards such as SPL (Solana) live on different virtual machines with different address and signature schemes; there is no direct key or contract compatibility with any EVM chain. The path to those ecosystems is cross-chain swaps against external networks, planned in the long-term phase of the roadmap (Section 7).

Architecture

The system is a three-layer stack: clients that hold all keys, a relay that moves ciphertext, and a chain that anchors value and integrity. Each layer is engineered to know as little as possible about the layers around it.

5.1 Clients

All client platforms — Web/PWA, Android, iOS, and desktop — are built from one shared codebase, so the security model is identical everywhere. Clients generate keys, encrypt and decrypt everything, render the UI, and sign chain transactions. Native apps add capabilities the web cannot provide, such as the Bluetooth mesh transport and on-device audio transcription.

5.2 Relay

The relay is intentionally boring: it authenticates devices, queues encrypted payloads, fans messages out to linked devices via per-device cursors, hosts the chunked store for large encrypted files, and sends content-free push notifications. Its retention rules (Section 3.4) are short by design. It cannot decrypt anything it carries, and for 1:1 messages a sealed-sender mode removes the sender identity from what the relay can observe.

5.3 Chain

The chain layer provides what a relay never can: durable integrity and neutral settlement. Payments, call-session records, token issuance, and the curated token directory anchor here. Because the chain is EVM-compatible, the wallet in the app is a genuine self-custody EVM wallet: it derives from a standard BIP-39 seed, and the same seed can be imported into widely used EVM wallets. The wallet supports multiple networks, including external EVM networks alongside the Lemniscate chain.

The LMNS Token

6.1 A utility token, deliberately

LMNS is the native coin of the Lemniscate chain and the single unit of account inside the app. It is a utility token: its purpose is to be used, not held in expectation of profit. LMNS pays for:

• Subscriptions — Premium and Business tiers (Section 3.6) are payable exclusively in LMNS.
• File passes — expanded transfer limits for large encrypted files.
• Boosts and in-app features — channel boosts, group-call seat extensions, collectible usernames, paid channels, gifted subscriptions.
• Token listings — the one-time $2,500 curated-listing fee for LRC-20 tokens is settled in LMNS.
• Network fees — gas for LRC-20 operations on the chain, while ordinary messenger usage remains gas-free for users.
• Planned utility expansions — as the roadmap ships (Section 7), top-ups of the planned wallet debit card are intended to be payable in LMNS, extending the same utility model rather than changing it.

LMNS is not an investment. It confers no equity, no dividend, no revenue share, no governance right over Lemniscate Labs LLC, and no claim against the company. Nothing in this document is an invitation to buy LMNS in expectation of appreciation. Purchase LMNS if — and only if — you want to use the things it unlocks.

6.2 Presale — a transparent, volume-based price schedule

An initial distribution of LMNS is conducted directly inside the Lemniscate messenger. The presale deliberately avoids date-based phase pricing ("price rises next month"), because dates say nothing about a project's traction. Instead, the package price follows one public number: how much has actually been sold. A progress bar shows cumulative presale sales from 0 to the presale cap; the current price is a pure function of that bar — no dates, no announcements, no discretion.

The schedule in one sentence: the price starts at $0.25 and doubles with every quarter of the presale allocation that is sold — reaching $0.50 when 25% is sold, $1.00 at 50%, $2.00 at 75%, and $4.00 at the cap. Within each quarter the price moves in small fixed steps with every 1% sold (+$0.01 per 1% in the first quarter, then +$0.02, +$0.04, and +$0.08 per 1%), so there is never a cliff — only a steadily rising ladder that climbs faster the further the sale progresses.

Properties of this design, stated plainly:

• Verifiable by anyone. The progress bar and the price rule are public; every buyer can recompute the current price from the bar. There is nothing to announce and nothing to trust.
• The price never falls and never skips. Each purchase is settled entirely at the price displayed at checkout; the next step applies from the next purchase onward.
• The schedule responds to reality. If demand is low, the price simply stays low; if adoption accelerates, the price accelerates with it. The schedule promises a rule, not an outcome.
• One price feed. The buy screen, the in-app wallet, and invoices all read the same price source — there is exactly one current price at any moment.
• Only real sales move the bar. Affiliate hold-balances, gifted subscriptions, and team allocations do not count toward the progress bar.

Further mechanics:

• Purchases are made directly inside the Lemniscate messenger after identity verification (KYC): open the wallet, tap “Buy LMNS” and pay with USDC / USDT from the built-in wallet (Ethereum, Polygon, BNB Smart Chain) — top-ups from any external wallet such as MetaMask are supported. The live price and presale progress are published at lemniscate.network/buy.
• Delivery is automatic and immediate: the package is credited to the buyer's Lemniscate in-app wallet, and every delivery writes an on-chain purchase receipt (order number + buyer address) into the project's custody wallet — publicly verifiable in the block explorer.
• Affiliate commissions are credited instantly to the referrer's in-app wallet and are immediately spendable inside Lemniscate (plans, gifts, tips); like all LMNS during the presale, they cannot be swapped or withdrawn until the exchange listing.
• During the presale, in-app swap functionality for LMNS is disabled; LMNS remains fully usable for subscriptions, features, and token listings.

6.3 Token allocation — preliminary

The allocation below is preliminary and indicative. It reflects the current working plan and is published for transparency, not as a commitment. Final tokenomics — including vesting schedules, emission details, and any changes to the split — will be published before mainnet launch, and the mainnet genesis will follow the published final version.

Roadmap

The roadmap below states what is done, what is in progress, and what is planned. Dates beyond the current phase are targets, not promises; see the forward-looking-statements notice in Section 9.

Team & Entity

Lemniscate is developed and operated by Lemniscate Labs LLC, a limited liability company organized in the United States. The company builds the wider Lemniscate ecosystem — the Lemniscate messenger and chain, and related infrastructure — and operates its own servers for the application relay, the chain nodes, and the web presence.

The project is led by its founder, Simon, who directs product, engineering, and operations. In keeping with the project's privacy stance, extended personal biographies are intentionally omitted from this draft; verified entity and contact information is available through official channels listed on lemniscate.network and lemniscate.network.

Risk Factors & Legal Notice

Read this section in full before acting on anything in this document. It qualifies every other section.

9.1 No offer, no solicitation

This whitepaper is an informational description of a technology project. It is not a prospectus, an offering memorandum, an offer to sell, or a solicitation of an offer to buy any security, financial instrument, or asset in any jurisdiction. No regulatory authority has reviewed or approved this document. Any distribution of LMNS occurs, if at all, under separate terms published through official channels, and those terms — not this document — govern.

9.2 Not investment advice

Nothing herein constitutes investment, legal, tax, or accounting advice. LMNS is a utility token intended for use within the Lemniscate ecosystem. It is not designed, offered, or promoted as an investment, and no statement in this document should be read as a prediction or promise of value appreciation. Consult your own qualified advisers before making any decision involving digital assets.

9.3 Risk of total loss

Digital assets are volatile and can lose all value. Software can fail; cryptographic schemes can be weakened; keys can be lost — and with a self-custody design, lost keys and lost seed phrases are unrecoverable by anyone, including us. You should not commit funds you cannot afford to lose entirely, and you should assume that participation in any early-stage token ecosystem carries a realistic possibility of total loss.

9.4 Presale scope and external access

Until the end of the presale, LMNS remains inside the Lemniscate platform: external RPC access, third-party wallets (such as MetaMask) and external transfers or swaps are deliberately closed and open when the presale ends. Nothing in this document is an offer, a solicitation or investment advice; token values can rise and fall, up to total loss.no monetary value, and may be reset, altered, or discarded at any time before or during the transition to mainnet.

9.5 Development-stage disclosure

Several capabilities described here are explicitly in development: full on-chain settlement of in-app balances (in-app balances run on the platform ledger, with deposit/withdrawal rails to the chain; on-chain settlement is being rolled out), the Bluetooth mesh transport (native apps, phased), the wallet debit card (dependent on licensed card-issuing partners and jurisdiction-specific requirements), validator-set expansion, and exchange listing. The presale price schedule in Section 6.2 carries draft parameters until final publication. Preliminary tokenomics are exactly that — preliminary. Where this document marks something as planned, in development, indicative, or draft, no assurance is given that it will ship, ship on time, or ship in the described form.

9.6 Jurisdiction restrictions

Access to LMNS, the presale, or parts of the Lemniscate service may be restricted or unavailable in certain jurisdictions, including jurisdictions where the offer or use of digital assets is limited or prohibited. It is your responsibility to ensure that your participation complies with the laws applicable to you. Lemniscate Labs LLC reserves the right to restrict availability by jurisdiction and to require identity verification where legally necessary.

9.7 Forward-looking statements

This document contains forward-looking statements — including the roadmap, planned features, validator expansion, mainnet, and listing intentions. Such statements are based on current expectations and assumptions and are subject to known and unknown risks and uncertainties. Actual results may differ materially. Lemniscate Labs LLC undertakes no obligation to update forward-looking statements except as required by law.

9.8 No warranty; limitation

The Lemniscate software and network are provided on an "as is" and "as available" basis without warranties of any kind, express or implied, to the maximum extent permitted by applicable law. This document may contain errors and will change; the version identifier on the cover governs which draft you are reading. In case of conflict between this document and the applicable terms of service, the terms of service prevail.