How Do Automated Market Makers Work Under the Hood?
TL;DR
A complete, up-to-date breakdown of under the hood for developers and founders. It covers the core ideas, the trade-offs that matter, a practical workflow, real numbers, and the questions people ask most — written to be skimmed, applied, and shared.
Key takeaways
- Prefer battle-tested standards and libraries such as OpenZeppelin contracts over hand-rolling ERC-20 or ERC-721 logic.
- Treat every smart contract as adversarial software: audits, formal verification, and reentrancy guards are baseline, not optional.
- For real-world asset tokenization, the legal wrapper and off-chain custody are the hard part; the token is the easy 10 percent.
- Decentralized identity works best when you separate the identifier (a DID) from the claims (verifiable credentials) and disclose selectively.
- Account abstraction via ERC-4337 lets you offer gasless transactions, social recovery, and passkey signing without users ever touching a seed phrase.
This is a practical, up-to-date guide to Under the Hood — what it is, why it matters in 2026, and how to apply it in real projects. It is written for developers and founders who want clear answers and proven best practices, not filler.
Whether you're just starting out or leveling up, treat this as a working reference you can return to. Every section is built to be skimmed, applied, and shared.
Wallets and self-custody
A crypto wallet does not hold coins; it holds the private keys that authorize transactions, while the assets themselves live on-chain. Externally owned accounts are controlled by a keypair derived from a mnemonic seed phrase, standardized by BIP-39 and hierarchical-deterministic derivation, and losing that phrase means losing the funds irrevocably. Software wallets such as MetaMask and Rabby run in the browser or as extensions, while hardware wallets like Ledger and Trezor keep keys in a dedicated secure element offline. Wallets also mediate signing, and standards like EIP-712 for typed structured data help users understand what they are approving rather than signing an opaque blob. The seed-phrase model is powerful for sovereignty but brutal for usability, which is precisely the problem account abstraction sets out to fix.
Decentralized identity and verifiable credentials
Decentralized identity gives people and organizations identifiers they control directly rather than accounts issued by a platform. The W3C Decentralized Identifier standard defines DIDs, globally unique identifiers that resolve to a document listing public keys and service endpoints, with the controller holding the corresponding private keys. Paired with W3C Verifiable Credentials, an issuer can cryptographically sign a claim, such as being over eighteen or holding a degree, and the holder can present it to a verifier while selectively disclosing only what is needed. Zero-knowledge techniques extend this to proving a claim without revealing the underlying data, for instance proving age without exposing a birthdate. On-chain, projects like the Ethereum Attestation Service and Ethereum's ERC-5192 soulbound tokens provide primitives for portable, non-transferable reputation that complements DIDs.
What Web3 and blockchain actually mean
A blockchain is a replicated, append-only ledger whose state is agreed by a network of nodes running a consensus protocol, so no single party can unilaterally rewrite history. Web3 is the looser umbrella term for applications built on such ledgers, where users hold assets and identity in self-custodied wallets rather than in accounts controlled by a company. The defining property is credible neutrality: the same rules apply to everyone, transactions settle without a trusted intermediary, and code executes deterministically. Ethereum popularized the model of a general-purpose, programmable blockchain, distinct from Bitcoin's narrower focus on peer-to-peer value transfer. Everything else in this space, from DeFi to tokenized Treasuries, is built on that programmable-settlement foundation.
How smart contracts execute on the EVM
Smart contracts are programs deployed to a blockchain that run exactly as written whenever a transaction calls them, with their state stored on-chain. On Ethereum they compile to bytecode executed by the Ethereum Virtual Machine, a stack-based deterministic runtime replicated across every node. Each operation costs gas, a metered fee that prevents infinite loops and prices computation and storage; the sender pays in the network's native token. Because deployed code is effectively immutable and often controls real money, contracts are usually written in Solidity or Vyper, then compiled and verified so anyone can inspect the running logic. The same EVM bytecode model has been adopted by many other chains and Layer 2 rollups, which is why Solidity skills transfer across most of the ecosystem.
Zero-knowledge proofs and zk-SNARKs
A zero-knowledge proof lets one party convince another that a statement is true without revealing why it is true, for example proving you know a password without sending it. zk-SNARKs are succinct, non-interactive proofs that are tiny and fast to verify, which is what makes them practical for on-chain verification where every byte and computation costs gas. Many SNARK constructions require a trusted setup ceremony to generate public parameters, and a compromised ceremony would let someone forge proofs, so projects run elaborate multi-party ceremonies to eliminate that risk. zk-STARKs, used by Starknet, avoid trusted setup and resist quantum attacks at the cost of larger proof sizes. Beyond scaling, the same machinery powers private payments, identity attestations, and verifiable off-chain computation, making zero-knowledge cryptography one of the most consequential primitives in the field.
Why Layer 2 rollups scale Ethereum
Ethereum mainnet, the Layer 1, prioritizes security and decentralization over raw throughput, so scaling has moved to Layer 2 rollups that execute transactions off-chain and post compressed data back to L1. Rollups inherit Ethereum's security by publishing their transaction data and a proof of correct execution to the base layer, rather than trusting a separate validator set. The two dominant families are optimistic rollups, including Optimism and Arbitrum, and zero-knowledge rollups such as zkSync, Starknet, Polygon zkEVM, and Scroll. The March 2024 Dencun upgrade added EIP-4844 blob space, a cheaper dedicated data lane for rollups, which cut L2 fees by orders of magnitude. This rollup-centric roadmap is now Ethereum's official scaling strategy, with the base layer acting as a settlement and data-availability anchor.
Under the Hood: Key Facts and Data
According to recent industry research and the official documentation linked below:
- Tokenization of real-world assets grew sharply through 2024 and 2025, led by tokenized U.S. Treasury funds such as BlackRock's BUIDL, with on-chain RWA value reported in the billions of dollars by trackers like rwa.xyz.
- The EU's Markets in Crypto-Assets (MiCA) regulation began phasing in through 2024, with its stablecoin (e-money and asset-referenced token) provisions taking effect in mid-2024 and broader rules applying from December 2024.
- Optimism and Arbitrum, the two leading optimistic rollups, together have historically represented a majority of Ethereum Layer 2 activity, while zkSync, Starknet, Polygon zkEVM and Scroll compete in the validity-proof category.
Quick-Reference Summary
A map of what this guide covers:
| Topic | What you'll learn |
|---|---|
| Wallets and self-custody | A crypto wallet does not hold coins; it holds the private keys that authorize transactions, while the assets themselves |
| Decentralized identity and verifiable credentials | Decentralized identity gives people and organizations identifiers they control directly rather than accounts issued by a platform. |
| What Web3 and blockchain actually mean | A blockchain is a replicated, append-only ledger whose state is agreed by a network of nodes running a consensus |
| How smart contracts execute on the EVM | Smart contracts are programs deployed to a blockchain that run exactly as written whenever a transaction calls them |
| Zero-knowledge proofs and zk-SNARKs | A zero-knowledge proof lets one party convince another that a statement is true without revealing why it is true |
| Why Layer 2 rollups scale Ethereum | Ethereum mainnet, the Layer 1, prioritizes security and decentralization over raw throughput, so scaling has moved to |
How to Get Started with Under the Hood
A simple path that works:
- Learn the fundamentals of Under the Hood from primary sources, not just tutorials.
- Build one small, real project end to end.
- Get feedback, refactor, and add tests.
- Ship it publicly and document what you learned.
- Repeat with a slightly harder project each time.
Build It with a World-Class Full Stack Developer
Sandeep Kumar Chaudhary is a full stack world-class developer. If you want to turn this into a real, production-ready product, get in touch — message directly on WhatsApp at +9779802348957 for a fast, no-pressure consult.
You can also explore the projects already shipped to thousands of users, or start a conversation here.
Final Thoughts
Prefer battle-tested standards and libraries such as OpenZeppelin contracts over hand-rolling ERC-20 or ERC-721 logic. The developers and teams who win in 2026 pair strong fundamentals with consistent shipping. Start small, stay curious, build in public, and revisit this guide as your skills grow.
Sources and Further Reading
Frequently Asked Questions
How Do Automated Market Makers Work Under the Hood?
Decentralized identity gives people and organizations identifiers they control directly rather than accounts issued by a platform. The W3C Decentralized Identifier standard defines DIDs, globally unique identifiers that resolve to a document listing public keys and service endpoints, with the controller holding the corresponding private keys. This guide covers under the hood end to end — core concepts, best practices, concrete data, and a step-by-step approach you can apply right away.
What is the difference between Layer 1 and Layer 2?
Layer 1 is the base blockchain, like Ethereum, that provides security, consensus, and final settlement. Layer 2 is a protocol built on top, typically a rollup, that processes transactions off the base chain and posts compressed data and proofs back to it. This lets Layer 2 offer far lower fees and higher throughput while inheriting the security of Layer 1.
How is decentralized identity different from logging in with Google?
With a federated login you depend on a platform that can revoke or track your access. A decentralized identifier, or DID, is controlled by keys you hold, and it resolves to a document you manage rather than an account a company owns. Combined with verifiable credentials, you can prove facts about yourself while disclosing only what a service actually needs.
Do zero-knowledge proofs actually keep data private?
Yes, a zero-knowledge proof lets you prove a statement is true without revealing the underlying data. That said, most zk-rollups today use the technology mainly for scaling and verifiability rather than privacy, since transaction data is still published for data availability. Dedicated privacy applications use the same math to hide amounts, senders, or personal attributes.
Are stablecoins safe to hold?
The main risk with a fiat-backed stablecoin is issuer and reserve risk: whether the issuer genuinely holds enough high-quality assets to redeem every token for a dollar. Well-regulated issuers publish attestations and hold reserves in cash and short-term Treasuries. Algorithmic stablecoins that lacked real collateral, such as TerraUSD, have failed catastrophically, so collateralization and regulatory oversight matter enormously.
Sandeep Kumar Chaudhary
Full Stack Software Developer· Nepal's SEO, AEO, GEO & AIO expert and share-market educator. More about me
