plzdontclickhere.

Since we started the project, I’ve been telling the @circle team that this will be the last privacy solution in blockchain space. And we delivered. What we have built is not just privacy-preserving smart contracts. Instead, it's a paradigm shift in how blockchains, composability, and privacy need to co-exist. The design addresses the two core failures of prior privacy systems: lack of composability and a painful developer journey. Pure cryptographic privacy is elegant, but expensive and hard to scale in practice. Instead, this design builds on the now-established trend of cryptographic enclave technologies. What we’ve built is a parallel execution environment on @arc : Arc public blockchain continues processing cleartext blocks, while the Arc privacy sector operates as a parallel privacy-preserving virtual machine that processes encrypted transactions. State, transactions, and user accounts remain hidden. Validators cannot inspect what’s inside, even if they try to snoop or are compromised. Yet they continue producing blocks for both public and private states in sync, committing to each state tree. That is also a major difference from designs that rely on access control, which inevitably creates failure points and data exposure risk. The public and private state composition is the game changer for developing. For the first time, users can move between private and public state within the same block space. No bridge. No extra wallet layer. No separate accounts. A single transaction can move between private and public execution with zero friction. Furthermore, the environment gives users post-quantum protection by design. Transactions and accounts remain encrypted, and public keys stay protected under post-quantum secure algorithms. Any account or asset created inside the privacy sector is automatically post-quantum secure. The result: a fully composable privacy sector on @arc that is post-quantum secure and seamlessly interoperable with public execution. This is the last privacy layer in Web3. See the whitepaper: https://t.co/Fz0IMafS2a @circle @arc

sergey_nog's tweet photo. Since we started the project, I’ve been telling the @circle team that this will be the last privacy solution in blockchain space.

And we delivered.

What we have built is not just privacy-preserving smart contracts. Instead, it's a paradigm shift in how blockchains, composability, and privacy need to co-exist. The design addresses the two core failures of prior privacy systems: lack of composability and a painful developer journey.

Pure cryptographic privacy is elegant, but expensive and hard to scale in practice. Instead, this design builds on the now-established trend of cryptographic enclave technologies.

What we’ve built is a parallel execution environment on @arc :

Arc public blockchain continues processing cleartext blocks, while the Arc privacy sector operates as a parallel privacy-preserving virtual machine that processes encrypted transactions.

State, transactions, and user accounts remain hidden. Validators cannot inspect what’s inside, even if they try to snoop or are compromised. Yet they continue producing blocks for both public and private states in sync, committing to each state tree.

That is also a major difference from designs that rely on access control, which inevitably creates failure points and data exposure risk.

The public and private state composition is the game changer for developing. For the first time, users can move between private and public state within the same block space. No bridge. No extra wallet layer. No separate accounts. A single transaction can move between private and public execution with zero friction.

Furthermore, the environment gives users post-quantum protection by design. Transactions and accounts remain encrypted, and public keys stay protected under post-quantum secure algorithms. Any account or asset created inside the privacy sector is automatically post-quantum secure.

The result: a fully composable privacy sector on @arc that is post-quantum secure and seamlessly interoperable with public execution.

This is the last privacy layer in Web3.

See the whitepaper: https://t.co/Fz0IMafS2a

@circle @arc

117

55K

plzdontclickhere. @plzdntclickhere

about 1 month ago

@KookCapitalLLC @Evan_ss6 bro you're so right. holy shit. closed source apps are immue from all of the opensource tokens and software it uses to operate. truly genius.