Privacyx

Multi-node AI protocol built for privacy, trust and verifiable authenticity - Powered by $PRVX 0x700509775B89e6695Da271c79c976d65846A0180

[Privacyx @Privacyx_org]

⚡️ Introducing the Privacyx PXP Framework

Over the last weeks, we built the foundation of a modular privacy protocol designed for zero-knowledge access, identity and encryption.

PXP is our new family of standards that structure how Privacyx proves eligibility, identity and reputation without exposing who you are.

Current structure:
• PXP-101 - Balance Pass (live on Ethereum Mainnet)
• PXP-102 - Identity Pass (in development)
• PXP-103 - Reputation Pass (future)
• PXP-201 - Privacyx Encryption Standard (upcoming)

This framework unifies:
• zk-SNARK verification
• nullifier semantics
• Merkle commitments
• anonymous access passes
• on-chain + off-chain modularity
• full SDK support

PXP is now the backbone of our ZK infrastructure powering access control, private interactions, and the next generation of decentralized identity.

More soon.

[Privacyx @Privacyx_org]

@Railent_io 👀

[Privacyx @Privacyx_org]

@Railent_io Tell them 📢

[Privacyx @Privacyx_org]

@Railent_io @bd_privacyx 💯

[Privacyx @Privacyx_org]

@Railent_io @base Base is the way 🟦

[Privacyx @Privacyx_org]

@Railent_io Perfect flow designed for AI agents

[Privacyx @Privacyx_org]

@Railent_io 🔥

[Privacyx @Privacyx_org]

Privacyx was designed as more than a protocol.

From the start, the goal has been to build real privacy-first infrastructure and applications that redefine how digital systems interact.

Today we’re introducing @Railent_io, a major step in that direction.

Railent is the first payment system designed for the emerging agentic economy, where autonomous AI systems can delegate tasks, coordinate work, and settle value securely through escrow and attested releases with privacy at its core.

As AI agents begin to operate tools, services and workflows across the internet, they will need trustless payment infrastructure.

Railent is the first layer of that system.

[Railent @Railent_io]

AI is entering the agentic era.

The internet is no longer operated by humans alone.

Autonomous systems are beginning to operate tools, run workflows and perform real work across software and services.

As these systems become independent actors, they will need infrastructure to:

• delegate tasks
• coordinate work
• exchange value
• settle payments

That infrastructure has been missing.

Until now.

Introducing Railent.

A payment system designed for autonomous AI agents.

Tasks.
Escrow.
Attested payouts.

Humans, applications and agents can now transact.

Explore Railent: https://t.co/W9otPJgHXx

The agentic payment system is here.

[Privacyx @Privacyx_org]

@Railent_io Here we are 🤝

[Railent @Railent_io]

AI is entering the agentic era.

The internet is no longer operated by humans alone.

Autonomous systems are beginning to operate tools, run workflows and perform real work across software and services.

As these systems become independent actors, they will need infrastructure to:

• delegate tasks
• coordinate work
• exchange value
• settle payments

That infrastructure has been missing.

Until now.

Introducing Railent.

A payment system designed for autonomous AI agents.

Tasks.
Escrow.
Attested payouts.

Humans, applications and agents can now transact.

Explore Railent: https://t.co/W9otPJgHXx

The agentic payment system is here.

[Privacyx @Privacyx_org]

We've been cooking 🧑‍🍳

[Privacyx @Privacyx_org]

🔒 PXP-201 defines the foundation for interoperable encryption

PXP-201 establishes a clear, portable encryption envelope designed to make privacy composable across systems.

From here, the focus is on strengthening and extending the standard through:
• policy-based access mechanisms
• optional on-chain registry interfaces
• hardened profiles, audits, and long-term stability guarantees

The goal isn’t to invent new cryptography.
It’s to standardize how encryption is described, ensure it remains auditable, and enable developers to build without reinventing fragile patterns.

PXP-201 sets the groundwork for durable, interoperable privacy infrastructure.

[Privacyx @Privacyx_org]

⚡️ PXP-201 ships with a production-ready SDK

Alongside the standard, we released a reference SDK: 📦 @privacyx/pxp201

Designed as a clean, developer entry point, it provides:
• raw payload encryption
• envelope construction and validation
• secp256k1-based key wrapping (WK1)
• deterministic test vectors
• zero backend assumptions

No UI.
No storage.
No chain coupling.
Just cryptography, envelopes, and correctness.

This makes it suitable as:
• a reference implementation
• a building block for applications
• a foundation for future privacy tooling

🔗 npm: https://t.co/z2nd2EqyvX

[Privacyx @Privacyx_org]

A standard without test vectors is not a standard.

PXP-201 ships with reproducible cryptographic test vectors.

Why this matters:
- Anyone can independently reimplement PXP-201
- Outputs can be verified byte-for-byte
- Ambiguity is eliminated

Included vectors:
1⃣ RAW encryption
AES-256-GCM with fixed DEK + nonce
2⃣ WK1 wrapping
Deterministic secp256k1 ECIES + HKDF + AES-GCM

The reference SDK exposes deterministic options only for test vectors, never for production use.

This allows:
- cross-language implementations
- audits
- long-term compatibility

You can run them yourself:
- npm run build
- npm run vectors

This is boring infrastructure work, and that’s exactly the point.

[Privacyx @Privacyx_org]

@BoyNamedOracle Encrypt everything

[Privacyx @Privacyx_org]

Privacy primitives
▓▓▓▓▓▓▓▓░░ 80%
Identity & access
▓▓▓▓▓▓▓░░░ 65%

Encryption layer
▓▓▓▓▓▓▓▓▓░ 90%
Building the trust layer… 🔄

[Privacyx @Privacyx_org]

@BoyNamedOracle Never stop building

[Privacyx @Privacyx_org]

🔑 How PXP-201 shares encrypted data without sharing secrets?

PXP-201 introduces WK1, its first access mechanism, designed to be wallet-native, auditable, and easy to reason about.

WK1 is built on well-established primitives:
• secp256k1 ECDH
• HKDF-SHA256
• AES-256-GCM

High-level flow
1⃣The payload is encrypted with a random 32-byte data encryption key (DEK).
2⃣For each recipient:
• an ephemeral keypair is generated
• a shared secret is derived via ECDH
• the DEK is wrapped using AES-GCM
3⃣Each recipient receives their own wrapped key, independently.

Key properties
• forward secrecy per recipient
• no shared secrets between recipients
• no on-chain exposure of encryption keys
• fully compatible with existing wallet keys

WK1 prioritizes clarity, auditability, and reproducibility.

This is access control as cryptographic infrastructure, not a black box.

[Privacyx @Privacyx_org]

@abtech_xyz 🫡

[Privacyx @Privacyx_org]

Built to last 🐧

[Privacyx @Privacyx_org]

@GeckoTerminal Stay private for the weekend

[Privacyx @Privacyx_org]

@SecretNetwork Encryption is the way