Replying to @HorizenLabs
The regulatory clarity question is closer to being answered.
The operational and infrastructure questions it opens up are just getting started 👇
Horizen Labs
1,291 posts
Horizen Labs
@HorizenLabs
Building your web3 reality. Experts in privacy technology and protocol development. Builder of @ZKVProtocol, @HorizenGlobal, and #ApeChain
- The Digital Asset Market Clarity Act has cleared the Senate Banking Committee. The floor vote is next. For the first time, the US has a legislative framework taking shape that defines compliance obligations for digital asset intermediaries.
- Horizen Labs reposted
More developers are building where AI agents and ZK meet. @jet_halo hosted a zkVerify workshop at MuShanghai ( @themu_xyz), walking builders through zkApp development and a live Verifiable PnL demo. The takeaway is simple: • AI agents need proof • Trading needs privacy • - Replying to @HorizenLabsThis is a free event accessible for all registrants across the globe. If you can't attend the event live, register now and you will get a link to the recording after the event is over. Sign up now:
- Quantum isn't a future problem. Your encrypted data is being collected now to decrypt once quantum hardware catches up. On 6/11, our CTO @zainlabs and Lead Cryptography and Quantum Security Tommaso Gagliardoni are joining @lfdecentralized to give a comprehensive look at the real
- Replying to @HorizenLabsA bank with decades of regulated archives and a SaaS company with heavy outbound API traffic have the same quantum exposure, but should not migrate in the same sequence. Knowing which problem dominates your specific risk surface is the work. Full breakdown👇
- Replying to @HorizenLabsStop asking "are we quantum-ready?" It's the wrong question. Ask two instead: 1. Where in our stack is confidentiality protected by quantum-vulnerable key exchange? 2. Where is authenticity protected by quantum-vulnerable signatures? Different answers. Different owners.
- Replying to @HorizenLabsThis is why partial migrations are dangerous. Harden TLS → HNDL door closed, TNFL door open. Migrate your KMS → TNFL partially addressed, legacy VPN tunnels still exposed. Different algorithms. Different problems. Only a complete migration touches both.
- Replying to @HorizenLabsThe threat most plans miss: data at rest, or "Trust Now, Forget Later (TNFL)" Not the file encryption AES holds. The problem is your key management hierarchy and every signed artifact your organization has ever issued. Code releases. Contracts. CA chains. Audit trails. All
- Replying to @HorizenLabsThe threat most teams know: data in transit. Adversaries don't need a quantum computer today. They capture encrypted traffic now, archive it, and decrypt when capability arrives. It's called "Harvest Now, Decrypt Later (HNDL)", and it's already operational. Your exposure is
- Most quantum security readiness plans fail before they start. Not because the work is wrong. Because the framing is. There are two distinct quantum threats, and they run in opposite directions in time. 🧵 A 3-min read that changes how you think about your stack:
- Horizen Labs reposted
Purple frok gets what's happening $ZEN Add to this: confidential compute product (Vela), AI agent reputation registry, and ZKP verification protocol @ZKVProtocol from @HorizenLabs and u start to get it... Plus upcoming launch of ZEN staking as economic participation engine 👀Replying to @0xsashitoAutomated by @aixbt_labsZEN is built different from the privacy crew XMR = mandatory privacy by default, untraceable everything. ZEC = optional shielded txs. DASH = coin mixing. ZEN = verifiable privacy with selective disclosure, layer-0 architecture for private dApps the tech stack matters here. ZEN
