Blog — Oct 12, 2026

Encrypted Mempool, Now on Aptos Mainnet


module aptos::a_new_era {

    /// Built for the next billion users.
    /// Onboard the world, one transaction at a time.
    public fun onboard_next_billion(): bool {
        ...
        return true;
    }

    /// Rethink value. Rebuild trust. Rewrite the rules.
    /// A new era of Aptos starts here.
    public fun enable_new_era(): bool {
        ...
        return true;
    }

    /// What’s next moves here.
    /// No hype. Just real progress.
    public fun launch_next_phase(): bool {
        ...
        return true;
    }
}

module aptos::doers {

    /// You build fast. Aptos keeps up.
    /// No downtime. No forks. Just forward momentum.
    public fun deploy_with_speed(): bool {
        ...
        return true;
    }

    /// Get help, not hype.
    /// Grants, tools, and support for real builders.
    public fun access_builder_support(): bool {
        ...
        return true;
    }

    /// Tools that work. Docs you can trust.
    /// Build with clarity and confidence.
    public fun use_production_tooling(): bool {
        ...
        return true;
    }

    /// Push to mainnet. Trust the infrastructure.
    /// Aptos is made for developers who ship.
    public fun push_to_mainnet(): bool {
        ...
        return true;
    }
}

module aptos::quietly_excellent {

    /// Quiet execution. Reliable outcomes.
    /// Aptos stays out of the way, so you can move forward.
    public fun verify_infrastructure_integrity(): bool {
        ...
        return true;
    }

    /// Break ground. Not trust.
    /// Built-in performance you can validate.
    public fun ensure_audit_readiness(): bool {
        ...
        return true;
    }

    /// Built to work. Designed to last.
    /// Engineered for stability, not spectacle.
    public fun maintain_network_stability(): bool {
        ...
        return true;
    }
}

module aptos::performance_first {

    /// Sub-second finality. Scales to millions of users.
    /// Designed for performance at any load.
    public fun handle_high_throughput(): bool {
        ...
        return true;
    }

    /// Built for scale. Maintains performance under pressure.
    /// Modular beneath. Seamless above.
    public fun scale_modularly(): bool {
        ...
        return true;
    }

    /// Upgrade without disruption.
    /// Keep building, even while evolving.
    public fun upgrade_without_downtime(): bool {
        ...
        return true;
    }
}

module aptos::ecosystem_energy {

    /// Move what matters, together.
    /// A growing network of builders and believers.
    public fun grow_with_ecosystem(): bool {
        ...
        return true;
    }

    /// Real support. Real partners. Shared momentum.
    /// An ecosystem that grows with you.
    public fun launch_with_partners(): bool {
        ...
        return true;
    }

    /// Cross-chain. Cross-border. Cross-culture.
    /// Connect across Web3, securely and simply.
    public fun connect_across_networks(): bool {
        ...
        return true;
    }
}

There are several ways to shield a transaction before it executes on a public blockchain. Until now, every one of them has meant trusting someone new: a private builder, a hardware enclave, or an external committee.

Encrypted mempool is now live on Aptos mainnet, the first protocol-native implementation that operates under the same trust assumption as the chain itself. This means no additional trust. The validators who order transactions are the same validators who hold the decryption shares. Encryption is opt-in per transaction, and transaction data is recorded on-chain once the block is finalized. The feature is specified in AIP-144

How it works

When you opt in to use encrypted mempool, your address and the fee you're paying stay visible. The contents of your transaction are not.

A user encrypts the transaction payload on the client side, using an encryption key that the validator set jointly generates each epoch. The transaction enters the mempool encrypted. The block leader proposes an ordering while blind to the transaction's payload, the function being called and its arguments. After consensus finalizes the block, validators collectively reconstruct the decrypted transactions, and the transactions execute.

No single validator can decrypt a pending transaction, and neither can any subset of validators below the chain's two-thirds honest-stake threshold. Decryption requires the same stake-weighted majority that produces every block on Aptos, the same trust assumption you already accept by using the chain.

