how a private stablecoin transfer should feel: open your wallet. toggle private on and hit send. no one else can see it. how it actually works on Arc : configurable privacy at the protocol layer, encrypted state in hardware enclaves, master key threshold-split across validators, post-quantum from day one.... what each piece actually does ↓show more

configurable privacy at the protocol layer. apps and assets decide what stays private: transactions, balances, contract state, workflows. The same wallet holds public and private. The same solidity deploys in either execution environment (private EVM compatibility!)

encrypted state in hardware enclaves + threshold-split master key signing private state runs inside TEEs (AWS Nitro Enclaves), isolated from the host OS and the validator operator. the decryption key is split across the validator set. NO SINGLE party can decrypt alone

post-quantum from day one. confidentiality today has to hold against a future quantum computer that can break ECC. Arx uses X-Wing (ML-KEM-768 + X25519) a hybrid KEM combining classical and post-quantum security. harvest-now-decrypt-later doesn't work here.

selective disclosure, on your terms. view keys let you or a counterparty (auditor, admins etc) reveal specific transactions, balances, or contract state whether for compliance, audit, or verification. Private by default and auditable when you choose. One network. One send. No one else sees it unless you say so Full design in the arc privacy whitepaper

@arc 🛡️

@arc do you like dog @0xrachelita

@arc 100 percent crazy how much is going on under the hood, but how simple the UX is

X-Wing on the wire is the right call, and it settles harvest-now-decrypt-later for transport only. The threshold-split key is the part to read carefully: a quorum of validators can reconstruct it and decrypt every past state, so confidentiality holds as long as no quorum ever colludes, for as long as the ciphertext matters. That is a governance guarantee rather than a cryptographic one, and a different promise from ZK privacy, where no set of parties can. The other classical leg is attestation: a share is only released to an enclave the validator believes is real, and Nitro attestation documents are signed with ECDSA P-384, so the post-quantum story ends at the attestation root until that moves too.

@arc Great feature! I’ll try it out in a bit. Is the long-term goal for privacy to extend beyond transfers to other onchain activity as well?

@arc the duke of arc

@arc ArcticAnimals see privacy evolving with Arc’s protocol

@arc Good tek 🔥

@arc Would you ever default it on?

@arc This is exciting!

@arc Intresting 👀

@blockjain @arc you have a cat too?

@arc all of that behind one toggle

@arc 💯

@arc Build on arc

@arc Will Duke be included in the future? Performing privacy transfers at the token level

@arc Did you launched Bancor and other tokens?

@arc sent u a dm

@arc Its done

@arc SAVE DUKE

@arc Arc is the OS of the web3

@arc Looks like true financial freedom is within reach now

@arc Ok, so you can shill now your pets name

@arc ArcticAnimals see privacy evolving with Arc’s protocol

@arc Saw the privacy feature 👀