As blockchain applications gradually expand into stablecoins, DeFi, and cross-border payments, transparent on-chain data is exposing more privacy issues, including address linkage, fund flow tracking, and user behavior analysis. Privacy protocols have therefore become an important part of Web3 infrastructure, and Lelantus Spark is one of the more representative solutions in the recent evolution of privacy protocols.
Compared with traditional privacy coins that mainly focus on anonymous transfers, Lelantus Spark places greater emphasis on a transaction structure that is “verifiable but untraceable.” Its design is not only used to hide user transaction activity, but also provides the underlying support for Spark Assets, private stablecoins, and confidential asset systems. Within the Firo ecosystem, Lelantus Spark is not just an anonymous transaction tool, but the core infrastructure of the entire private finance system.
Lelantus Spark is a zero-knowledge privacy protocol launched by Firo. It is used to hide the sender, recipient, and amount in on-chain transactions. Its design focuses on breaking the on-chain link between transaction inputs and outputs through anonymity pools and zero-knowledge proofs.
Compared with Firo’s earlier Sigma and Lelantus protocols, Spark further improves transaction efficiency, privacy structure, and user experience. Spark also introduces a new address model, making anonymous transactions feel closer to ordinary cryptocurrency transfers.
Ordinary blockchain transactions are usually fully public. Anyone can view wallet addresses, asset flows, and transfer amounts. Lelantus Spark hides this key data, reducing the likelihood that on-chain analytics tools can trace user activity.
On traditional public chains, transaction inputs and outputs usually have clear links. Spark tries to break that linkage structure.
Firo previously used the Zerocoin and Sigma protocols, but as privacy technology evolved, the project needed a more efficient and flexible anonymity model. One of Spark’s main goals is to improve privacy and scalability without relying on a trusted setup.
A Firo private transaction usually begins when a user converts public assets into anonymous assets.
The user first transfers ordinary public FIRO into the Spark anonymity pool. During this process, assets on the public chain are converted into an anonymous state.
This is similar to “repackaging” publicly traceable assets as anonymous assets, reducing the risk of linking them back to the original address.
Users rely on Spark addresses when making private transactions. Unlike traditional public addresses, Spark addresses do not directly expose long-term asset relationships.
Spark addresses are designed to reduce the on-chain tracing risks caused by address reuse.
All assets that enter the Spark system become part of a shared anonymity pool. As the pool grows, the link between a single transaction and its original source becomes harder to identify.
The anonymity pool is the core structure of the Lelantus Spark privacy model. Its role is to mix a large number of user transactions, improving anonymity.
An anonymity set can be understood as a “set of possible transaction sources.” The larger the anonymity set, the harder it is for outside observers to determine which asset came from the real sender.
Spark’s anonymity does not rely on mixing just two individual transactions. Instead, it is built on a much larger anonymity pool.
On public blockchains, transaction paths can usually be tracked continuously. An anonymity pool breaks this continuity, making it difficult to create a direct mapping between inputs and outputs.
This mechanism is similar to placing many identical assets into a shared pool, then withdrawing assets again from that pool.
CoinJoin usually requires multiple users to participate in transaction mixing at the same time. Spark’s anonymity pool structure is more flexible and does not require users to participate synchronously.
Compared with CoinJoin, Spark is better suited to long-term anonymity set expansion.
Lelantus Spark uses zero-knowledge proofs to verify transaction validity while avoiding the exposure of specific transaction details.
Zero-knowledge proofs are a cryptographic technique that allows users to prove something is true without revealing the underlying data.
In Spark, the network can verify that a user really owns the assets and satisfies the transaction rules, without publicly revealing the source or amount of those assets.
Even when transaction details are hidden, Spark still uses cryptographic mechanisms to ensure that the same asset cannot be spent more than once.
This means the system can protect privacy while maintaining blockchain security and consistency.
Some zero-knowledge protocols require a trusted setup. If the initialization process has problems, it could theoretically affect system security. One of Spark’s design goals is to avoid this dependency.
Spark addresses are one of the important structures introduced by Lelantus Spark. Their role is to improve the private transaction experience.
Traditional public addresses are usually fixed over long periods, making it easy to build a complete on-chain asset profile. Once an address is linked to a real-world identity, historical transaction records can also continue to be tracked.
Spark addresses do not directly expose long-term asset relationships, nor do they publicly display the full flow of funds the way ordinary addresses do.
This structure is better suited to payment scenarios that require privacy protection.
Spark addresses are mainly used for private transaction scenarios, while ordinary public addresses can still be used for regular on-chain transfers.
Beyond on-chain privacy, network-layer privacy is also important. Even when transaction data is hidden, node broadcast paths may still expose a user’s IP address.
Dandelion++ divides transaction propagation into two phases, Stem and Fluff. In the initial phase, a transaction randomly passes through multiple nodes. Only afterward is it broadcast to the entire network.
This mechanism can reduce the likelihood that an attacker identifies the transaction source through the broadcast path.
Without network-layer privacy, a user’s IP address may still reveal the real source of their activity, even if transaction amounts and addresses are hidden.
For this reason, on-chain privacy and network-layer privacy usually need to be used together.
Firo, Monero, and Zcash all follow privacy protocol paths, but their underlying designs are clearly different.
| Comparison Dimension | Lelantus Spark | Monero RingCT | Zcash zk-SNARKs |
|---|---|---|---|
| Amount Hiding | Supported | Supported | Supported |
| Address Privacy | Supported | Supported | Supported |
| Trusted Setup | Not required | Not required | Required |
| Anonymity Structure | Anonymity pool | Ring signatures | Zero-knowledge proofs |
| Network-Layer Privacy | Dandelion++ | Dandelion++ | Partially supported |
Compared with RingCT and zk-SNARKs, Spark places greater emphasis on an anonymity pool structure that does not require a trusted setup, along with scalable confidential asset capabilities.
Lelantus Spark is the core protocol in Firo’s privacy system. Through anonymity pools, Spark addresses, and zero-knowledge proofs, it hides transaction senders, recipients, and amounts, reducing the risk of on-chain tracing. Compared with traditional public blockchain transactions, Spark places greater emphasis on a “verifiable but untraceable” privacy model and strengthens network-layer anonymity through Dandelion++.
As blockchain use cases gradually expand into stablecoins, DeFi, and digital asset issuance, privacy infrastructure continues to become more important. The anonymous asset structure explored by Lelantus Spark has also become one of the key technical paths for private finance in Web3.
Spark breaks the link between transaction inputs and outputs through anonymity pools, Spark addresses, and zero-knowledge proofs.
No. One of Spark’s design goals is to avoid reliance on a trusted setup.
Spark addresses are mainly used for anonymous transactions and do not directly expose long-term asset relationships the way ordinary public addresses do.
Yes. Lelantus Spark can hide transaction amounts and fund flows.
Spark handles on-chain privacy, while Dandelion++ handles network-layer privacy. Together, they reduce the risk of users being traced.





