Privacy is finally moving mainstream.
The rise of privacy-preserving networks like Zcash and Monero in late 2025 signals something important: enterprises are entering the arena, and adoption is accelerating. But to bring privacy to users and organisations in a scalable way, the ecosystem needs infrastructure that is both decentralized and private by design.
That’s where Aztec comes in — a privacy-first, decentralized Ethereum Layer 2 built for real-world use cases. Aztec enables private transactions natively, allowing individuals and organisations to transact without exposing balances or activity publicly.
As the network launches its token and prepares for public participation, users can now stake AZTEC with P2P.org to help secure the protocol.
Once the public sale has concluded, you’ll be able to stake your newly acquired AZTEC tokens.
To begin:

Why Delegate?
Solo staking increases decentralization, and Aztec benefits from a broad validator set.
But if you don’t want to manage hardware, uptime, or operational risk, P2P.org provides the geographic and data-center redundancy required for secure private networks.
Click Choose Provider → Select P2P.org from the list → Proceed to stake.

Staking on Aztec takes inspiration from Ethereum’s model.
When delegating, your stake is organized into fixed 200,000 AZTEC batches — analogous to 32 ETH validator units on Ethereum.
Example:
If you delegate 500,000 AZTEC:
This is expected behavior — and important for understanding rewards and activation.
Aztec includes a slashing mechanism to penalize misbehaving sequencers. Unlike some networks, slashing only affects the specific sequencer that misbehaved, not your entire delegated balance.
Continuing the earlier example:
This design encourages healthy validator performance and strong operational setups.
To support delegators, both P2P.org and the broader Aztec community will deploy monitoring tools shortly after mainnet launch. These will help users track:
Our infrastructure is distributed geographically across top-tier data centers, ensuring strong reliability for a privacy-sensitive chain like Aztec.
Staking AZTEC helps secure one of the first fully private, decentralized L2 networks. Whether you choose to solo stake or delegate, you are contributing to a critical new layer of Ethereum infrastructure.
For users who want security, resilience, and zero-maintenance staking, P2P.org is ready to support your participation from day one.
If Aztec is part of your strategy, we’ll help you run it at institutional standards.
<h2 id="at-a-glance"><strong>At a Glance:</strong></h2><ul><li>PeerDAS (Peer Data Availability Sampling) launches with Fusaka in on December 3, 2025.</li><li>Dramatically reduces bandwidth requirements for Ethereum validators.</li><li>Enables cheaper, more scalable Layer 2 operations.</li><li><a href="https://p2p.org/?ref=p2p.org" rel="noopener noreferrer nofollow">P2P.org</a>'s infrastructure positioned to maximize PeerDAS benefits for institutional clients.</li></ul><p>PeerDAS is the core of the Fusaka upgrade. It’s the piece that actually shifts Ethereum’s capacity and changes the economics of data availability for rollups. While the concept is technical, the impact is practical: more room for L2s, more responsibility for node operators, and a more scalable Ethereum base layer.</p><p>Today we’re focusing specifically on PeerDAS: what it changes and what it means for the teams building on top of Ethereum — including P2P.org’s validator and node infrastructure.</p><h2 id="why-peerdas-exists"><strong>Why PeerDAS Exists</strong></h2><p>Rollups publish compressed transaction data to Ethereum in the form of “blobs.”Since Dencun, this has been the cheapest and most scalable way to anchor L2 activity on-chain.</p><p>The bottleneck is how Ethereum verifies that data is available.Today, every node must download every blob in full. With blob throughput capped at 6 blobs per slot, the system simply cannot scale alongside growing L2 usage.</p><p>PeerDAS replaces this model with something lighter, safer, and more scalable.</p><figure class="kg-card kg-image-card"><img src="https://p2p.org/economy/content/images/2025/12/data-src-image-64ebfdd7-a14b-462c-8b0f-288a12d8b873.png" class="kg-image" alt="" loading="lazy" width="1600" height="580" srcset="https://p2p.org/economy/content/images/size/w600/2025/12/data-src-image-64ebfdd7-a14b-462c-8b0f-288a12d8b873.png 600w, https://p2p.org/economy/content/images/size/w1000/2025/12/data-src-image-64ebfdd7-a14b-462c-8b0f-288a12d8b873.png 1000w, https://p2p.org/economy/content/images/2025/12/data-src-image-64ebfdd7-a14b-462c-8b0f-288a12d8b873.png 1600w" sizes="(min-width: 720px) 720px"></figure><p>Source: <a href="https://dune.com/hildobby/blobs?ref=p2p.org"><u>https://dune.com/hildobby/blobs</u></a> </p><h2 id="how-peerdas-actually-works"><strong>How PeerDAS Actually Works</strong></h2><p>Instead of treating blob data as a single chunk that every node must download, PeerDAS breaks each blob into many independent pieces (“columns”). Each node downloads only a fraction of the blob. Other nodes download the remaining pieces.</p><p>Because these pieces are mathematically linked, sampling a subset with enough diversity gives the same confidence as downloading the whole blob.</p><p>This is a shift from full replication to distributed verification.</p><figure class="kg-card kg-image-card"><img src="https://p2p.org/economy/content/images/2025/12/data-src-image-518d4f69-f653-4847-96b4-e31e83629c9d.png" class="kg-image" alt="" loading="lazy" width="1600" height="900" srcset="https://p2p.org/economy/content/images/size/w600/2025/12/data-src-image-518d4f69-f653-4847-96b4-e31e83629c9d.png 600w, https://p2p.org/economy/content/images/size/w1000/2025/12/data-src-image-518d4f69-f653-4847-96b4-e31e83629c9d.png 1000w, https://p2p.org/economy/content/images/2025/12/data-src-image-518d4f69-f653-4847-96b4-e31e83629c9d.png 1600w" sizes="(min-width: 720px) 720px"></figure><h2 id="what-this-enables-for-rollups"><strong>What This Enables for Rollups</strong></h2><p>PeerDAS doesn’t just reduce bandwidth; it expands Ethereum’s capacity.</p><h3 id="1-up-to-8x-more-blob-throughput"><strong>1. Up to 8x more blob throughput</strong></h3><p>The network can safely increase blob limits from 6 → up to 48 blobs per slot over time. More data availability means rollups can post more frequently, at lower and more stable costs.</p><h3 id="2-lower-fees-and-fewer-congestion-shocks"><strong>2. Lower fees and fewer congestion shocks</strong></h3><p>Rollups no longer compete for a narrow DA window, reducing situations where blob fees suddenly spike.</p><h3 id="3-room-for-more-complex-l2-applications"><strong>3. Room for more complex L2 applications</strong></h3><p>Higher bandwidth supports applications that generate more data — social networks, gaming activity, high-frequency trading, and more sophisticated L2 designs.</p><p>Rollups get the most direct benefit from PeerDAS. Their operating environment becomes cheaper and less volatile.</p><h2 id="what-peerdas-means-for-validators"><strong>What PeerDAS Means for Validators</strong></h2><p>This is where the upgrade becomes more nuanced.</p><p>PeerDAS reduces per-node download requirements, but it increases node responsibilities:</p><h3 id="1-stricter-bandwidth-and-peering-expectations"><strong>1. Stricter bandwidth and peering expectations</strong></h3><p>Nodes must reliably fetch, store, and serve their assigned columns. Poor performance impacts peer scoring and can reduce overall network connectivity.</p><h3 id="2-higher-operational-load-under-increased-throughput"><strong>2. Higher operational load under increased throughput</strong></h3><p>More blobs overall still means more data moving through the network. Even with sampling, operators will see more traffic than before.</p><h3 id="3-supernode-dynamics"><strong>3. Supernode dynamics</strong></h3><p>Operators running very large key counts (>3,872 validators per node) are effectively pushed into “supernode” territory, which requires storing and serving all blob data.Some operators will choose this voluntarily for reliability and resilience.</p><h2 id="p2porgs-peerdas-readiness"><strong>P2P.org's PeerDAS Readiness</strong></h2><p>Higher DA throughput and larger validator loads mean the infrastructure layer becomes even more important.</p><p>Our technical team has thoroughly tested PeerDAS functionality across Ethereum testnets, validating that our infrastructure handles the sampling mechanisms reliably while maintaining validator performance.</p><p>What PeerDAS changes for us:</p><ul><li>More bandwidth headroom is required per node</li><li>Healthier peer selection and scoring becomes essential</li><li>Validators must maintain consistent performance under increased blob load</li><li>Monitoring and alerting around DA sampling failures becomes part of normal operations</li></ul><p>When Fusaka activates in December 2025, P2P.org's validators will immediately leverage PeerDAS capabilities. Institutional clients will experience seamless transitions to the new data availability model with zero service interruption.</p><p>This preparation reflects P2P.org's broader approach: we don't wait for network upgrades to catch up. We test thoroughly, optimize proactively, and ensure our clients capture every advantage new protocol features offer.</p><h2 id="the-bottom-line"><strong>The Bottom Line</strong></h2><p>For institutional validators, PeerDAS means better operational efficiency without compromising security. For the Ethereum ecosystem, it means Layer 2 solutions can scale to serve millions of users affordably.</p><p>For P2P.org, it reinforces a simple reality: as Ethereum scales, so do the expectations placed on those who secure it.</p><p>And for P2P.org clients, it means their infrastructure partner is positioned to deliver these benefits from day one of the upgrade.</p><p><strong>Questions about how PeerDAS will impact your operations? </strong></p><div class="kg-card kg-button-card kg-align-center"><a href="https://link.p2p.org/bdteam?ref=p2p.org" class="kg-btn kg-btn-accent">Contact our institutional team</a></div>
from p2p validator