The infrastructure layer for durable memory and decentralized intelligent services.
Cosmos SDK · IBC
Institutional validator
Cosmos chain · IBC
Cosmos chain · IBC
Ecosystem campaigns
Institutional validator
Market data
ZK Layer 1
ZK proving network
EVM Layer 1
Cosmos chain · IBC
Validator
Validator
Validator
Wallet support
EVM support
Cosmos SDK · IBC
Institutional validator
Cosmos chain · IBC
Cosmos chain · IBC
Ecosystem campaigns
Institutional validator
Market data
ZK Layer 1
ZK proving network
EVM Layer 1
Cosmos chain · IBC
Validator
Validator
Validator
Wallet support
EVM support
Modern applications increasingly rely on permanent data, identity, verifiable execution, settlement and trust, yet these capabilities typically come from different vendors. Lumera unifies them within a single architecture. As software becomes more autonomous, with agents that act, spend and make decisions without human intervention, the need for these capabilities to work together only grows.
Lifecycle of a single file being stored
import { createLumeraClient } from "@lumera-protocol/sdk-js"
const client = await createLumeraClient({
preset: "mainnet", signer, address
})
// hashes the file, registers on chain, stores across supernodes
const task = await client.Cascade.uploader.uploadFile(file, {
fileName: "report.pdf",
isPublic: true,
expirationTime
})
import { Lumera } from "@lumera-protocol/sdk-js"
const lumera = new Lumera({ apiKey: process.env.LUMERA_API_KEY })
const memory = await lumera.memory.open(agentId)
await memory.remember({
user: "Alice",
preference: "Window seat"
})
const context = await memory.recall()
The same primitive in two shapes: a file an application stores, or a fact an agent needs to still have next session.
Lumera splits the work in two. The blockchain keeps the permanent record of what was asked for, what was paid, and what was proven. The heavy lifting happens off to the side, on SuperNodes that put up their own money as collateral and lose it if they cheat. So the network can take on much more work without the record getting slower or less secure.
Launch your application, secure the network, store the data. Each one is open today.
The infrastructure layer for durable memory and decentralized intelligent services.
An agent’s identity is an API key belonging to someone else. Revocable, non-portable, carrying no independent reputation. It cannot accumulate a record, delegate authority, or be held accountable for anything.
Lumera ID is the universal on-chain principal for users, agents, applications, data assets and providers. It is a container that accumulates claims over time.
Delegation chains are the enterprise wedge. Grant an agent a budget class or a dataset. Scoped, time-bound, revocable, enforced on-chain.
Nothing proves what model ran, what data it consumed, what it cost, or whether it was the model advertised. The client trusts the provider completely.
Agent state lives in provider-controlled databases. Switch providers, lose context. No memory the agent owns, no institutional knowledge that accumulates, no data sovereignty.
Cascade is content-addressed erasure-coded storage with BLAKE3 Merkle proofs. Alongside it sits a leaderless quorum-replicated database for hot state, the tier an application reads from between writes. Large values overflow from one to the other transparently.
Payment rails assume a human at the end. An agent cannot hold a balance, earn revenue, or settle a transaction on its own behalf.
LUME is the settlement, staking and governance token. Everlight funds what per-use fees cannot: an artifact that must stay available for years, a verifier ready before it is needed, a node paid for capacity.
Providers are often chosen based on a brand name, a website or a recommendation. Traditional reputation systems record opinions rather than verifiable work, and they can be bought, gamed or abandoned by moving to a new account.
Every job leaves a signed record of who performed it, what was delivered and whether the work was verified. Over time, those records build an evidence-based picture of who delivers, earned rather than claimed and tied to a persistent identity.
Every connection in the graph represents a completed job. Not a review, not a score someone assigned, but work requested, delivered, checked and paid for.
Three classes of execution, three consequences when something goes wrong. They never collapse into each other.
Quality moves the trust graph. Nothing is slashed.
If runner and verifier disagree, that is objective evidence. No judgement needed.
The protocol never fires an irreversible action on its own.
Durable memory shipped first because every other capability depends on it. Hover over each capability to see what supports it and which parts of the network it uses.
LUME pays for storage, backs the operators who hold it, earns them standing on the network, and gives holders a vote. Every one of those jobs shows up as activity you can look up on the explorer.
Storing a file, keeping it stored, checking that it is still there, running an agent: every one of those is paid for in LUME. The more the network is used, the more LUME the work requires.
To do the work at all, an operator has to lock up LUME first. Get caught returning a wrong result, faking a receipt or going silent, and they lose it. The busier the network gets, the more LUME sits locked up behind it.
Anyone can claim to be reliable. Here, standing is backed by LUME an operator would forfeit, so a good reputation is one they paid to build and can still lose.
Fees, settings and upgrades are decided by a vote of LUME holders, and the operators with the longest record of good work carry extra weight.
Each turn of the wheel makes the next one cheaper to win.
Durable memory, identity, verifiable execution and settlement behind one SDK and one economic model. Build against stable interfaces.
Fund a Global Credits balance once, on-chain. Provider-agnostic from the start.
Written once. Readable from any framework, agent or model. Provably intact decades from now.
An agent that forgets is a demo. Every session starts from scratch. The same context must be sent and paid for again, while anything the agent learned about a customer last week disappears.
What memory does exist usually lives in a database controlled by someone else. It can be deleted, lost during a migration or quietly altered, with no way to prove otherwise.
Lumera stores each fact once, ties it to an identity the agent controls rather than a vendor account, and continuously proves the data is still there and unchanged. Your agent reads and writes through an SDK. No wallet, no gas and no blockchain expertise required.
Read the Cascade paper →Pay once and the fact is kept. There is no renewal to forget and no bill that grows with age.
The network keeps re-proving that the data is still held, continuously, and anyone can check the result.
Memory belongs to the identity that created it, not the application or vendor used to write it. Switch models or frameworks and the memory stays with you.
Paying an operator to hold data is not the same as knowing they still have it. The network settles that question continuously, on its own, without anyone asking.
import { Lumera } from '@lumera-protocol/sdk-js'
const lumera = new Lumera({ apiKey: process.env.LUMERA_API_KEY })
// 1. open the memory an agent writes under
const memory = await lumera.memory.open(agentId)
// 2. remember a fact once, it is kept forever
await memory.remember({ units: 'metric' })
// 3. recall it from any framework or model
const context = await memory.recall()
// 4. ask the network to prove it is still there
const proof = await memory.prove(context.id)
No. A vector database makes memory searchable and object storage makes it cheap; neither can prove the data is still there, and both tie the memory to an account you rent. Lumera sits underneath as the permanent, provable copy the agent owns: pay once instead of monthly, retention proven by Merkle challenge instead of promised in an SLA, and every read and write adding to the record the agent carries to its next counterparty. Keep your index, point it here.
No. You call the SDK with an API key, the same as any other service. That key is how you authenticate to Lumera. It is separate from the on-chain identity your data is written under. There is no gas to budget, no token to hold, and no seed phrase for your users.
Nothing is lost. You pay once at the point of writing, and operators keep being compensated for holding it after that, continuously, out of protocol rewards and a share of network fees. Retention does not depend on a subscription staying current, which is the difference between permanence funded and permanence promised.
Yes, and you do not swap anything out. The MCP connector mounts underneath the harness you already run, so an agent in LangChain, CrewAI or anything else that speaks MCP keeps its loop exactly as it is and gains memory beneath it. There is also a Python and TypeScript SDK, and an HTTP API for everything else.
Not in the sense of erasing it, and that is deliberate: a memory you could quietly remove is not evidence. What you control is what goes in, and you can supersede a record so the current answer changes while the history stays intact. Treat it the way you would an append-only ledger, and keep anything you may need to erase out of it.
Three calls and an API key. The network keeps the data and keeps proving it is still there.
Cryptographic passports that enforce permissions and delegated authority for people, applications and autonomous systems. Every action can be traced to the identity authorized to take it.
An API key grants access. An identity carries a permanent record of what it can do, what it has done and where it has delegated authority.
The developer documentation carries the detail this page leaves out: the interfaces, the guarantees, and how it fits with everything else.
Every action produces a cryptographic receipt showing what was done, so anyone can independently verify the result rather than take it on faith.
A receipt is more than a log saying the job finished. It records what was used, what was run and what came back, giving another party what it needs to replay the work and compare the result.
The developer documentation carries the detail this page leaves out: the interfaces, the guarantees, and how it fits with everything else.
Protocol-native settlement, escrow and incentives for decentralized services. Applications and agents can hold budgets, pay providers and earn payment for completed work.
No invoice. No net-30. No uncertainty over who holds the funds while the work is being completed. Each stage is recorded and enforced by the protocol.
The developer documentation carries the detail this page leaves out: the interfaces, the guarantees, and how it fits with everything else.
Trust built from verifiable protocol activity rather than from intermediaries or reputation alone, accumulated one paid job at a time.
It is not a review or a score assigned by someone else. An edge connects two identities because work was requested, delivered, verified and paid for, with every stage recorded by the protocol.
Each completed job leaves a signed receipt. Together, those receipts create a durable record of who consistently delivers.
Click a participant to see what the network knows about them.
Trusted for research. Untested in finance. One universal score cannot tell you the difference.
Every edge represents a verified, paid job. Copying the data does not transfer the history to another identity.
Building a false record requires bonding real LUME against work that can be independently checked. Failed verification can put that stake at risk.
More jobs improve routing. Better routing attracts better work. Each strengthens the other.
The developer documentation carries the detail this page leaves out: the interfaces, the guarantees, and how it fits with everything else.
The architecture, specifications, and design decisions behind the protocol.
How durable memory, identity, verifiable execution, settlement and trust combine into a single architecture, and why autonomous software needs them together rather than assembled from separate vendors.
How LUME pays for work, secures the network through staking, and ties provider incentives to verified delivery. Covers supply, fee flows and the penalties behind failed verification.
The wordmark, symbol, color values and type that make up Lumera. Take what you need. Use it accurately and in good faith, under the terms further down this page.
24pxGreen is a fill color. As small text on a light background it does not carry enough contrast, so use Teal there instead.
You do not need to ask permission to refer to Lumera accurately. You do need to be straight about what your relationship with the project actually is.
Refer to Lumera as it is. Do not use the marks in a way that misleads people about who made something, who stands behind it, or what it does.
Using the marks does not make you a partner. Do not present your project as endorsed, certified, audited or affiliated unless we have agreed that in writing.
The marks may not appear in connection with fraud, scams, phishing, malware, impersonation of Lumera or its team, unauthorized token sales, or any unlawful activity.
Use the files as supplied. No recoloring, distortion, rotation, effects, or combining the marks with other logos, words or shapes to form something new.
The marks stay ours. Do not register them, or anything confusingly similar, as a trademark, company name, domain, social handle or app-store listing.
This is a limited, revocable license to use the marks under these terms. If we ask you to stop or to change how you are using them, please do.
NTT DOCOMO GLOBAL, Inc., part of the NTT DOCOMO Group, has joined Lumera as a validator, contributing to the security and decentralization of the Lumera network. NTT DOCOMO GLOBAL works across global digital and technology…
Lumera has added 1XP as a validator on the network. 1XP operates validator infrastructure across multiple ecosystems, builds public intelligence tools used by operators…
Lumera Protocol is partnering with Lagrange, the team behind DeepProve and the ZK Prover Network, to bring permanent, provable storage to verifiable AI. The integration…
FalconX, one of the world’s leading institutional digital asset prime brokers, is now a validator on Lumera. The firm serves more than 2,000 institutional clients…
Testnet goes live June 30, 2026. Mainnet to follow. 📣 Testnet announcement. Everything in this post applies to Lumera Testnet. Mainnet users do not need to take any…
Lumera testnet upgrade proposal v1.12.0, codenamed Aurora Zenith, is now live for a 48-hour governance vote. The upgrade is estimated to execute at block height…
Lumera has reached a major milestone. With the 1.8.5 release, some of the most anticipated upgrades in the project’s history are now live: SuperNodes are running on…
Lumera’s EVM upgrade has been running on Testnet since late June, and the results have been smooth which means that Mainnet is next. The upgrade is coming soon, and when…
Lumera has upgraded to full EVM compatibility on testnet. If you have an existing Lumera wallet, your account needs to be migrated before you can use MetaMask, access…
If you’re ready to explore the Lumera ecosystem, one of the first steps is setting up your wallet so you can hold and use LUME, the native token of Lumera Protocol. In…
August’s headline story was the Midnight Network partnership, bringing Cascade’s permanent, privacy-compatible storage layer to the Midnight ecosystem. The partnership…
Inference prices have fallen at a median of roughly fifty times per year since 2020, and the gap between the best frontier models is now a few percent and changes hands…
Q2 2026 was Lumera’s strongest quarter yet for on-chain activity and infrastructure growth — a period of consolidation after Q1’s Foundry Season 2 surge, capped by two…
Validators secure the chain. SuperNodes deliver its services.
Their job is running the blockchain.
They perform the network’s services. The chain records the commitments, proofs and results.
Lumera splits the work in two. The blockchain keeps the permanent record of what was asked for, what was paid, and what was proven. The heavy lifting happens off to the side, on SuperNodes that put up their own money as collateral and lose it if they cheat. So the network can take on much more work without the record getting slower or less secure.
Storing a file forever means someone has to be paid to keep it for years. Everlight is the fund that does that. Part of every payment and block reward goes in, and it pays operators on an ongoing basis to hold data and stay ready, so keeping your file is always worth their while.
A share of network rewards, a share of every fee, and returns on the fund itself.
On a steady schedule, for as long as they keep holding the data.
Operators earn for the space they keep available, not only for the work that comes in.
Coming next: a fund large enough that its returns alone cover storage, without ever spending the fund.
Bond LUME, serve the network, and take the full service fee on every verified job.
Three revenue streams fund the people who secure the chain and the people who hold the data. Every one of them is paid in LUME, settled on chain, and tied to work that was actually done.
Agents are already doing work that matters. What they lack is everything that makes work accountable: a memory that survives, an identity of their own, evidence of what they did, and a way to be paid for it. Lumera is building all of it on one architecture.
Memory is live on mainnet today. The other four are being built on it.
An agent remembers a customer across every session, every model and every framework it ever runs on, and can prove the record has not changed. Context stops being something you rebuild on each call.
The agent carries its own passport rather than an account you rent for it. Permissions are explicit, delegation does not mean sharing a secret, and the history follows the agent wherever it works.
Every job leaves evidence of what ran. Another operator can re-derive the result rather than take it on faith, so a disagreement is settled against the record instead of against whoever is larger.
An agent holds a budget, hires another agent, and pays it when the work checks out. No invoice, no human closing the loop, no counterparty risk on either side.
A record of who actually delivered accumulates from paid work. Routing decisions get made against evidence, and a bad history cannot be shed by opening a new account.
An agent with an identity of its own, a budget you set, a receipt for every step it took, and a reputation it has to earn. You hand it a goal, not a script.
Please read this section carefully. It explains the most important difference between Lumera and a typical website.
The Lumera Protocol is a public blockchain. The following are recorded on, or made available through, a decentralized network that anyone can inspect:
We do not control this network. We cannot change, hide or delete information recorded on it, and neither can anyone else acting alone. Other people may be able to link a wallet address to you through your own disclosures, exchange records or analysis of on-chain activity.
Our explorers, dashboards and APIs display this public data. They do not make it any more or less public than it already is.
Do not upload Personal Information, whether yours or anyone else’s, to Cascade or the blockchain. Files uploaded as private are access-controlled, but they are still stored by independent SuperNode operators, and they are designed to be retained permanently. If you must store sensitive content, encrypt it on your own device before uploading.
The Lumera Foundation, together with its officers, directors, employees, contractors, consultants, agents, affiliates, predecessors and successors (collectively, “Lumera Foundation”, “we”, “us” or “our”), respects your privacy.
This Privacy Policy explains how we collect, use and share Personal Information when you use lumera.io, docs.lumera.io and any other website, application, or network interface we operate that links to this Policy (together, the “Services”). It also explains your rights and choices, and how to contact us.
This Policy does not cover the Lumera Protocol itself. The Lumera Protocol is open-source software run by independent validators, SuperNodes and other network participants that we do not control. It also does not cover third-party wallets, exchanges, explorers or other services, even if we link to them.
We and our service providers may process Personal Information in the United States and other countries whose data protection laws may differ from those where you live. Section 8 explains how we handle international transfers.
“Personal Information” means any information that relates to an identified or identifiable individual. We collect it directly from you, automatically when you use the Services, and from third parties.
Communications. When you email us, fill out a form, or message our team on a community platform, we receive your contact details, the content of your message and any attachments, and the time and date.
Updates and newsletters. If you sign up for updates, we collect your name and email address.
Programs and partnerships. If you apply to or take part in a validator, SuperNode, delegation, grant, ecosystem or partnership program, we collect business contact details, organization information, node and infrastructure details, and wallet addresses. Where a delegation, grant, token agreement or legal obligation requires it, we may also ask for identity, company registration or sanctions-screening information.
Events. If you register for an event we host or co-host, we collect your contact details and any information needed to organize the event.
Faucet, claims and migrations. When you request testnet tokens, claim tokens from the legacy Pastel network, or migrate an account, you give us a wallet address and, where relevant, a signed message. Much of this is also recorded publicly on chain.
Campaigns and rewards. If you take part in a quest, learn-to-earn or community rewards program, we collect the wallet address and any other details the program requires, such as a social handle.
Job applications. If you apply for a role, we collect your résumé and the information you choose to share.
Where the law requires it, we will tell you whether you must provide certain Personal Information and what happens if you don’t.
Usage and device information. When you visit the Services, our hosting and content delivery providers process standard request data, including your IP address, browser and device type, the pages you request, the referring page, and the date and time of your visit. lumera.io does not set cookies of its own. Where we or a provider use cookies, browser storage or similar technologies (collectively, “Cookies”), Section 2C sets out which ones and why.
Network interface logs. When you or your application use our public endpoints, our servers log your IP address, request metadata, timestamps and the addresses or records queried. This covers RPC, REST/LCD, gRPC and EVM JSON-RPC nodes, the SN-API gateway, the LumeScope API and the faucet. We use these logs to operate the endpoints, enforce rate limits and prevent abuse.
Wallet connections. When you connect a wallet to one of our interfaces, we receive your public wallet address and the transactions you ask to sign. We never receive your private keys or seed phrase, and we will never ask for them.
Social media and community platforms. If you interact with our accounts or communities on X, Discord, Telegram, YouTube or similar services, or post publicly about Lumera, we may receive your profile information and the content of your posts or messages.
Partners and co-hosts. Event co-hosts and program partners may share information you agreed to give them, such as attendee lists.
Compliance providers. Where a program or the law requires it, we may receive sanctions-screening or verification results from service providers.
Public blockchain data. We read public on-chain data to operate our explorers, dashboards and programs.
Providing and securing the Services. Operating, maintaining and protecting the Services, including rate-limiting and abuse prevention for public endpoints and the faucet.
Communicating with you. Answering questions, sending administrative notices, and telling you about changes to our terms and policies or to the network, such as required upgrades.
Programs and partnerships. Evaluating applications, administering agreements, making delegations, and distributing grants and rewards.
Events. Organizing, staffing and running events.
Marketing. Sending news about Lumera and the ecosystem. You can opt out at any time (see Section 6), and where the law requires consent we ask for it first.
Understanding and improving the Services. Analyzing usage trends to improve content and features and to develop new ones.
Integrity of campaigns. Detecting duplicate accounts, bots and other attempts to game quests, faucets or reward programs.
Compliance and legal. Sanctions screening, verification where required, tax and accounting, responding to lawful requests, enforcing our terms, and protecting our rights and the rights of others.
If you are in the European Economic Area or the United Kingdom, we process your Personal Information only when we have a legal basis to do so:
Consent, for example for marketing emails or non-essential Cookies.
Contract, where we need the information to provide something you asked for or to perform an agreement with you.
Legal obligation, for example to comply with sanctions law or a court order.
Legitimate interests, such as securing and improving the Services and preventing fraud and abuse. We rely on these interests only where they are not overridden by your rights and interests.
No analytics or advertising Cookies on lumera.io. We do not use analytics cookies, advertising pixels or similar tracking technologies on lumera.io. If that changes, we will update this Policy, and where the law requires consent we will ask for it before any non-essential Cookie is set.
Strictly necessary browser storage. lumera.io keeps a small amount of data in your browser’s own storage so the site works as you left it: your light or dark theme preference, and a short-lived cache of partner logos. This stays on your device and is not transmitted to us.
Documentation site. docs.lumera.io is hosted for us by Mintlify, which stores an anonymous identifier in your browser and serves assets from its own content delivery network. Mintlify processes that information under its own privacy policy.
Live network data. Some pages load live network statistics directly from blockchain node endpoints, some of which are run by independent infrastructure providers. Those providers receive your IP address and basic request information when the page loads.
Third-party content. The Services may embed content or link to sites run by others, such as YouTube videos, social media features, wallets and explorers. Those third parties may collect information about you under their own policies, and we do not control what they collect.
We do not sell your Personal Information. We share it only as described in this Policy, or with your consent:
Service providers that work on our behalf, including website hosting and content delivery, documentation hosting, email delivery, event management, customer support, compliance screening, auditing and professional advisors.
Affiliates that help us operate the Services and programs.
Program and event partners, when you take part in a co-hosted event, campaign or program and have been told your information will be shared.
Public posts. Information you post in public channels, such as Discord, Telegram or GitHub, can be seen by anyone.
Corporate transactions. A buyer, successor or assignee, as part of a merger, reorganization, sale of assets or similar transaction, including in insolvency proceedings.
Legal and safety. Authorities or other parties, where we believe in good faith that disclosure is needed to:
We may also use and share information that has been aggregated or de-identified so that it no longer identifies you, unless the law prohibits it.
We are not responsible for the privacy practices of wallets, exchanges, bridges, explorers, community platforms, node operators, SuperNode operators or any other third party. That applies even when the Services link to them or display their data. A link is not an endorsement. Please review their privacy policies before you use them.
We use physical, organizational and technical safeguards designed to protect the information we hold. No system is perfectly secure, so we cannot guarantee the security of your information.
You are responsible for the security of your wallet, devices and credentials. Never share your seed phrase or private keys with anyone, including anyone claiming to represent Lumera. If you see an impersonation or phishing attempt, report it to security@lumera.io.
Your choices. You can decline to share certain information, but some features or programs may then be unavailable to you.
Access, correction and deletion. You may ask us to access, correct or delete the Personal Information we hold about you, using the contact details in Section 12. Some information may be kept in backups or archives, or for fraud prevention, legal compliance or other legitimate purposes, as the law allows.
Marketing. You can unsubscribe from marketing emails at any time with the link in each email or by contacting us. We may still send you administrative messages.
If you are in the EEA or the UK, you also have the right to:
These rights have exceptions and limits under the law.
Because the Lumera Protocol is decentralized and public, we cannot change or delete information recorded on the blockchain or content stored on Cascade. Your rights apply to the Personal Information that we hold in our own systems.
Non-essential Cookies. We do not currently set any, so there is nothing to accept or reject. If we introduce them, we will provide a way to make that choice and to change it later.
Browser settings. Most browsers let you block or delete cookies and clear site storage. Doing so may affect how the Services work.
Do Not Track. There is no common standard for Do Not Track signals, so we do not currently respond to them.
The Services are not directed to anyone under 18, and we do not knowingly collect Personal Information from them. If you believe someone under 18 has given us Personal Information, contact legal@lumera.io and we will delete it.
Transfers. Your Personal Information may be transferred to, stored in and processed in the United States and other countries where we or our service providers operate. Where the law requires it, we use appropriate safeguards for these transfers, such as the European Commission’s standard contractual clauses.
Retention. We keep Personal Information only for as long as we need it for the purposes described in this Policy. When deciding how long that is, we consider the nature of the information, our relationship with you, any legal retention requirements and applicable limitation periods. When we no longer need the information, we delete it or de-identify it.
If you are a California resident, you may have the right to:
We do not sell Personal Information, and we do not share it for cross-context behavioral advertising.
California residents may also ask for information about our disclosures of Personal Information to third parties for their direct marketing purposes.
To make any request, email legal@lumera.io with “California Privacy Request” in the subject line. Include enough detail for us to find your information, such as your name and email address. We will verify your request before responding and will reply within the time the law requires.
We do not sell “covered information”, as that term is defined under Nevada law. Nevada residents may still send us a request not to sell their covered information by emailing legal@lumera.io with “Nevada Do Not Sell” in the subject line.
We may update this Policy from time to time. The effective date at the top shows when it last changed. If we make material changes, we will tell you through the Services or by other appropriate means. We encourage you to review this Policy regularly. By continuing to use the Services after an update takes effect, you acknowledge the revised Policy.
Unless this Policy says otherwise, Lumera Foundation is the controller of the Personal Information described here. For questions about this Policy or our privacy practices, contact:
Lumera Foundation
The Site and Services (defined below) are not offered to, and may not be used by, any person or entity that is a Prohibited Person. You are a Prohibited Person if you:
“Restricted Territories” means Cuba, Iran, North Korea, Syria, the Russian Federation, Belarus, and the Crimea, Donetsk and Luhansk regions of Ukraine, together with any other jurisdiction we designate from time to time.
“Sanctions Lists” means the sanctions lists maintained by the U.S. Office of Foreign Assets Control (including the Specially Designated Nationals and Blocked Persons List), the UK Office of Financial Sanctions Implementation, the European Union and the United Nations Security Council.
If you are a Prohibited Person, do not access or use the Services. Using a VPN or any other method to get around these restrictions is prohibited.
Welcome. These Terms of Use (these “Terms”) govern your access to and use of the Services provided by Lumera Foundation organized under the laws of the Cayman Islands, together with its officers, directors, employees, contractors, consultants, agents, attorneys, affiliates, predecessors and successors (collectively, “Lumera Foundation”, “we”, “us” or “our”).
The “Services” means:
Some Services may carry additional terms. If additional terms conflict with these Terms, the additional terms control for that Service.
Please read these Terms carefully. By accessing or using the Services, you confirm that you have read, understood and agree to be bound by them. If you do not agree, do not access or use the Services.
The Lumera Protocol (the “Protocol”) is open-source blockchain software. It is run by independent validators, SuperNode operators and other participants. The Services are interfaces and information that help you learn about, monitor and interact with the Protocol. They are not the Protocol itself. Specifically:
We don’t control the network. We do not operate, control or guarantee the Protocol, the Lumera network, or the validators and SuperNodes that run it.
We can’t undo transactions. We cannot reverse, cancel, modify or censor transactions or storage actions on the Protocol.
We can’t recover keys. We cannot recover lost keys, seed phrases or digital assets.
We don’t hold your assets. We do not take custody of your digital assets.
When you use the Protocol, you do so directly, through your own wallet and at your own risk.
We may change these Terms from time to time at our sole discretion. When we do, we will update the date at the top and keep the current version available on the Site. Changes take effect when posted. If you keep using the Services after that, you accept the changes. If you do not agree to a change, you must stop using the Services.
To use the Services, you must:
You agree that your use of the Services will comply with all applicable laws and regulations. You also agree that you will not use the Services to conduct, promote or facilitate any illegal activity. If you use the Services on behalf of an organization, you confirm that you are authorized to accept these Terms for it.
Our Privacy Policy, available at lumera.io/privacy, explains how we collect, use and share Personal Information. We use commercially reasonable safeguards, but we cannot guarantee that unauthorized parties will never access your information. You provide information at your own risk.
Transactions, wallet addresses, staking and governance activity, and Cascade storage records are recorded publicly on the Protocol. Anyone can view them, and they cannot be deleted. Please consider this before you transact or store anything.
The Services may let you connect a self-custodial wallet, such as Keplr, MetaMask or Lumera Hub. You are solely responsible for:
We will never ask for your seed phrase or private keys. Anyone who does is not acting for us. Please report impersonation or phishing to security@lumera.io.
Cascade is the Protocol’s storage service. If you use Cascade, whether directly or through the Services, you acknowledge and agree to the following:
Designed to be permanent. Stored content is split across independent SuperNodes and designed to be retained for the long term. Once stored, it generally cannot be modified or deleted by you, by us or by anyone else.
Public files are public. Files you store as public can be retrieved by anyone. Files you store as private are access-controlled, but they are still held by independent third parties. Encrypt anything sensitive on your own device before you upload it.
Your content, your responsibility. You are solely responsible for what you store and must have every right needed to store it. You must not store:
Fees. Storage fees are paid once, in LUME, at the time you store content. They are set by on-chain parameters that governance can change, and transaction gas is charged separately.
No guarantee. Descriptions of retention proofs, self-healing and the Everlight pool explain how the Protocol is designed. They are not a promise or warranty from us. We do not guarantee the availability, integrity, retrievability or duration of any stored content.
We may provide public endpoints, the SN-API gateway, LumeScope, the faucet, SDKs, sample code and documentation. These are provided “as is” and may be rate-limited, changed or discontinued at any time without notice. Do not treat them as guaranteed production infrastructure.
Testnet tokens have no monetary value.
Open-source software we publish is licensed under its own license, such as the Apache License 2.0. For that software, the license governs your rights, not these Terms.
You agree not to engage in, or attempt to engage in, any of the following in connection with the Services:
Intellectual property infringement. Violating any copyright, trademark, patent, publicity, privacy or other proprietary right.
Attacks and abuse. Interfering with or compromising the security or proper functioning of the Services or any network or device. This includes deploying malware, denial-of-service attacks, and scraping or overloading endpoints beyond published limits.
Gaming programs. Using bots, duplicate accounts or other means to manipulate faucets, quests, campaigns, reward programs or metrics.
Fraud and impersonation. Misleading anyone, impersonating Lumera Foundation or its team, or using our name or marks in phishing, scams or unauthorized token sales.
Unlawful content. Storing or distributing content prohibited by Section 7 or by law.
Evading restrictions. Circumventing the eligibility, sanctions or geographic restrictions in these Terms.
Any other unlawful conduct. Violating any law, rule or regulation that applies to you or to us.
Please read this Section carefully. It limits what you may rely on and the claims you may bring.
In this Section, “Foundation Parties” means:
LUME is the native utility token of the Lumera Protocol. It is designed to be used within the Protocol to:
The uses of LUME are defined by the Protocol’s open-source code. So are the rules that govern it, including issuance, inflation, fees, burns, staking rewards and supply. On-chain governance can change all of these, and the Foundation Parties do not control them.
LUME is not intended to constitute an investment contract, security, share, debt instrument or other financial instrument in any jurisdiction.
Holding LUME gives you no right against any Foundation Party or its assets. That includes no ownership, equity, debt, dividend, profit share, revenue share, redemption or voting right, other than voting in on-chain governance under the Protocol’s own rules. No Foundation Party has any obligation to buy back or redeem LUME, to support its price, or to make or maintain a market for it.
THE FOUNDATION PARTIES DO NOT PROVIDE, AND HAVE NOT PROVIDED, ANY GUIDANCE, FORECAST, PROJECTION, PREDICTION, ESTIMATE OR ASSURANCE OF ANY KIND REGARDING:
No Foundation Party promises, guarantees or undertakes that LUME will:
Whether and when LUME is listed depends on decisions of third parties, such as exchanges, regulators and market participants. It also depends on market, legal, regulatory and technical conditions outside our control. An exchange may decline, delay or reverse a listing at any time, for any reason.
A Foundation Party may mention a date, target, window, quarter, roadmap, schedule or other timeline for any of the following:
Wherever it appears, that timeline is only a non-binding estimate made in good faith at the time. This applies to roadmaps, technical papers, blog posts, announcements, presentations, AMAs, social media posts, Discord or Telegram messages, emails, calls and private conversations alike.
It may change without notice, be delayed indefinitely, or never happen. A change, delay or cancellation is not a breach of any obligation. No Foundation Party has any duty to update or correct an estimate once it is made.
The Services may display figures such as:
These figures come from on-chain data or third-party sources, may be delayed or inaccurate, and describe past or current conditions only. They are not a prediction or promise of future results.
No person is authorized to make any statement, promise or representation on behalf of any Foundation Party about the price, value, liquidity, returns, listing or listing timing of LUME.
Statements about these matters by anyone else are theirs alone and do not bind any Foundation Party. That includes community members, moderators, ambassadors, validators, partners, influencers, exchanges and market commentators.
If a Foundation Party, or anyone claiming to act for one, has made a statement that appears to conflict with this Section, this Section controls. The only exception is set out in Section 10.11.
You agree that you have not relied, and will not rely, on any statement, estimate, forecast or timeline described in this Section when you decide to:
You make these decisions independently, based on your own judgment and your own professional advice. You accept that you could lose some or all of the value of any LUME you hold.
TO THE FULLEST EXTENT PERMITTED BY LAW, YOU IRREVOCABLY WAIVE, RELEASE AND DISCHARGE ANY CLAIM, DEMAND, ACTION OR PROCEEDING AGAINST ANY FOUNDATION PARTY, AND AGREE NOT TO BRING ONE OR HELP ANYONE ELSE BRING ONE. THIS APPLIES WHETHER THE CLAIM IS IN CONTRACT, TORT (INCLUDING NEGLIGENCE AND NEGLIGENT MISREPRESENTATION), STATUTE, EQUITY OR OTHERWISE, IF IT ARISES FROM OR RELATES TO:
No Foundation Party will owe you any compensation, refund, rebate, bonus, extension, make-whole payment or other remedy for any of these matters. This Section applies in addition to Sections 13 to 20.
You are solely responsible for deciding whether acquiring, holding or using LUME is lawful where you are, and for any taxes that apply to you.
LUME may become subject to legislation, regulation or regulatory action in any jurisdiction, and that could affect whether it can be used, transferred or listed. The Foundation Parties may modify, suspend or discontinue any Service or program in response.
This Section 10.11 applies if you have a written agreement for the purchase, grant, delegation or lock-up of LUME that is signed by an authorized officer of Lumera Foundation:
What the agreement governs. Its express terms govern the matters it expressly covers.
Everything else. Everything else is subject to this Section, including any statement that is not written into that agreement.
No implied obligations. Unless the agreement expressly says so, it creates no obligation to list LUME, to list it by any date, or to achieve any price, liquidity or return.
Everything on the Services is for general information only. It is not investment, financial, legal, tax or other professional advice. Get independent advice before you make any decision involving the Services, the Protocol or LUME.
The Services describe capabilities, roadmaps and designs, some of which are planned or still in development, including in our technical papers. Statements about future plans, features, performance or network growth are forward-looking. They depend on risks and uncertainties, and they may change or never happen. Nothing on the Services is a commitment to deliver any feature by any date.
Some jurisdictions do not allow certain disclaimers, waivers or limitations. Where that is the case, this Section applies to the maximum extent the law permits. Nothing in this Section excludes or limits any liability that cannot lawfully be excluded or limited.
Staking, delegating, and operating a validator or SuperNode involve the Protocol’s rules and parameters. These include:
Governance can change these at any time.
Network upgrades may require you to act, for example to migrate an account within a set window. If you do not act in time, you may lose the ability to recover staked or delegated assets. You are responsible for following network announcements and the documentation.
We or third parties may run quests, learn-to-earn programs, competitions or other reward campaigns. Each is subject to its own published rules and eligibility criteria. We may disqualify participants, withhold rewards, or change or end a campaign if we suspect abuse, ineligibility or a violation of these Terms. You are responsible for any taxes on rewards you receive.
The Services are provided on an “as is” and “as available” basis. To the fullest extent permitted by law, we disclaim all representations and warranties of any kind, whether express, implied or statutory, including warranties of merchantability, fitness for a particular purpose, title and non-infringement.
We do not warrant that:
Nothing we say creates a warranty. We do not endorse or take responsibility for statements, offers or advertisements made by third parties about the Services.
These Terms do not create any fiduciary duty on our part. To the fullest extent permitted by law, you agree that we owe no fiduciary duties to you or anyone else. Any such duties that might exist at law or in equity are irrevocably disclaimed, waived and eliminated. Our only duties to you are those expressly set out in these Terms.
You represent that you understand the risks of using blockchain systems and digital assets and that you have a working knowledge of how they operate. These risks include:
We are not responsible for these risks. You assume full responsibility for all risks of using the Services and the Protocol.
The Services may link to or display third-party resources, including wallets, exchanges, bridges, explorers, node providers and partner projects, and third parties may offer promotions related to Lumera. We do not own or control these resources and do not endorse them. You use them at your own risk, and these Terms do not govern your dealings with third parties. You release us from all liability arising from your use of third-party resources.
The Services and their content are owned by us or our licensors and are protected by intellectual property laws. Examples include text, graphics, logos, papers and designs. Excluding open-source software, which is licensed under its own terms, we grant you a limited, revocable, non-exclusive, non-transferable license to access and view the Services for your personal or internal business use.
Use of the Lumera name, logos and other marks is governed by our brand terms at lumera.io/brand.
If you send us feedback or suggestions, we may use them without any obligation to you.
You assume all risks in connection with your use of the Services and your interactions with the Protocol. You waive and release us from all liability, claims, causes of action and damages arising from or relating to your use of the Services or your interactions with the Protocol through them.
You agree to defend, indemnify and hold harmless us and our officers, directors, employees, contractors, agents, affiliates and subsidiaries from all claims, damages, obligations, losses, liabilities, costs and expenses, including reasonable legal fees, arising from:
To the fullest extent permitted by law, we will not be liable to you for any indirect, incidental, special, consequential, exemplary or punitive damages. This includes loss of profits, digital assets, data, goodwill or use, arising out of or relating to the Services or the Protocol.
We are also not responsible for:
To the extent we are liable despite the above, our total liability for all claims will not exceed US$100.
These limits apply regardless of the theory of liability, whether contract, tort, negligence, strict liability or otherwise, and even if we have been told such damages are possible. Some jurisdictions do not allow certain exclusions or limitations, so some of these may not apply to you.
We may suspend or end your access to all or part of the Services at any time, with or without notice. Reasons include suspected violation of these Terms, security concerns or legal requirements.
Sections 5, 7, 10 and 13 through 25 survive any termination.
If a dispute, claim or controversy arises out of or relates to the Services or these Terms (a “Dispute”), including their interpretation, breach or enforcement, you and we will first try to resolve it through good-faith negotiation. The negotiation period begins when either party gives written notice.
If the Dispute is not resolved within 60 days of that notice, it will be resolved exclusively by the jurisdiction of the courts of the Cayman Islands. All disputes shall be resolved in accordance with the laws of the Cayman Islands and you and we waive any objection to that forum.
Notices to us under this section must be sent to legal@lumera.io.
You may bring Disputes against us only in your individual capacity. You may not bring them as a plaintiff or class member in any class, collective, consolidated or representative action or arbitration. You and we both waive any right to a jury trial. Either party may still bring an individual claim in small claims court where it qualifies.
These Terms, and any Dispute between you and us, are governed by the laws of the Cayman Islands, without regard to conflict-of-laws principles.
Entire agreement. These Terms, together with the Privacy Policy and any additional terms for a specific Service, are the entire agreement between you and us about the Services.
Severability. If any provision is found unenforceable, the rest of these Terms remain in effect.
No waiver. If we do not enforce a provision, that does not waive our right to enforce it later.
Assignment. You may not transfer your rights or obligations under these Terms without our consent. We may assign ours without restriction.
Headings. Headings are for convenience only.
Language. If we provide a translation, the English version controls.
Lumera Foundation