LighterIM

Lighter.IM Public Beta is LIVE! 🌐⛓️ Explore our non-custodial, multi-chain protocol today. 1️⃣ Follow the Guide: docs.lighter.im/docs/tutorial-… 2️⃣ Watch the Demo: patreon.com/posts/lighter-… 3️⃣ Join the Beta: beta.lighter.im Help us build a more secure way to move assets. 🛠️

1/4 Horizen生态项目@lighterim 团队发布了一篇《基于@Base生态的 $ZEN 机密隐私计算环境（HCCE）技术架构及其合规隐私范式研究报告》涵盖以下内容： 1.深度解构与架构机理 2.HCCE的应用场景与实际案例研究 场景1:机密去中心化金融 场景2:企业级资产管理与合规支付 场景3:消费者应用与数据主权

There have recently been some discussions on the ongoing role of L2s in the Ethereum ecosystem, especially in the face of two facts: * L2s' progress to stage 2 (and, secondarily, on interop) has been far slower and more difficult than originally expected * L1 itself is scaling, fees are very low, and gaslimits are projected to increase greatly in 2026 Both of these facts, for their own separate reasons, mean that the original vision of L2s and their role in Ethereum no longer makes sense, and we need a new path. First, let us recap the original vision. Ethereum needs to scale. The definition of "Ethereum scaling" is the existence of large quantities of block space that is backed by the full faith and credit of Ethereum - that is, block space where, if you do things (including with ETH) inside that block space, your activities are guaranteed to be valid, uncensored, unreverted, untouched, as long as Ethereum itself functions. If you create a 10000 TPS EVM where its connection to L1 is mediated by a multisig bridge, then you are not scaling Ethereum. This vision no longer makes sense. L1 does not need L2s to be "branded shards", because L1 is itself scaling. And L2s are not able or willing to satisfy the properties that a true "branded shard" would require. I've even seen at least one explicitly saying that they may never want to go beyond stage 1, not just for technical reasons around ZK-EVM safety, but also because their customers' regulatory needs require them to have ultimate control. This may be doing the right thing for your customers. But it should be obvious that if you are doing this, then you are not "scaling Ethereum" in the sense meant by the rollup-centric roadmap. But that's fine! it's fine because Ethereum itself is now scaling directly on L1, with large planned increases to its gas limit this year and the years ahead. We should stop thinking about L2s as literally being "branded shards" of Ethereum, with the social status and responsibilities that this entails. Instead, we can think of L2s as being a full spectrum, which includes both chains backed by the full faith and credit of Ethereum with various unique properties (eg. not just EVM), as well as a whole array of options at different levels of connection to Ethereum, that each person (or bot) is free to care about or not care about depending on their needs. What would I do today if I were an L2? * Identify a value add other than "scaling". Examples: (i) non-EVM specialized features/VMs around privacy, (ii) efficiency specialized around a particular application, (iii) truly extreme levels of scaling that even a greatly expanded L1 will not do, (iv) a totally different design for non-financial applications, eg. social, identity, AI, (v) ultra-low-latency and other sequencing properties, (vi) maybe built-in oracles or decentralized dispute resolution or other "non-computationally-verifiable" features * Be stage 1 at the minimum (otherwise you really are just a separate L1 with a bridge, and you should just call yourself that) if you're doing things with ETH or other ethereum-issued assets * Support maximum interoperability with Ethereum, though this will differ for each one (eg. what if you're not EVM, or even not financial?) From Ethereum's side, over the past few months I've become more convinced of the value of the native rollup precompile, particuarly once we have enshrined ZK-EVM proofs that we need anyway to scale L1. This is a precompile that verifies a ZK-EVM proof, and it's "part of Ethereum", so (i) it auto-upgrades along with Ethereum, and (ii) if the precompile has a bug, Ethereum will hard-fork to fix the bug. The native rollup precompile would make full, security-council-free, EVM verification accessible. We should spend much more time working out how to design it in such a way that if your L2 is "EVM plus other stuff", then the native rollup precompile would verify the EVM, and you only have to bring your own prover for the "other stuff" (eg. Stylus). This might involve a canonical way of exposing a lookup table between contract call inputs and outputs, and letting you provide your own values to the lookup table (that you would prove separately). This would make it easy to have safe, strong, trustless interoperability with Ethereum. It also enables synchronous composability (see: ethresear.ch/t/combining-pr… and ethresear.ch/t/synchronous-… ). And from there, it's each L2's choice exactly what they want to build. Don't just "extend L1", figure out something new to add. This of course means that some will add things that are trust-dependent, or backdoored, or otherwise insecure; this is unavoidable in a permissionless ecosystem where developers have freedom. Our job should make to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can.

@HorizenZH lighterim.horizen zkp.horizen ...

每个 .horizen 域名都包含用于协调和参与的链上功能。 不续租。已完全拥有。 👉立即认领您的 .horizen 域名： get.unstoppabledomains.com/horizen/?utm_c…

今天，Horizen与@unstoppableweb 合作，推出仅支持 Web3 的域名🧵 只有经得起实际考验的隐私才有意义。 应用程序负责价值转移、用户协调，并在公共环境中运行，这些环境中的假设会迅速受到考验。理论上有效的隐私保护措施在这种环境下往往会失效。

Builders who believe privacy should be practical are already shipping. Congrats to @HubzNetwork on completing Horizen Genesis and contributing to a privacy-first ecosystem built to last! 👏

🚀 Lighter.IM Multi-Chain Public Beta is launching soon! We are bringing the power of intent-based trading and #zkp to multiple chains. Get ready for a faster, more secure, and non-custodial experience. Join our community to stay updated and be among the first to test: 👉 t.me/lighterim_user #Web3 #DeFi #MultiChain #LighterIM #Uniswap #Permit2 @thriveprotocol @horizenglobal

Horizen’s mainnet is live on @Base. 🎉 A new chapter for onchain privacy begins today - bringing a seamless EVM-native environment designed for builders and users who want privacy that is practical, not complicated. @horizenofficial-2/welcome-to-privacy-on-base" target="_blank" rel="nofollow noopener">paragraph.com/@horizenoffici…

Huge W for ZK infra zkVerify’s numbers here change how builders think about routing, proofs, and UX including ramps like ours Solid analysis 👇

Light mode ON ~

When the entry point is trust-minimised, everything built on top scales faster. So… how does LighterIM hit different? • ZK-verified onboarding (privacy without drama) • Routing that actually finds liquidity • Infra that feels invisible • Built for teams tired of “almost works” ramps The result: a cleaner, quieter, lighter way to enter Web3 (And yes, it’s coming… soon 👀)

Problem: Users hit friction before they even touch crypto Solution: Lighter.IM Why? Cause it's a @ZKVProtocol-native entry point that removes blockers instead of well.. adding more steps. And how? By fixing the first bottleneck in the stack with a ZK-powered fiat gateway that gives users instant, verified, compliant access to onchain assets without the trust overhead. → docs.lighter.im/docs/intro

LighterIM → Own your trades ~

Your LighterIM Ticket = ERC-6551 NFT ✨ Tracks your cred, not your assets~ Lose it? Your funds stay cozy in escrow. Reputation ≠ custody.

LighterIM → Privacy by default ~

Most ‘fiat ramps’ = ➡️ Custodial ➡️ KYC farm ➡️ Middlemen everywhere Lighter flips it. ZK proof generated on your device. Escrow → proof → done.

@HorizenLabs @idOS_network @horizenglobal @ZKVProtocol 🤝

Thrilled to be part of the @idOS_network Consortium. @horizenglobal and @ZKVProtocol are aligned with idOS’ mission to bring user-owned identity to the internet and we are ready to contribute with real infrastructure and builder support. Looking forward to what we build together 🤝

Privacy isn’t a luxury, it’s infrastructure. @thriveprotocol and @horizenglobal are funding the builders creating a private Web3, real teams, real products, real utility. From private DEXs to ZKP-enabled on/off ramps, here’s the new generation of privacy-first apps: 1️⃣ @zendexfi — MEV-proof trading 2️⃣ @tachyonpe — Cross-chain transfers with no surveillance trail 3️⃣ @datahubz — “Don’t trust, verify” enterprise compliance 4️⃣ @nyra_perp — Private perpetuals 5️⃣ @UseObscura — Social trading with verifiable PnL 6️⃣ @LighterIM — ZK-powered fiat gateways 7️⃣ @AdPrivaAds — Verifiable ad engagement without exposing data This is Thrive Protocol in action, connecting capital to measurable outcomes and reshaping how privacy, proof, and progress coexist.

@horizenglobal @thriveprotocol @zendexfi @tachyonpe 💙

And the list keeps growing! Here are the teams we're supporting through the @thriveprotocol x Horizen Developer Grant Program: @zendexfi - Private DEX that stops MEV bots from front-running your trades @tachyonpe - Cross-chain transfers that break the surveillance trail @datahubz - Enterprise compliance with cryptographic proof instead of "trust me" audits @nyra_perp - Private perpetuals trading @UseObscura - Social trading with verifiable PnL @LighterIM - ZKP-enabled off/on-ramps @AdPrivaAds - Verifiable ad engagement with ZKPs @GamblorCasino - Provably fair gaming with privacy built into every hand

Stacked cohort, serious builders 😼 LighterIM is here to make fiat ↔︎ crypto light B_ _ _ loading… ~

LighterIM → Test it, win trust ~

Quick LighterIM flow: 1️⃣ Seller signs intent (Permit2 + Nostr) 2️⃣ Buyer accepts & pays fiat off-chain 3️⃣ ZKP proves payment → assets auto-release Fiat → crypto, trustless.