LumosCore
Multichain Web3 Infrastructure
One interface. Every network. Custody nowhere.
Abstract
Where the industry has been, and the trade-off LumosCore refuses to make.
The first generation of crypto infrastructure made digital assets accessible through centralised exchanges. The model was simple: create an account, deposit assets and trade through one interface. It solved the usability problem, but introduced a fundamental trade-off. The exchange held the keys.
The emergence of decentralised finance changed that model. Users could interact with markets directly from their own wallets, without depositing assets into a centralised platform. But another problem emerged. As blockchain ecosystems multiplied, decentralised activity became increasingly fragmented across networks, wallets, applications and liquidity venues.
LumosCore is designed around the next step in that evolution.
The simplicity of a unified platform, with the control of self-custody.
LumosCore provides a unified interface for trading, liquidity, token issuance, cross-chain transfers, wallet functionality, asset discovery and rewards across supported blockchain ecosystems.
The underlying networks remain independent. Transactions are constructed for the relevant network and signed by the user's own wallet. LumosCore does not custody user assets, maintain user balances or operate a bridge holding pooled customer funds.
Cross-chain transport is delegated to external protocols and selected on a network-by-network basis according to defined requirements, including the avoidance of LumosCore custody and a preference for canonical assets where available.
This whitepaper explains the problem LumosCore is addressing, the platform architecture, its current deployment, economics, expansion strategy and associated risks.
From CEX to Multichain
How the industry traded custody for usability, then usability for fragmentation.
1.1The first problem: access
For much of crypto's early growth, the easiest way to interact with digital assets was through a centralised exchange. The model was familiar.
The complexity of blockchain infrastructure was largely hidden from the user.
That simplicity came from centralisation. A centralised exchange controls the infrastructure through which customer assets are held and transactions are executed. Coinbase, for example, explicitly describes its exchange as a custodial service in which it maintains the private keys for assets held on its platform.
This creates a fundamental trade-off: convenience increases, but the user gives up direct control of the keys. The exchange becomes a counterparty. Its security, solvency, operational controls and governance become relevant to the user's ability to access their assets.
The industry has seen the consequences when that relationship breaks down. Major exchange incidents have included the Mt. Gox hack, the Bitfinex hack and the collapse of FTX.2 The common characteristic is not that every event had the same cause, but that users had entrusted assets to a centralised intermediary.
This created one of the defining principles of decentralised finance.
Users should be able to interact with financial infrastructure without first surrendering custody of their assets.
1.2The second problem: custody
Decentralised exchanges changed the architecture. Instead of depositing assets with an exchange, users could connect their own wallets and interact directly with on-chain markets. The private key remained with the user. The exchange no longer needed to hold the user's assets.
This solved an important problem. But it introduced another.
The infrastructure became distributed. A user might now need one application for trading, another for liquidity, another for bridging, another for wallet activity and another for interacting with a different blockchain.
Self-custody solved the custody problem. It did not solve the fragmentation problem.
1.3The multichain problem
The industry continued to expand. Ethereum was joined by Layer 2 networks, alternative Layer 1s, appchains and specialised ecosystems. Liquidity moved across them. Projects deployed across them. Users began holding assets across them.
The result is an ecosystem where the underlying technology can be powerful, but the experience can be unnecessarily complicated. A user who operates across several networks may have to understand:
The user did not necessarily ask for any of that complexity. They simply wanted to use their assets. This creates two costs.
The number of networks is growing. The interface should not have to grow with it.
1.4The LumosCore thesis
Self-custody should not require a fragmented user experience.
The goal is not to replace blockchains. It is not to force every network into one technical architecture. And it is not to create another custodial exchange.
Instead, LumosCore provides a unified interface through which users can access functionality across supported ecosystems while the underlying assets and settlement remain on the relevant networks. This creates a different model:
| Model | User experience | Asset custody |
|---|---|---|
| Centralised exchange | Unified | Platform controlled |
| Individual DeFi apps | Fragmented | User controlled |
| LumosCore | Unified | User controlled |
Table 1. Where the experience is unified, and where custody sits. This is the core idea behind the platform — everything else in the architecture follows from it.
The LumosCore Platform
Seven kinds of on-chain activity behind one interface.
LumosCore brings multiple forms of on-chain activity into one interface. Every entry below is a live page on the platform.
The objective is not simply to put more features on one website. It is to remove unnecessary boundaries between the activities users already perform across Web3.
Architecture
Three parties, three jobs — and none of them holds anyone else's assets.
The platform is built around a separation of responsibilities.
This distinction is fundamental.
3.1Non-custodial execution
Transactions are constructed client-side and signed in the user's own wallet. LumosCore does not hold private keys. It does not maintain a custodial balance for users. It does not have a privileged mechanism through which it can move customer assets. There is no requirement to deposit funds before using the platform.
This means LumosCore does not need to become the counterparty between the user and the blockchain. The user authorises the transaction. The relevant network executes it.
3.2Network-native infrastructure
Each blockchain remains its own source of truth. LumosCore reads balances, market information and position state from the relevant network sources and presents that information through a common interface. Transactions are similarly constructed according to the requirements of the network on which they will execute.
This allows LumosCore to maintain a consistent user experience without pretending that different blockchains are technically identical. Adding a network therefore means integrating its:
The user experience stays consistent. The infrastructure underneath adapts.
3.3Platform infrastructure
LumosCore uses static pages served through a CDN together with stateless edge functions. There is no requirement for a large per-user infrastructure footprint.
This architecture is intended to allow the platform to scale its user base without requiring an equivalent increase in user-specific infrastructure.
Cross-Chain Infrastructure
The mechanism can differ between networks. The requirements do not.
Cross-chain functionality is essential to a multichain platform. It is also one of the areas where security assumptions need to be explicit.
LumosCore therefore does not operate a custodial bridge holding pooled user assets. Instead, cross-chain transport is delegated to external protocols.
Transport requirements
LumosCore must not take possession of user funds during a cross-chain transaction.
When a transport mechanism can deliver a canonical asset rather than a wrapped representation, the canonical route is preferred.
The user should know which transport mechanism is being used and understand its relevant assumptions before signing.
This approach avoids making one bridge or protocol a permanent dependency of the entire platform.
Multichain infrastructure creates another challenge: asset identity.
A ticker is not unique. Anyone can issue an asset called USDC. The issuer and issuing account are what identify the asset.
LumosCore therefore uses the network's domain-attestation standard to establish a stronger relationship between an asset, its issuer and its domain. The verification process works as a two-way relationship:
The issuing account publishes its domain on-chain.
That domain identifies the corresponding asset and issuing account.
LumosCore checks that the two references resolve to each other.
The asset receives the verification mark only when the relationship resolves successfully.
5.1Verification is not endorsement
A verification mark means identity, not quality. It does not mean that LumosCore:
It simply provides additional evidence that the asset is associated with the issuer and domain it claims.
By the handshake, which is automatic and free; or by a hand review, which is what a curated listing is. The route is recorded on every mark and shown on the asset, so a domain the issuer controls and a listing LumosCore stands behind remain distinguishable. Neither route is a purchase: a declined application is refunded in full and carries no mark, and creating an asset through the launchpad qualifies it for nothing on its own.
Current Deployment
Live functionality as of August 2026 — not a roadmap.
The following functionality is live as of August 2026.
| Capability | Production functionality |
|---|---|
| Trading | Swaps and limit orders against the network's order book and pools, priced from executed on-chain trades. |
| Liquidity Pools | Pool creation, liquidity deposits and withdrawals without a lock-up period. |
| Token Issuance | Asset issuance, supply minting and initial pool creation through a single flow. |
| Cross-Chain | USDC transfers between Stellar and Ethereum, Base, Arbitrum, Optimism, Polygon, Avalanche, Linea and World Chain through the transport architecture described in Section 4. |
| Wallet | Balances, activity, trustlines and claimable payments through a non-custodial interface. |
| Curated Listings | Hand-reviewed listings with issuer verification, per Section 5. |
| Rewards | Three liquidity and holding programmes distributing LUMOS on fifteen-day cycles. |
Table 2. Production functionality, August 2026. Each linked capability opens the live page.
Economics
Priced before the signature, settled on-chain, no spread on the quote.
LumosCore monetises activity occurring across the platform. The pricing model is designed to be visible before a transaction is signed. There is no additional spread added to quoted prices and no platform fee introduced after the user signs.
| Revenue stream | Price | Details |
|---|---|---|
| Trading | 0.2% | Reduced to 0.1% for holders of 250,000+ LUMOS. LUMOS held in liquidity pools counts toward the threshold. |
| Limit Orders | Free | Network fee only. |
| Cross-Chain | 0.2% / 0.1% | Same LUMOS threshold as trading. External transport and network costs are passed through without markup. |
| Token Issuance | $25 | $5 asset creation + $10 opening liquidity + $10 pool and network setup. |
| Curated Listing | $250 | Manual review and issuer verification. Fully refunded in the asset paid if the listing is declined. |
| Advertising | $15 / 1,000 | Impressions, minimum 5,000. Payable in the network's native asset or LUMOS. |
Table 3. Revenue streams and prices.
7.1LUMOS utility
LUMOS is integrated into the platform's economic model through:
Holding at least 250,000 LUMOS qualifies a user for the reduced trading and cross-chain fee tier. LUMOS held within a liquidity pool counts toward the threshold. Token details are published at lumoscore.com/lumos.
LUMOS does not represent equity in LumosCore OÜ, a debt claim, a dividend or a governance right over the company.
7.2Revenue model
The platform's revenue model is designed around activity rather than account balances.
The infrastructure model is designed so that increasing the number of users does not require an equivalent increase in user-specific infrastructure.
Expansion
More networks behind the same interface — chosen by activity, not novelty.
LumosCore's long-term opportunity comes from extending the same interface across an increasingly multichain ecosystem. The objective is not simply to maximise the number of supported networks.
Network integrations will be driven by the presence of:
8.1Additional networks
Each new network requires its own data integration, transaction construction, wallet signing path and appropriate cross-chain infrastructure. The user should not have to learn those differences simply because LumosCore has added another network.
8.2Multichain Explorer
As users hold and transact across multiple ecosystems, activity becomes increasingly difficult to monitor. LumosCore plans to develop a native multichain explorer that brings activity from supported networks into one interface.
8.3Native Multichain Wallet
LumosCore also intends to extend its wallet capabilities through a mobile-first, passkey-based wallet. The objective is to make holding and using assets across networks part of the same experience while preserving self-custody.
Team
References
- 1Aggregate decentralised exchange volume. DeFiLlama, defillama.com/dexs.
- 2Centralised exchange security and custody risks are documented across industry research and incident reports. Historical examples include the Mt. Gox and Bitfinex hacks and the FTX collapse.
- 3Cross-Chain Transfer Protocol. Circle, circle.com/cross-chain-transfer-protocol.
This document is published for informational purposes only.
It is not an offer to sell or a solicitation to buy any asset and does not constitute investment, legal, tax or financial advice. It should not be relied upon when making financial decisions.
LUMOS is a utility token used for fee reduction and reward distribution on the platform. It confers no equity, debt claim, dividend or governance right over LumosCore OÜ.
Statements concerning future development represent current intentions and may change without notice. Statements concerning deployed functionality describe the platform as of August 2026.
Digital assets are volatile and may lose all of their value.
LumosCore operates on a non-custodial basis. Users retain sole control of their keys and sole responsibility for transactions they authorise.