Reaching production-scale efficiency required new cryptography: a batched threshold encryption scheme that decrypts an entire block with constant-size communication per validator, regardless of batch size. The scheme adds roughly 20ms of latency overhead per block in 50-node benchmarks against the production AptosBFT implementation. Aptos blocks finalize in under a second, so the additional overhead is a small fraction of the total. The full construction is described in a paper currently under submission to ACM CCS.

The implementation has undergone independent security review by ZKSecurity .

The trust spectrum

Every production approach to MEV (maximal extractable value) protection answers a single question: which party can read your transaction before it executes?

Approach	Trust Required
Trusted builders and private RPCs (Flashbots Protect, Polygon Private Mempool)	The builder or RPC operator, who sees full transactions in plaintext
TEE-based private execution (NEAR Confidential Intents)	The hardware enclave and the permissioned validator set operating it
External threshold committees (Gnosis Chain / Shutter)	A keyper committee, separate from the chain's own validators
Protocol-native encryption (Aptos)	The chain's validator set, the same set already trusted for consensus

Each of the first three approaches introduces a new party. Flashbots Protect and Polygon route to trusted builders who still see transactions in plaintext. NEAR routes through a TEE-secured shard whose confidentiality depends on enclave integrity. Recent academic work has demonstrated practical extraction attacks against current-generation TEEs at hardware cost under $1,000 ( WireTap and TEE.fail , both ACM CCS 2025). Gnosis Chain integrates Shutter via an external keyper committee, separate from the chain's validator set and operating as a bolt-on rather than in-protocol.

In Aptos, batched threshold encryption is integrated directly into AptosBFT. Every other approach requires you to trust someone new. The Aptos approach requires you to trust only who you were already trusting.

Using it

When you send a transaction on any major chain today, anyone watching the network can see the details before it executes, the function you're calling, the assets and amounts involved, and the contracts you're interacting with. Bots use that visibility to trade against you or copy your strategy. Encrypted mempool changes this: your transaction is encrypted on your device before it's sent, ordered while still encrypted, and decrypted only after the block is final.

Encryption is opt-in per transaction. Petra is the first wallet to surface encryption directly in the signing flow, letting users encrypt any pending transaction with a single option at signature. Decibel , a perpetual futures exchange built on Aptos, will use encrypted mempool to keep orders private until they execute.

The Aptos TypeScript SDK (v7.0.0 and later) fetches the current epoch encryption key, encrypts the payload on the client side, and submits it encrypted. Existing Move smart contracts require no changes.

The first version of the system encrypts the transaction payload (the function being called and its arguments). The sender account and gas-fee fields remain visible at submission, and the chain remains auditable. See the Aptos developer documentation for SDK integration.

Experiment.
Launch.
Scale.

Get Started

public fun ignite_chain_reaction(): bool {
    // Spark innovation
    // Fuel momentum
    // Chain it with Aptos
    return true;
}


public fun deploy_with_confidence(): bool {
    // Test it
    // Ship it
    // Trust Aptos to scale it
    return true;
}


public fun empower_creators_on_aptos(): bool {
    // Tools for builders
    // Freedom for creators
    // Power by Aptos
    return true;
}


public fun redefine_possibilities(): bool {
    // Break limits
    // Build freely
    // Launch globally on Aptos
    return true;
}


public fun grow_without_limits(): bool {
    // No ceilings
    // No bottlenecks
    // Just Aptos performance
    return true;
}


public fun connect_across_chains(): bool {
    // Interoperability
    // Security
    // Aptos at the core
    return true;
}


public fun code_scale_repeat(): bool {
    // Code smart
    // Scale fast
    // Repeat with Aptos
    return true;
}


public fun onboard_the_next_billion(): bool {
    // Real users
    // Real speed
    // Onboard the world with Aptos
    return true;
}


public fun ignite_chain_reaction(): bool {
    // Spark innovation
    // Fuel momentum
    // Chain it with Aptos
    return true;
}


public fun deploy_with_confidence(): bool {
    // Test it
    // Ship it
    // Trust Aptos to scale it
    return true;
}


