Aptos Labs

On Aptos, an address isn't a public key. Every account's address comes from an authentication key: a hash of the public key and signature scheme. The public key isn't revealed onchain until the account first signs a transaction. That authentication key can be rotated. Swap in a new key without changing the address or moving assets, so an exposed key can be retired in place. Signature schemes can be combined too. MultiKey accounts (AIP-55) let one account mix schemes like Ed25519, secp256k1 ECDSA, and passkeys. AIP-137 would add SLH-DSA (FIPS 205), a hash-based post-quantum signature, as an account option if it's approved through governance. Paired with a classical scheme in a MultiKey account, it could run in hybrid mode. Post-quantum security is a full-stack effort. Account signatures are where it starts. Learn more: https://lnkd.in/eJHMxD9U

Confidentiality on Aptos now spans three layers, all live on mainnet: • Identity: Keyless Accounts • Amounts: Confidential APT • Intent: Encrypted Mempool Each targets a different part of what's visible onchain. Each is opt-in. Under the hood: • Keyless Accounts: users create and manage accounts with existing credentials like Google or Apple, verified with zero-knowledge proofs, without publicly tying that identity to an onchain address. • Confidential APT: users can encrypt balances and transfer amounts. Validators check a zero-knowledge proof that a transfer is valid, while balances and amounts stay confidential. Addresses stay public. • Encrypted Mempool: the payload (function called + arguments) is encrypted client-side, ordered while encrypted, and decrypted by validators together only after the block is finalized. Opt-in by design, built for compliant use. Confidential APT is available in Petra Wallet and on Confidential Assets Web. For users who want to use Encrypted Mempool, Petra also offers the ability to encrypt their transactions right at signing. Petra: https://petra.app Confidential Assets Web: https://lnkd.in/gY77jErs Built by Aptos Labs.

Encrypted Mempool is LIVE on Aptos mainnet! Approved through onchain governance and now enabled, it lets users opt in to encryption, one transaction at a time: → The payload (function called + arguments) is encrypted client-side → Block leaders propose ordering without seeing it → Validators decrypt together only after consensus finalizes the block In practice: → Institutional flow can reach the chain without revealing intent before execution → Traders can encrypt the orders they choose, lowering MEV risk on those orders → Agents can submit trades with inputs encrypted until execution → Petra Wallet offers users the ability to encrypt their transactions right at signing → Decibel plans to let users keep orders encrypted until they execute → Developers: TypeScript SDK v7.0.0+ handles encryption, and existing Move contracts need no changes Under the hood: Decryption takes the same two-thirds stake-weighted majority that already produces every block on Aptos. New batched threshold encryption decrypts a full block with constant-size communication per validator, keeping added latency minimal. The implementation was independently reviewed by zkSecurity. How we built it: https://lnkd.in/g36EiT6Q

The real test of a stack is what gets built on it. Decibel's order book and matching run in Move. Shelby uses Aptos as its coordination and settlement layer. Different problems, same foundation. Avery Ching on DevNTell. Watch the full clip 👇

MonoMove. Aptos' rebuilt execution engine, running up to 55x faster. Coming soon, pending a governance vote. Learn more: https://lnkd.in/p/eDDZTXu2

Earlier this year, Aptos Labs and Aptos Foundation committed $50M+ across the Aptos stack. Our side of that: building the products, the research, and the protocol infrastructure institutions and agents need onchain. Heads down on all three.

Private Beta is deliberately a co-build. Each Shelby engagement starts with the workload, and what repeats across customers shapes what gets built next. First up: enterprise AI, spatial intelligence, and distributed rendering. New workloads are already entering onboarding. Stay tuned! Shelby is co-developed by Aptos Labs and Jump Crypto. Meet the first cohort: https://lnkd.in/gQHvQZ3D

Big milestone for Shelby: Private Beta is live, with real customer workloads now running in production environments. The opportunity is clear: give teams more freedom to choose the right compute without the data layer becoming the constraint. Now we get to see that play out with customers.

Reminder: Aptos Testnet resets to a fresh genesis tomorrow, Oct. 7. All Testnet state will be cleared: deployed contracts, accounts, balances, and history. Before Oct. 7: → Have deployment scripts ready → Indexer and analytics teams: plan for pre-reset history being cleared After the reset: → Redeploy contracts and recreate test accounts → Re-fund test accounts from the faucet → Node operators: re-sync from the new genesis → Update any clients that pin the genesis hash Need realistic test data? Forklift can fork live Mainnet state locally, so your tests don't depend on long-lived Testnet state. Mainnet and Devnet are not affected. AIP-147: https://lnkd.in/e-D8ySKm

Introducing MonoMove: the rebuilt Aptos execution engine and the largest performance upgrade since mainnet. Markets onchain need scale and safety. MonoMove is built for both. The Move code behind every order, loan, and payout executes up to 55x faster. Parallelism is not even switched on yet. The execution engine runs the Move smart contracts behind every transfer, trade, loan, and payment on Aptos. Institutional trading, clearing, and settlement need what today's engines were not built for: sustained throughput at market scale, continuous market data, and asset protections that hold when volume spikes. MonoMove was rebuilt to support that. MonoMove rebuilds the MoveVM and the execution stack around it. Replaying mainnet Decibel transactions, execution speedup over the current Move VM: • Perp collateral withdrawals: up to 55x • Vault request processing: up to 40x • Perp market requests: up to 38x • Order placement: up to 22x MonoMove unlocks low-latency Move execution across the network. It also already improves end-to-end blockchain throughput by up to 11x without any additional optimizations and without parallelism. How we measured: realistic crypto workloads such as trading, borrowing/lending, and payments, running on both engines against a real database. Execution now has more room for complex applications. MonoMove keeps Move rules on how assets are created, copied, and transferred, and layers redundant checks in the verifier and the VM. Whole classes of bugs are eliminated by construction rather than caught after the fact. Differential testing is expanding alongside it: identical transactions, identical results. Formal verification of critical components is coming as well. Feature completeness is targeted for the end of 2026, with mainnet rollout planned for 2027 pending a governance vote. Performance and safety are advancing together, for the institutions bringing markets onchain. More on MonoMove via TheStreet: https://lnkd.in/e4_xraHj