# Lumera Protocol — full site text > Generated from lumera.io. Every core page, in reading order. # Lumera — The Intelligence Layer > Source: https://lumera.io/ · Lumera Protocol Mainnet live ## Store. Verify. Build. The infrastructure layer for durable memory and decentralized intelligent services. [Start building →](https://docs.lumera.io/quickstart) [Run a node →](https://lumera.io/network) ### Building with [See every integration →](https://lumera.io/ecosystem) Cosmos [Cosmos SDK · IBC](https://lumera.io/ecosystem#eco-cosmos) FalconX Institutional validator Osmosis Cosmos chain · IBC Injective Cosmos chain · IBC Snag Ecosystem campaigns NTT DOCOMO GLOBAL Institutional validator Xangle Market data Midnight ZK Layer 1 Lagrange ZK proving network LUKSO EVM Layer 1 Talis Cosmos chain · IBC Luganodes Validator Nansen Validator Allnodes Validator Keplr Wallet support MetaMask EVM support Cosmos Cosmos SDK · IBC FalconX Institutional validator Osmosis Cosmos chain · IBC Injective Cosmos chain · IBC Snag Ecosystem campaigns NTT DOCOMO GLOBAL Institutional validator Xangle Market data Midnight ZK Layer 1 Lagrange ZK proving network LUKSO EVM Layer 1 Talis Cosmos chain · IBC Luganodes Validator Nansen Validator Allnodes Validator Keplr Wallet support MetaMask EVM support Lumera ### The foundation beneath intelligent systems. 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. One protocol architecture [Explore the architecture →](https://lumera.io/protocol) Durable Memory Live Permanent storage and state that survives sessions, applications and providers. Cascade Identity Cryptographic passports that enforce permissions and delegated authority. Lumera ID Verifiable Execution Actions that produce cryptographic receipts proving what work was performed. Proof of Service Settlement Protocol-native settlement, escrow and incentives for decentralized services. Global Credits Trust A record built from verifiable protocol activity rather than intermediaries or reputation alone. Trust graph Cascade ### Permanent data. Durable memory. Pay once. Store Forever. No recurring storage fees. Erasure coded. Efficient redundancy with self-healing mechanisms to ensure permanence and retrievability. Cryptographically verified. Continuous retention proofs, sampled every epoch. Economically secured. SuperNodes are bonded, and a missed challenge can trigger slashing. Portable. Independent of any individual model, provider, or application. Protocol native. Memory belongs to the identity that wrote it, not to the application or vendor it was written through. [Live from the explorer →](https://portal.lumera.io/lumera-mainnet-1) 1.60M Total transactions 36.4 TB Current storage utilized 98.72% Network uptime 168,519 Active wallets Lifecycle of a single file being stored One Upload, Stored Forever Application Reads it back A different application Reads it back A different model Application One file, uploaded once Independent SuperNodes Redundancy1.50× Threshold Permanent data A file enters once and the network keeps proving it is still there. Store a file Remember a fact Copy 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 }) The same primitive in two shapes: a file an application stores, or a fact an agent needs to still have next session. Live on mainnet Production SDKs TypeScript · Go · Rust Permanent storage available today [Explore Cascade →](https://lumera.io/memory) Designed to scale ### Consensus where it matters. Execution where it scales. 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. Control plane The chain ConsensusGovernancePaymentsProofs Latest block Request · escrow Client Your application Calls the SDK with an API key. Data path Never touches consensus Receipt · settlement Execution plane SuperNodes StorageVerificationExecutionProtocol services Memory plane Cascade, plus hot state Permanent dataDurable memory One requestA request enters at the application and leaves as a receipt. Replay Who runs what Validators secure the chain. SuperNodes do the work. Validators keep the official record and agree on what happened. SuperNodes store the files, prove on demand that they still have them, and check that work was done correctly. Two separate jobs, and neither can take over the other. What ties them together Capacity is backed by capital at risk. To run a SuperNode you have to lock up your own LUME first. Let that deposit drop too low and your SuperNode is taken offline. The network can never store more than its operators have money riding on. Build ### Three ways in. Launch your application, secure the network, store the data. Each one is open today. For developers Build an app Give your applications or agents durable memory and verifiable data in a few lines of code. Start with an API key and ship your first upload today. Quickstart→ For operators Run a SuperNode Store pieces of the network’s data, prove on demand that you still have them, and check other nodes’ work. You get LUME for your SuperNode’s work. Operator guide→ For validators Run a validator Keep the network in agreement, secure it, and process every transaction that runs through it. Fifty active slots, earning rewards for the operator and everyone who stakes with them. Validator guide→ Community ### Where the network talks. Discord Builder support and protocol discussion. X Releases, upgrades and announcements. YouTube Upgrade walkthroughs and explainers. Telegram Day to day community chat. Blog Deep dives and release notes. ### Ship today. Prove it forever. [Start building →](https://docs.lumera.io/quickstart) [Explore the network →](https://portal.lumera.io/lumera-mainnet-1) --- # Protocol Overview > Source: https://lumera.io/protocol · Lumera Protocol ## One Architecture. Limitless Capabilities The infrastructure layer for durable memory and decentralized intelligent services. The Stack ### Lumera Intelligence Layer 01 Lumera ID Identity An identity the agent owns, not an API key on someone else’s account. Today 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. On Lumera 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. ProfileKeyRotationDelegationCapabilityGrantAppIdentityAssetIdentityAttestation Delegation chains are the enterprise wedge. Grant an agent a budget class or a dataset. Scoped, time-bound, revocable, enforced on-chain. 02 Proof of Service Verifiable Execution Proof of what ran, what it cost, and that you accepted it. Today 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. On Lumera Global Credits Fund once. Provider-agnostic. Per-Turn Acknowledgment Only accepted turns are billable. Transcript Fingerprints Verifiable in dispute, never in plaintext. 03 Cascade Durable Memory Memory that survives switching providers. Today Agent state lives in provider-controlled databases. Switch providers, lose context. No memory the agent owns, no institutional knowledge that accumulates, no data sovereignty. On Lumera 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. ONE / QUORUMVector clocksHinted handoffAnti-entropy repairSigned write receipts 04 LUME · Everlight Settlement Someone has to pay for permanence, not just usage. Today Payment rails assume a human at the end. An agent cannot hold a balance, earn revenue, or settle a transaction on its own behalf. On Lumera 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. 05 Trust Graph Trust A record of who actually delivered, earned rather than claimed. Today 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. On Lumera 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. WhoWhatVerdictPriceTime 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. What happens when it goes wrong ### When an agent is wrong, the damage is contained. Three classes of execution, three consequences when something goes wrong. They never collapse into each other. Reasoning Example A model analyzes a contract Check No replay is possible, so output is advisory Consequence Reputation only Quality moves the trust graph. Nothing is slashed. Deterministic compute Example A pack transforms data Check A second node replays it Consequence Slashable If runner and verifier disagree, that is objective evidence. No judgement needed. Effects Example A transaction is proposed Check Returned as a signed plan Consequence App validates The protocol never fires an irreversible action on its own. The Foundation ### Memory at the base. Everything else stands on it. 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. What it serves Applications and agents Your framework, your models, your product. ↑Serves↑ Identity Built on memory Verifiable Execution Built on memory Settlement Built on memory Trust Built on memory ↑Built on↑ The foundation Live Durable Memory Permanent, provable storage. Everything above it needs a record that outlives the session that made it. Memory→ ↑Runs on↑ Execution plane SuperNodes StorageVerificationComputeProtocol services Memory plane Cascade, plus hot state Permanent dataDurable memory Control plane The chain ConsensusGovernancePaymentsProofs One foundation carries all of it, which is why a new capability does not mean a new network.Data never passes through consensus Start at the foundation Live Durable Memory None of this holds without a record that is still there when someone checks. Permanent, provable storage is live on mainnet, and it is where the rest of the architecture starts. Memory ### Ship today. Prove it forever. [Start building →](https://lumera.io/build) --- # Durable Memory > Source: https://lumera.io/memory · Lumera Protocol Durable Memory Cascade ## A memory you can prove. 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 →](https://lumera.io/technicalpaper#paper-cascade) ### Pay once. Prove it forever. Take it anywhere. 01 Store once Pay once and the fact is kept. There is no renewal to forget and no bill that grows with age. 02 Prove it The network keeps re-proving that the data is still held, continuously, and anyone can check the result. 03 Take it anywhere 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. Retention ### Storage nobody has to take on trust. 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. Challenge The network selects a node and byte range Each epoch, the protocol challenges nodes to return a specific slice of data, making it impractical to precompute a response. Response The node returns the slice and its Merkle proof The proof traces a hash path from the requested data to the root under which the file was committed, verifying that the node still holds it. Verdict The result is recorded onchain A successful response keeps the node earning. A missed challenge can trigger slashing, and the missing fragment is rebuilt elsewhere. One challenge, every epoch, for the life of the file. ### Three calls, start to finish store · recall · prove Copy 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) Works withMCPLangChainCrewAIHTTP API [See every adapter →](https://docs.lumera.io/) ### Questions we get asked Is this a replacement for Pinecone or S3? 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. Do I need a wallet? 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. What happens if we stop paying? 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. Will it work with the framework I already use? 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. Can I delete something once it is written? 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. Built on memory Identity A record that outlives the session is what makes an identity worth owning. Next, that memory attaches to a passport the agent holds rather than an account it rents. Lumera ID Live on mainnet today Give it a memory today. Three calls and an API key. The network keeps the data and keeps proving it is still there. [Read the docs →](https://docs.lumera.io/intelligence-layer/durable-memory) [Open the app](https://hub.lumera.io/) --- # Identity > Source: https://lumera.io/identity · Lumera Protocol Identity Lumera ID ## An identity you own, not a key a vendor issued. 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. [Explore the architecture →](https://lumera.io/protocol) How it works today An agent’s identity is often little more than an API key. Whoever holds the key can act as the agent, with no reliable way to prove which agent performed a specific action. Delegation means sharing the same secret, and revoking it ends access without preserving a durable identity. How it works on Lumera The agent holds a persistent identity that exists independently of any application. Permissions are explicit and can be delegated for a limited purpose without sharing secrets. Every action remains attributable because the identity outlives the application, model and session behind it. What this is not Not a login for your users This is not a sign-in provider and it does not replace how people log into your product. It is the identity the work is signed with, underneath whatever you already use. Anatomy of an identity ### More than a name. A record with a history. 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 key Controlled by the identity owner, never the protocol. Without it, no one can act as that identity. Permissions An explicit record of what the identity is authorized to do. Delegations Limited authority granted to another party, with a defined scope and expiration. History A durable record of every action the identity has signed, readable long after the session ends. Anchor Permanently recorded, so revoking access never erases the past. Handing over authority Without sharing a secret You Control the identity and define what it may do. Your application or agent Receives limited authority for a specific task, budget and period. Another agent Can receive a narrower delegation, but never more authority than the agent granting it. Revoking access Withdraw a delegation and every permission beneath it ends too. No keys need to be rotated because no secret was shared. Keeping the history Revocation prevents future actions without erasing the past. Everything already done remains attributable. ### What a real identity makes possible. 01 Delegated authority Grant a limited permission to another agent, for a set scope, without handing over credentials. 02 Attribution Work is signed, so who did what stays answerable long after the job finished. 03 Portability The same identity works across applications and models, because it does not belong to any of them. A record worth having History creates trust only when it is tied to a persistent identity, one that cannot be discarded and recreated without consequence. That continuity makes identity the foundation of the trust graph. Next in the stack Verifiable Execution An identity worth trusting needs work that can be checked against it. Next, every job leaves evidence of what actually ran. Proof of Service Read the full specification. The developer documentation carries the detail this page leaves out: the interfaces, the guarantees, and how it fits with everything else. [Read the docs →](https://docs.lumera.io/intelligence-layer/identity) --- # Verifiable Execution > Source: https://lumera.io/execution · Lumera Protocol Verifiable Execution Proof of Service ## Answers you can verify, not answers you have to trust. Every action produces a cryptographic receipt showing what was done, so anyone can independently verify the result rather than take it on faith. [Explore the architecture →](https://lumera.io/protocol) How it works today A model returns an answer and that is the end of it. There is no record of what ran, on what input, at what cost, and no way for a second party to reproduce it. When the answer matters, the only recourse is to trust the vendor that produced it. How it works on Lumera Every action produces a signed receipt recording what was run and what it returned. Another node can re-run the work using the same inputs, making disagreements detectable instead of subjective. Payment can then be tied to verified work. Anatomy of a receipt ### Enough to verify it, without trusting anyone. 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. Inputs A fingerprint of the exact inputs, so the original request cannot be quietly changed. Method Which operator ran the work and what it ran. Output A fingerprint of the result, so any difference is immediately detectable. Signature Signed by the identity that performed the work, making the result attributable. Anchor Permanently recorded so the receipt cannot be altered and can always be retrieved. How a result gets checked Nobody has to be believed Work runs An operator does the job and signs a receipt for it. Someone else re-runs it A second operator takes the same inputs and does it independently. The two are compared Agreement settles it. Disagreement is visible, not arguable. They match The receipt stands, payment releases, and the job becomes a line in the operator’s record. They differ Payment stays escrowed and the operator that signed a result it could not defend forfeits part of its bonded stake. ### What becomes possible when work is checkable. 01 Re-derivation A second operator can reproduce the result independently and compare. 02 Dispute resolution Disagreement resolves against evidence rather than against whoever is larger. 03 Payment on delivery Money can be released against verified work instead of on a promise. What this is not Not a judgement on the answer The protocol does not decide whether a result is good. It establishes what was run and what came back, so a disagreement has evidence behind it. Quality stays a question for whoever asked. What it is for Work that has to answer for itself An agent spending money, taking a position, or making a call somebody may query months later. The receipt is what turns that from a claim into a record. [How records accumulate →](https://lumera.io/trust) Next in the stack Settlement Once work can be checked, payment can wait for the check. Next, money that only moves when the job is verified. Global Credits Read the full specification. The developer documentation carries the detail this page leaves out: the interfaces, the guarantees, and how it fits with everything else. [Read the docs →](https://docs.lumera.io/intelligence-layer/verifiable-execution) --- # Settlement > Source: https://lumera.io/settlement · Lumera Protocol Settlement Global Credits ## Payment that waits for proof. Protocol-native settlement, escrow and incentives for decentralized services. Applications and agents can hold budgets, pay providers and earn payment for completed work. [Explore the architecture →](https://lumera.io/protocol) How it works today Payment systems are built around people, cards and company accounts. Agents can transact only through credentials and controls created for human users. Automated work still depends largely on invoices, payment terms and trust between companies. How it works on Lumera Funds are locked in escrow when a job is accepted and released only after the work is verified. The provider gets paid, the customer can see exactly what was delivered, and the protocol enforces settlement for both sides. Anatomy of a payment ### Payment moves when the work is verified. 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. Requested The job, its price and what counts as complete are defined. Escrowed The agreed amount is locked onchain when the job is accepted. Verified A second operator confirms the work before funds are released. Released Payment goes directly to the identity that completed the work. Recorded Both sides can see what was paid, for what and when. Escrow, end to end Neither side holds the other’s money Accepted Funds leave the buyer and are locked by the protocol. Held Nobody can spend them while the work is being checked. Released Verification passes and the operator is paid. If verification fails The escrow does not release. The operator forfeits part of the stake it bonded against the job, so failing costs money rather than reputation. If the operator disappears The job is reassigned and the funds stay locked until someone completes it. The buyer’s money was never in the operator’s hands. ### What settlement unlocks. 01 Programmable budgets An account can be given money to spend within limits it cannot exceed. 02 Agent to agent One agent hires another and pays it directly, without a human closing the loop. 03 Escrow by default Payment is held until the work is verified, so neither party carries the other’s risk. For the people building No wallet in your product Your users do not need a wallet, a seed phrase, or a token balance. Settlement happens underneath, and you bill however you already bill. This is how Cascade storage settles today: the fee is escrowed when the write is registered and released when the upload is verified and finalized. Where the token sits Underneath, not in front LUME is what the escrow holds and what operators bond, which is why a failed job can cost the operator something real. It is protocol plumbing rather than a step in anyone’s checkout. [See the economics →](https://lumera.io/economics) Next in the stack Trust Paid, verified jobs are the raw material of a reputation. Next, a record of who actually delivered. Trust graph Read the full specification. The developer documentation carries the detail this page leaves out: the interfaces, the guarantees, and how it fits with everything else. [Read the docs →](https://docs.lumera.io/intelligence-layer/economic-coordination) --- # Trust > Source: https://lumera.io/trust · Lumera Protocol Trust Trust graph ## A record of who actually delivered. Trust built from verifiable protocol activity rather than from intermediaries or reputation alone, accumulated one paid job at a time. [Explore the architecture →](https://docs.lumera.io/intelligence-layer/trust) How it works today 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. How it works on Lumera 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. Anatomy of an edge ### Every connection in the graph represents a completed job. 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. Who The identity that performed the work and the identity that paid for it. What The work that was requested and the result that was returned. Verdict Whether another operator independently verified the result. Price The amount placed in escrow and the amount released. When The block in which the payment settled, giving the record a fixed place in time. Why trust adds up ### Trust compounds with every verified job. 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. A companyHires agents A research agentDoes the work A compute providerRuns the jobs A risk-scoring workflowA reusable recipe A market data feedSource data A research agent illustrative Research and analysis 0.92 Financial decisions 0.18 Finding data 0.81 1,284 paid jobs · 3 disputes · 40,000 LUME staked To fake this you would need to pay for 1,284 real jobs and stake 40,000 LUME — and still pass someone else’s verification. Trusted for research. Untested in finance. One universal score cannot tell you the difference. Earned, not copied Every edge represents a verified, paid job. Copying the data does not transfer the history to another identity. Backed by stake Building a false record requires bonding real LUME against work that can be independently checked. Failed verification can put that stake at risk. Sharper with use More jobs improve routing. Better routing attracts better work. Each strengthens the other. ### Why a record beats a rating. 01 Earned, not bought Each edge in the graph represents a job that was completed, verified and paid for. Any identity can also bond LUME against its work. A failed job puts both its stake and its standing at risk. 02 Attached to identity The record follows the identity across applications and vendors. Starting again means starting without the history that earned trust. 03 Readable by anyone Applications and agents can make routing decisions using a verifiable record instead of an opaque score or vendor list. What it is used for Choosing who does the work When an agent selects an operator or a platform routes a job, it can consult the record directly instead of relying on a vendor list. Every completed job improves the signal, helping better work find the right provider. The other graph The intelligence graph The trust graph records who delivered. The intelligence graph records what was learned: what was asked, what was found and how the findings connect. Both are built on the same permanent foundation. [See both in the architecture →](https://lumera.io/protocol) Where it all goes The whole picture Memory, identity, evidence, settlement and reputation on one architecture. See what that makes possible. Vision Read the full specification. The developer documentation carries the detail this page leaves out: the interfaces, the guarantees, and how it fits with everything else. [Read the docs →](https://docs.lumera.io/intelligence-layer/trust) --- # Network > Source: https://lumera.io/network · Lumera Protocol Network ## Two roles power the network. Validators secure the chain. SuperNodes deliver its services. Consensus layer Validators 50 in the active set Their job is running the blockchain. Fixed set, elected by stake Responsible for Block production and finality Transaction ordering and inclusion Chain security through staked LUME Governance execution Service layer SuperNodes 28 running today They perform the network’s services. The chain records the commitments, proofs and results. Permissionless, bonded Responsible for Cascade storage, serving and repairToday Agent sessions and inferencePlanned Deterministic pack execution and verificationPlanned Trust graph indexing and queriesPlanned Both slashable Same stake at risk, different failure. A validator is slashed for Consensus faults, such as double signing or going dark. A SuperNode is slashed for Service faults, such as a deterministic mismatch or a forged receipt. Designed to scale ### Consensus where it matters. Execution where it scales. 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. Control plane The chain ConsensusGovernancePaymentsProofs Latest block Request · escrow Client Your application Calls the SDK with an API key. Data path Never touches consensus Receipt · settlement Execution plane SuperNodes StorageVerificationExecutionProtocol services Memory plane Cascade, plus hot state Permanent dataDurable memory One requestA request enters at the application and leaves as a receipt. Replay Who runs what Validators secure the chain. SuperNodes do the work. Validators keep the official record and agree on what happened. SuperNodes store the files, prove on demand that they still have them, and check that work was done correctly. Two separate jobs, and neither can take over the other. What ties them together Capacity is backed by capital at risk. To run a SuperNode you have to lock up your own LUME first. Let that deposit drop too low and your SuperNode is taken offline. The network can never store more than its operators have money riding on. How work becomes a record ### Who does the work, and who records what happened. 01 SuperNodes do the work Open set · 28 running Storage Keeps files safe Sessions Runs the agent Memory Holds live state Compute Runs and checks work 02 Each step emits a receipt Signed by the SuperNode that did the work Signed receipt ↓ 03 Validators order and finalize Fixed set · 50 validators They agree what happened and in what order. 04 It becomes the permanent record One block every 5.7s Newest block#6,490,707 The record outlives the app that wrote it. ### Network at a glance. [Live from the explorer →](https://portal.lumera.io/lumera-mainnet-1) Total transactions 1,597,900 Since genesis Active SuperNodes 28 Across 6 countries Network uptime 100.00% Rolling 90 days Cascade 36.4 TB used of 49.3 TB total capacity 73.9% used 231,799 files stored, with storage proofs running continuously Chain Block height 6,490,707 Block time 5.7s Active validators 50 Fixed active set Token Total supply 324.2M Circulating 322.5M Bonded 52.4% Staking APR 37.4% Economics Everlight pool 1.7M Funds retention Uptime · 90d 100.00% Everlight ### Permanence, paid for up front. 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. Where the money comes from A share of network rewards, a share of every fee, and returns on the fund itself. How operators get paid On a steady schedule, for as long as they keep holding the data. Paid to stay ready Operators earn for the space they keep available, not only for the work that comes in. Built to last Coming next: a fund large enough that its returns alone cover storage, without ever spending the fund. ### Run a SuperNode. Bond LUME, serve the network, and take the full service fee on every verified job. [Operator guide →](https://docs.lumera.io/supernodes/overview) --- # Economics > Source: https://lumera.io/economics · Lumera Protocol Economics ## The Network Pays for Itself. 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. Block rewards 98/ 2 98 percent to validators and their delegators for producing blocks, 2 percent to the community pool. Transaction fees 80 /20 20 percent is burned, so scarcity tracks usage rather than a fixed emission schedule. Service fees 100 Paid in full to the SuperNode operators who did the work. Escrowed on chain until the work is verified. The loop Usage funds capacity, capacity carries usage 20% burnedscarcity tracks usage Usage01 Applications store data and settle work. 0.02 LUME / MB Fees02 Paid in LUME on every action. 80 / 20 split Capacity03 Operators earn, bond more, and hold more. 100% to operators More capacity carries more usage What it costs Roughly 0.02 LUME per MB, paid once. No monthly bill, no egress charge, no renewal. Priced against the alternatives Dynamic adjustment keeps storage competitive with centralized providers even as LUME appreciates. Everlight Keeps paying operators to hold data after the write is paid for, so permanence is an economic property rather than a company promise. In full detail Every fee, split and reward, specified. [Understand Lumera’s Economics →](https://docs.lumera.io/protocol-revenue) [What LUME is for](https://docs.lumera.io/token) --- # LUME > Source: https://lumera.io/token · Lumera Protocol LUME ## One token, four structural jobs. 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. Paying for the work Every job 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. Money on the line Lost if they cheat 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. A track record worth keeping Earned, not claimed 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. Deciding what changes Holders vote 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. Value accrual ### Every job makes the next one easier to trust. LUME Settles it all 01 02 03 04 05 01 More data stored and verified → more LUME settlement volume. 02 More settlement → more staking demand for bonds and stakes. 03 More trust data → a richer graph and better routing. 04 Better routing → higher-value workloads. 05 Premium settlement → deeper economic security. Each turn of the wheel makes the next one cheaper to win. [Read the papers →](https://lumera.io/technicalpaper) [See the economics →](https://docs.lumera.io/protocol-revenue) --- # Build on Lumera > Source: https://lumera.io/build · Lumera Protocol Build ## Everything you need to build on Lumera. Durable memory, identity, verifiable execution and settlement behind one SDK and one economic model. Build against stable interfaces. [Read the docs →](https://docs.lumera.io/) [Source Code](https://github.com/LumeraProtocol/) ### How settlement works 01 Fund 02 Delegate 03 Invoke 04 Acknowledge 05 Settle Balance 0 credits Escrowed 0 credits Settled 0 credits Fund a Global Credits balance once, on-chain. Provider-agnostic from the start. credit values are illustrative Developer documentation Network setup, node operation, and protocol interfaces. Mainnet explorer Watch identities, receipts and settlements as they land. Source code The protocol is open. Read it, run it, contribute. Talk to the team Bring us what you are building and we will help you ship it. --- # Technical Papers > Source: https://lumera.io/technicalpaper · Lumera Protocol Technical Papers ## Dive Deep into the Inner Workings of Lumera The architecture, specifications, and design decisions behind the protocol. The papers 01 Architecture Intelligence Layer Paper Architecture and thesis 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. ArchitectureAgentsVerifiability [Read the paper →](https://lumera.io/technicalpaper/read?paper=intelligence-layer) 02 Economics Tokenomics Paper LUME and network economics 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. SupplyStakingFee flows [Read the paper →](https://lumera.io/technicalpaper/read?paper=tokenomics) Documentation Start building instead. SDK reference and working examples for building on Lumera today. [Go to docs →](https://docs.lumera.io/) Source Read the implementation. Lumera is open source. Every component is readable, and running on mainnet. [GitHub →](https://github.com/LumeraProtocol/) --- # Ecosystem > Source: https://lumera.io/ecosystem · Lumera Protocol Ecosystem ## Who Lumera connects to, and how. Foundation [Cosmos](https://cosmos.network) [Cosmos](https://cosmos.network)Cosmos SDK · IBC Lumera is a Cosmos SDK chain. IBC is native, so assets and messages move to any connected zone without a bridge contract. Connected chains [Osmosis](https://osmosis.zone) [Osmosis](https://osmosis.zone)Cosmos chain · IBC The DeFi hub of the Cosmos ecosystem. The connection lets LUME holders take part in DeFi without leaving the interchain. IBC-connected. [Injective](https://injective.com) [Injective](https://injective.com)Cosmos chain · IBC A finance-focused chain that needs durable memory for DeFi data, so its users can build trading strategies on a record that is still there later. IBC-connected. [Ethereum](https://ethereum.org) [Ethereum](https://ethereum.org)EVM Layer 1 EVM compatibility opens Lumera to the wider Ethereum ecosystem and the applications already built there. EVM-compatible on testnet while mainnet upgrade is coming soon. Building on Lumera [Talis](https://talis.art) [Talis](https://talis.art)Cosmos chain · IBC Building on Cascade. Talis stores the documentation behind its real-world asset tokens on Lumera, so provenance stays retrievable and provable long after issuance. IBC-connected. [Midnight](https://midnight.network) [Midnight](https://midnight.network)ZK Layer 1 A privacy-first Layer 1 built for confidential ownership, private metadata and selective disclosure. Its applications still need somewhere durable to keep the data behind them, and use Lumera to store it without exposing ownership. [Lagrange](https://lagrange.dev) [Lagrange](https://lagrange.dev)ZK proving network Building on Cascade. Lagrange’s decentralized prover network needs durable storage for the data behind its proofs, and uses Lumera to keep it retrievable at scale. [LUKSO](https://lukso.network) [LUKSO](https://lukso.network)EVM chain A chain built for digital identity and creative work, using Lumera to store the assets behind it. Wallets [Keplr](https://www.keplr.app) [Keplr](https://www.keplr.app)Wallet support Keplr users can hold and stake LUME with the wallet they already have. No new key material, no separate extension. [MetaMask](https://metamask.io) [MetaMask](https://metamask.io)EVM support · testnet Leading self-custodial crypto wallet, trusted by millions. LUME works with it directly through Lumera’s EVM support — live on testnet, with the mainnet upgrade coming soon. Operators [NTT DOCOMO GLOBAL](https://www.nttdigital.io) [NTT DOCOMO GLOBAL](https://www.nttdigital.io)Institutional validator An NTT subsidiary running a validator on Lumera mainnet. Institutional operators are what make an active set worth trusting. [FalconX](https://falconx.io) [FalconX](https://falconx.io)Institutional validator A digital asset prime broker providing deep liquidity, financing, and advanced technology to the world’s top institutions, now running a validator on Lumera mainnet. [Innovating Capital](https://innovatingcapital.com) [Innovating Capital](https://innovatingcapital.com)Institutional validator A technology fund running a validator on Lumera mainnet. [Luganodes](https://www.luganodes.com)Validator Swiss-based institutional-grade staking provider and global leader in staking volume, supporting 50+ PoS networks with $3bn+ under management, now running a validator on Lumera mainnet. [Allnodes](https://www.allnodes.com)Validator Top-ranked non-custodial node hosting and staking platform with a AAA rating on Staking Rewards, now running a validator on Lumera mainnet. [1XP](https://1xp.com)Validator Seoul-based validator operator, ISO 27001 certified, building the public intelligence tools that operators and governance teams rely on, now running a validator on Lumera mainnet. Show all ↓ Data and coverage [Xangle](https://xangle.io) [Xangle](https://xangle.io)Market data Korea’s primary crypto data and disclosure platform. Lumera is listed and covered there. [Nansen](https://nansen.ai/) [Nansen](https://nansen.ai/)On-chain analytics Lumera is covered on Nansen, so wallet and network activity can be tracked alongside the rest of the market. Community [Snag](https://www.snagsolutions.io) [Snag](https://www.snagsolutions.io)Ecosystem campaigns Campaign infrastructure used to reach and reward the people who show up early. --- # Vision > Source: https://lumera.io/vision · Lumera Protocol Vision ## An economy where software can be trusted with real work. 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. ### What this makes possible. Memory is live on mainnet today. The other four are being built on it. 01 [Durable memory→](https://lumera.io/memory) Cascade 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. 02 [An identity it owns→](https://lumera.io/identity) Lumera ID 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. 03 [Work you can check→](https://lumera.io/execution) Proof of Service 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. 04 [Money that moves itself→](https://lumera.io/settlement) Global Credits 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. 05 [Reputation that is earned→](https://lumera.io/trust) Trust graph 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. Where this ends up ### An agent that goes to work without you. 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. Identity Owned, not issued Budget Set by you, spent by it Receipts Every step, checkable Reputation Earned, not claimed [Start building →](https://docs.lumera.io/quickstart) [Read the papers](https://lumera.io/technicalpaper) --- # Blog > Source: https://lumera.io/blog · Lumera Protocol Blog ## What we shipped, and why. All Releases Guides Updates Ecosystem [Follow on X →](https://x.com/lumera) [RSS](https://lumera.io/blog/feed.xml) [See all posts →](https://lumera.io/blog/all) LatestEcosystem · September 21, 2026 · 2 min ### NTT DOCOMO GLOBAL Joins Lumera as a Validator 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… Read the post → Ecosystem September 18, 2026 2 min read Lumera Welcomes 1XP as a Validator Lumera has added 1XP as a validator on the network. 1XP operates validator infrastructure across multiple ecosystems, builds public intelligence tools used by operators… Ecosystem September 16, 2026 3 min read Lumera x Lagrange: Permanence for Verifiable AI 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… Ecosystem September 10, 2026 2 min read FalconX Joins Lumera as a Validator 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… --- # Brand > Source: https://lumera.io/brand · Lumera Protocol Brand ## Brand assets. 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. Logos SVG for screen and print. PNG where SVG will not go. Lumera wordmark, light Wordmark — light The default. Use on Navy and on any dark surface. [SVG](https://lumera.io/assets/lumera-logo-white.svg) [PNG](https://drive.google.com/drive/folders/1H0FnT2rNSHjjiH13PKv4WAfv-Jd_J0fF?usp=drive_link) Lumera wordmark, dark Wordmark — dark For light backgrounds, documents and print. [SVG](https://drive.google.com/drive/folders/1H0FnT2rNSHjjiH13PKv4WAfv-Jd_J0fF?usp=drive_link) [PNG](https://drive.google.com/drive/folders/1H0FnT2rNSHjjiH13PKv4WAfv-Jd_J0fF?usp=drive_link) Lumera symbol Symbol Square contexts only: avatars, favicons, app icons. [SVG](https://drive.google.com/drive/folders/1H0FnT2rNSHjjiH13PKv4WAfv-Jd_J0fF?usp=drive_link) [PNG](https://drive.google.com/drive/folders/1H0FnT2rNSHjjiH13PKv4WAfv-Jd_J0fF?usp=drive_link) [Download the full kit →](https://lumera.io/assets/lumera-brand-kit.zip) Construction Clear space Keep space equal to the height of the L on all four sides. Nothing enters it, including other logos, type and page edges. Minimum size Below this the letterforms break down. Wordmark: 96px on screen, 25mm in print. Symbol: 24px. 96px 24px Color Click any swatch to copy its hex. Copy Green #47C78A Primary accent. Fills, CTAs, active state. Copy Teal #078A8A Secondary accent, and the accent on light surfaces. Copy Navy #001432 Primary canvas. The default background. Copy Black #000000 Deepest surface. Full-bleed sections. Copy Gray #F5F5FA Light canvas, and primary text on dark. Green is a fill color. As small text on a light background it does not carry enough contrast, so use Teal there instead. Typeface Geist Everything else The intelligence layer [Get it →](https://fonts.google.com/specimen/Geist) Geist Mono Technical labels Proof of service [Get it →](https://fonts.google.com/specimen/Geist+Mono) Using the marks ### Good faith, plainly stated. 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. Go ahead - +Writing about, reporting on or reviewing Lumera - +Linking to lumera.io or the documentation - +Saying “built on Lumera” or “supports Lumera” where that is true - +Talks, tutorials, community content and educational material - +Showing the mark alongside others in an ecosystem or partner list Do not - –Suggest a partnership, endorsement or affiliation that does not exist - –Attach the marks to fraud, phishing, impersonation or an unauthorized token sale - –Present a fork, clone or unrelated product as Lumera - –Recolor, stretch, rotate, outline or otherwise alter the artwork - –Put the marks in your company name, product name, domain or app listing Terms 01 Use them in good faith 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. 02 No implied endorsement 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. 03 Nothing harmful or deceptive 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. 04 Do not modify the artwork Use the files as supplied. No recoloring, distortion, rotation, effects, or combining the marks with other logos, words or shapes to form something new. 05 Not part of your own identity The marks stay ours. Do not register them, or anything confusingly similar, as a trademark, company name, domain, social handle or app-store listing. 06 Permission can be withdrawn 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. Not sure Ask first. If your use is not clearly covered above, send us what you have in mind. It is a short conversation. [brand@lumera.io →](mailto:brand@lumera.io) --- # Privacy Policy > Source: https://lumera.io/privacy · Lumera Protocol Legal ## Privacy Policy. Last updated September 23, 2026 Public blockchain data 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: - Wallet addresses and balances - Transactions and staking activity - Governance votes - Cascade storage records, such as file hashes, sizes and metadata - Any file uploaded to Cascade as public 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. ### 1. Personal Information We Collect “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. #### A. Information you provide 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. #### B. Information we collect automatically 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. #### C. Information from third parties 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. ### 2. How We Use Personal Information #### A. Purposes 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. #### B. Legal bases (EEA and UK) 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. #### C. Cookies and similar technologies 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. ### 3. How We Share Personal Information 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: - Comply with law or legal process, including in other countries - Respond to lawful requests from public authorities - Enforce our terms - Protect the safety, rights or property of us, our users or others - Detect or prevent fraud and security issues 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. ### 4. Third-Party Services 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. ### 5. Security 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](mailto:security@lumera.io). ### 6. Your Rights and Choices 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. #### A. Your EEA and UK rights If you are in the EEA or the UK, you also have the right to: - Access your Personal Information and receive information about how we use it - Correct inaccurate information - Have your information deleted or anonymized - Restrict or object to our processing - Receive your information in a portable format - Withdraw consent at any time, free of charge, without affecting processing that happened before you withdrew - Lodge a complaint with a supervisory authority where you live or work, or where an issue occurred These rights have exceptions and limits under the law. #### B. Limits for blockchain data 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. #### C. Cookie choices 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. ### 7. Children 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](mailto:legal@lumera.io) and we will delete it. ### 8. International Transfers and Retention 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. ### 9. California Privacy Rights If you are a California resident, you may have the right to: - Know what Personal Information we collect, use and disclose - Request access to or deletion of your Personal Information - Correct inaccurate Personal Information - Not be discriminated against for exercising these rights 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](mailto: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. ### 10. Nevada Privacy Rights 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](mailto:legal@lumera.io) with “Nevada Do Not Sell” in the subject line. ### 11. Changes to This Policy 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. ### 12. Contact Us 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 [legal@lumera.io](mailto:legal@lumera.io) --- # Terms of Use > Source: https://lumera.io/terms-of-use · Lumera Protocol Legal ## Terms of Use. Last updated September 23, 2026 IMPORTANT NOTICE: PROHIBITED PERSONS 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: - Reside in, are a citizen of, are located in, are incorporated in, or have a registered office in the United Kingdom (each, a “UK Person”), Canada (each, a “Canadian Person”), or any Restricted Territory; - Are named on a Sanctions List, or act on behalf of, or intend to transact with, anyone named on a Sanctions List. “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: - The website at lumera.io, including the blog, technical papers and brand pages (the “Site”); - The developer documentation at docs.lumera.io; - The Lumera Portal (explorer and faucet), Lumera Hub and LumeScope; - Any public RPC, REST/LCD, gRPC, EVM JSON-RPC or SN-API endpoints we operate; and - Any other website, application or interface we operate that links to these Terms. 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. ### 1. The Lumera Protocol is not 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. ### 2. Changes to These Terms 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. ### 3. Eligibility To use the Services, you must: - Be at least 18 years old and able to form a binding contract; - Not be a Prohibited Person; and - Not be barred from using the Services under any applicable law. 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. ### 4. Privacy Our Privacy Policy, available at [lumera.io/privacy](https://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. ### 5. Public Nature of Blockchain Activity 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. ### 6. Your Wallet and Keys The Services may let you connect a self-custodial wallet, such as Keplr, MetaMask or Lumera Hub. You are solely responsible for: - Your wallet, devices, keys and seed phrase; - Every transaction you sign; and - Checking addresses, amounts and network details before you sign. 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](mailto:security@lumera.io). ### 7. Storing Data with Cascade 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: - Personal Information about others without a lawful basis; - Unlawful content; - Child sexual abuse material; - Malware; or - Material that infringes anyone’s rights. 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. ### 8. Network Endpoints and Developer Tools 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. ### 9. Prohibited Activity 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. ### 10. LUME: No Guidance, No Forecasts, No Listing Commitments Please read this Section carefully. It limits what you may rely on and the claims you may bring. #### 10.1 Who this Section covers In this Section, “Foundation Parties” means: - Lumera Foundation; - Its affiliates, subsidiaries, predecessors and successors, including, but not limited to, Pastel Growth Fund, LLC and Pastel Global Operations; - The current and former directors, officers, members, employees, contractors, consultants, advisors, agents, attorneys, ambassadors, community moderators and service providers of any of the above, including any market maker or liquidity provider engaged by any of them; and - Anyone else acting on behalf of any of them. #### 10.2 What LUME is LUME is the native utility token of the Lumera Protocol. It is designed to be used within the Protocol to: - Pay fees for protocol services, such as storing data with Cascade; - Pay transaction fees (“gas”); - Stake or delegate to validators to help secure the network; - Bond the SuperNodes that provide protocol services; and - Take part in on-chain governance. 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. #### 10.3 No guidance or forecasts THE FOUNDATION PARTIES DO NOT PROVIDE, AND HAVE NOT PROVIDED, ANY GUIDANCE, FORECAST, PROJECTION, PREDICTION, ESTIMATE OR ASSURANCE OF ANY KIND REGARDING: - (a) the price, value or market capitalization of LUME, now or at any future time, including at or after any listing; - (b) the liquidity of LUME, including trading volume, market depth, spreads, or your ability to sell, transfer, convert or exit a position; - (c) any return, yield, profit, gain, appreciation or income from acquiring, holding, staking, delegating, bonding, locking up or using LUME; - (d) staking rewards, APR, APY, commission rates, or validator or SuperNode income; - (e) circulating or total supply, inflation, burns, unlocks, vesting or release schedules, beyond what the Protocol’s code and published documentation state at the time; or - (f) the adoption, usage, revenue or success of the Lumera Protocol or anything built on it. #### 10.4 No commitment on listings, TGE or liquidity No Foundation Party promises, guarantees or undertakes that LUME will: - Be listed, or stay listed, on any centralized or decentralized exchange, or on any particular exchange or tier of exchange; - Be listed at any time, on any date, in any quarter or within any window; - Open, trade or settle at any price or within any price range; - Be supported by any market maker, liquidity provider, liquidity pool, bridge, wallet, custodian or on-ramp; or - Become transferable or tradable at any particular time, including in connection with any token generation event (“TGE”), listing event or network upgrade. 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. #### 10.5 Timelines are estimates, not promises A Foundation Party may mention a date, target, window, quarter, roadmap, schedule or other timeline for any of the following: - A listing or TGE; - A network upgrade or product release; - A token unlock; or - A program or campaign. 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. #### 10.6 Network figures are not forecasts The Services may display figures such as: - Staking APR; - Supply and bonded ratio; - Transaction counts and storage used; and - Fees and prices. 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. #### 10.7 Unauthorized statements 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. #### 10.8 No reliance 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: - Acquire, hold, stake, delegate, bond, lock up or otherwise use LUME; - Run a validator or SuperNode; or - Take part in any program. 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. #### 10.9 Waiver, release and covenant not to sue 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: - (a) the timing, occurrence, non-occurrence, delay, venue, terms or price of any TGE, exchange listing or delisting; - (b) the price, value, liquidity or volatility of LUME, or any lost opportunity or profit; - (c) any estimate, timeline or statement described in Sections 10.3 to 10.7; - (d) staking rewards, slashing, unbonding, lock-ups, vesting, unlocks or claims operating under the Protocol’s rules; or - (e) any act or omission of an exchange, market maker, liquidity provider, validator, SuperNode operator or other third party. 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. #### 10.10 Your responsibilities 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. #### 10.11 Signed agreements 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. #### 10.12 No professional advice 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. #### 10.13 Forward-looking statements 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. #### 10.14 Limits imposed by law 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. ### 11. Staking, Validators, SuperNodes and Upgrades Staking, delegating, and operating a validator or SuperNode involve the Protocol’s rules and parameters. These include: - Slashing, jailing and penalties; - Unbonding periods; - Commissions; and - Rewards that are variable and not guaranteed. 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. ### 12. Campaigns, Promotions and Rewards 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. ### 13. No Warranties 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: - The Services will be continuous, uninterrupted, timely or secure; - Any information, including live network statistics, will be accurate, complete or current; or - The Services will be free of errors, defects, viruses or other harmful components. 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. ### 14. No Fiduciary Duties 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. ### 15. Assumption of Risk 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: - Loss or theft of keys; - Software bugs and vulnerabilities in the Protocol, wallets or smart contracts; - Network failures, congestion, forks and upgrades; - Governance changes; - Actions of independent validators and SuperNode operators; - Price volatility; and - Changes in law or regulation. We are not responsible for these risks. You assume full responsibility for all risks of using the Services and the Protocol. ### 16. Third-Party Resources and Promotions 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. ### 17. Intellectual Property and Brand 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](https://lumera.io/brand). If you send us feedback or suggestions, we may use them without any obligation to you. ### 18. Release of Claims 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. ### 19. Indemnity 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: - Your access to or use of the Services; - Content you store or transmit; - Your violation of these Terms, any law or any third party’s rights; and - Anyone else’s use of the Services through a device, wallet or account you own or control. ### 20. Limitation of Liability 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: - Errors or inaccuracies in content; - Personal injury or property damage resulting from your use of the Services; - Unauthorized access to our servers or any data stored on them; - Interruption or cessation of the Services; - Bugs, viruses or similar code transmitted through the Services; - Loss or damage from your use of any content made available through the Services; or - The conduct of any third party, including validators, SuperNode operators and other users. 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. ### 21. Suspension and Termination 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. ### 22. Dispute Resolution 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](mailto:legal@lumera.io). ### 23. Class Action and Jury Trial Waiver 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. ### 24. Governing Law 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. ### 25. Miscellaneous 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. ### 26. Contact Lumera Foundation [legal@lumera.io](mailto:legal@lumera.io) ---