OP Labs privacy SDK discussed online

Posts on X on May 20 put a new crypto infrastructure idea into circulation: a privacy SDK for apps built on the OP Stack. No public product post, code release or documentation page from OP Labs describing such an SDK was available in reviewed OP Stack and Optimism materials on May 21, but the discussion itself pointed to a familiar problem for Ethereum-based systems — how to add confidentiality without abandoning public-chain settlement. The comparison that appeared most often was StarkWare’s privacy tooling on Starknet. StarkWare said on May 12 that strkBTC had gone live on Starknet with “shielded balances” and “private transfers” through its STRK20 framework, giving developers and users a live example of privacy features attached to an existing token and wallet flow. ### Was there an actual OP Labs product launch? OP Labs and Optimism did not publish a public announcement matching the social-media description in the materials reviewed on May 21. The main OP Stack pages describe the stack as an open-source, modular framework for launching blockchains, and the developer documentation presents the OP Stack as infrastructure for rollups and chains rather than as a privacy product. GitHub’s main Optimism repository likewise presents the OP Stack as a collaborative open-source project and does not surface a public privacy SDK release in the reviewed results. (starknet.io) That means the current state of the story is discussion of a concept, not a verified launch. ### What were developers actually talking about? May 20 posts described a toolkit that could give OP Stack applications privacy primitives rather than make the base stack itself private, according to the social briefing supplied for this story. (docs.optimism.io) In practice, that usually means app-level functions such as hidden balances, private transfers, selective disclosure or shielded transaction flows, while leaving the underlying chain architecture in place. The OP Stack’s own public description makes that framing plausible. (github.com) Optimism says the OP Stack is modular and can be adopted “layer by layer,” which is the kind of architecture developers typically cite when discussing add-on components such as identity, compliance or privacy modules. ### Why did StarkWare’s Privily and STRK20 come up in the discussion? StarkWare provided the clearest live comparison. Starknet said on April 20 that version 0.14.2 added infrastructure for private transactions, and on May 12 it said strkBTC had gone live as the first asset built on STRK20, with public and shielded modes. StarkWare’s STRK20 site says the framework brings private transfers to tokens on Starknet using zero-knowledge proofs and includes a compliance-ready design. (optimism.io) A February 17 StarkWare post on Nightfall also showed the company pushing institutional privacy use cases onchain. That post said Nightfall on Starknet was aimed at privacy-preserving transaction flows for regulated businesses, including KYC-aligned private payments and settlement workflows. ### What do ZK, MPC and TEE mean in this context? Zero-knowledge proofs, or ZK, are the approach StarkWare is publicly using in STRK20, based on its product pages and blog posts. (starknet.io) Those materials describe private transfers and shielded balances while preserving verifiability onchain. MPC, or multi-party computation, and TEE, or trusted execution environments, were cited in social posts as other design options for privacy stacks, according to the supplied briefing. (starkware.co) No OP Labs technical document reviewed on May 21 set out a public choice among those approaches, so any claim about a final architecture would go beyond the available evidence. ### Where would a real OP Stack privacy effort show up next? Optimism’s documentation hub, developer docs and the main Optimism GitHub repository are the public places where a formal SDK, specification or code contribution would most likely appear. (starknet.io) Those pages were live on May 21 and remain the clearest public record for any next step tied to OP Stack infrastructure. (github.com)