public fun empower_creators_on_aptos(): bool {
    // Tools for builders
    // Freedom for creators
    // Power by Aptos
    return true;
}


public fun redefine_possibilities(): bool {
    // Break limits
    // Build freely
    // Launch globally on Aptos
    return true;
}


public fun grow_without_limits(): bool {
    // No ceilings
    // No bottlenecks
    // Just Aptos performance
    return true;
}


public fun connect_across_chains(): bool {
    // Interoperability
    // Security
    // Aptos at the core
    return true;
}

public fun ignite_chain_reaction(): bool {
    // Spark innovation
    // Fuel momentum
    // Chain it with Aptos
    return true;
}


public fun deploy_with_confidence(): bool {
    // Test it
    // Ship it
    // Trust Aptos to scale it
    return true;
}


public fun empower_creators_on_aptos(): bool {
    // Tools for builders
    // Freedom for creators
    // Power by Aptos
    return true;
}

public fun ignite_chain_reaction(): bool {
    // Spark innovation
    // Fuel momentum
    // Chain it with Aptos
    return true;
}


public fun deploy_with_confidence(): bool {
    // Test it
    // Ship it
    // Trust Aptos to scale it
    return true;
}


public fun empower_creators_on_aptos(): bool {
    // Tools for builders
    // Freedom for creators
    // Power by Aptos
    return true;
}


public fun redefine_possibilities(): bool {
    // Break limits
    // Build freely
    // Launch globally on Aptos
    return true;
}


public fun grow_without_limits(): bool {
    // No ceilings
    // No bottlenecks
    // Just Aptos performance
    return true;
}


public fun connect_across_chains(): bool {
    // Interoperability
    // Security
    // Aptos at the core
    return true;
}


public fun code_scale_repeat(): bool {
    // Code smart
    // Scale fast
    // Repeat with Aptos
    return true;
}


public fun onboard_the_next_billion(): bool {
    // Real users
    // Real speed
    // Onboard the world with Aptos
    return true;
}


public fun ignite_chain_reaction(): bool {
    // Spark innovation
    // Fuel momentum
    // Chain it with Aptos
    return true;
}


public fun deploy_with_confidence(): bool {
    // Test it
    // Ship it
    // Trust Aptos to scale it
    return true;
}


public fun empower_creators_on_aptos(): bool {
    // Tools for builders
    // Freedom for creators
    // Power by Aptos
    return true;
}


public fun redefine_possibilities(): bool {
    // Break limits
    // Build freely
    // Launch globally on Aptos
    return true;
}


public fun grow_without_limits(): bool {
    // No ceilings
    // No bottlenecks
    // Just Aptos performance
    return true;
}


public fun connect_across_chains(): bool {
    // Interoperability
    // Security
    // Aptos at the core
    return true;
}

Encrypted Mempool, Now on Aptos Mainnet

How it works

The trust spectrum

Using it

Related Articles.

Aptos: The Full Stack for Markets and Machines

Tria Brings 500,000 Users to Aptos. Now With Decibel Perpetuals.

Archax Integrates with Aptos to Bring Over 100 Tokenized Securities Onchain

When Infra Meets Capital: What APT Futures Signal

Shelby Early Access is Open on Aptos Testnet

Confidential APT: Designing Privacy Features on Aptos

The Road to Mainnet: Decibel and the Future of Perpetuals on Aptos

PACT Enters Its Next Chapter

Experiment.
Launch.
Scale.

Encrypted Mempool, Now on Aptos Mainnet

How it works

The trust spectrum

Using it

Related Articles.

Aptos: The Full Stack for Markets and Machines

Tria Brings 500,000 Users to Aptos. Now With Decibel Perpetuals.

Archax Integrates with Aptos to Bring Over 100 Tokenized Securities Onchain

When Infra Meets Capital: What APT Futures Signal

Shelby Early Access is Open on Aptos Testnet

Confidential APT: Designing Privacy Features on Aptos

The Road to Mainnet: Decibel and the Future of Perpetuals on Aptos

PACT Enters Its Next Chapter

Experiment. Launch. Scale.

Experiment.
Launch.
Scale.