# Polygon Developer Docs

## Docs

- [Overview](https://docs.polygon.technology/blockchain-rails/index.md): The settlement layer for the Open Money Stack: Polygon Chain for public settlement and Polygon CDK for dedicated, compliance-grade infrastructure.
- [Polygon CDK FAQs](https://docs.polygon.technology/chain-development/cdk/additional-resources/faqs.md): Frequently asked questions about Polygon CDK, covering execution clients, rollup modes, and Agglayer integration.
- [Glossary](https://docs.polygon.technology/chain-development/cdk/additional-resources/glossary.md): Definitions of technical terms used throughout the Polygon CDK documentation.
- [Deployment Modes](https://docs.polygon.technology/chain-development/cdk/cdk-opgeth/architecture.md): Component reference for the three CDK deployment modes: sovereign, validium, and zkrollup.
- [Devnet Deployment Guide](https://docs.polygon.technology/chain-development/cdk/cdk-opgeth/devnet-deployment-guide.md): How to deploy a production-like Pessimistic Proof (cdk-opgeth-sovereign) devnet.
- [Going to Production](https://docs.polygon.technology/chain-development/cdk/cdk-opgeth/going-to-production.md): Deploy a CDK chain to testnet or mainnet with support from implementation providers.
- [Quickstart](https://docs.polygon.technology/chain-development/cdk/cdk-opgeth/local-guide.md): How to deploy a local cdk-opgeth testnet using Kurtosis, including L1, L2, Agglayer, and OP Stack components.
- [Why Choose CDK?](https://docs.polygon.technology/chain-development/cdk/get-started/benefits.md): Key benefits of Polygon CDK, including EVM compatibility, Agglayer integration, rollup modes, and implementation support.
- [What is CDK?](https://docs.polygon.technology/chain-development/cdk/get-started/overview.md): Enterprise-grade toolkit for building custom Ethereum L2 chains. Agglayer interoperability is built in by default.
- [Overview](https://docs.polygon.technology/chain-development/cdk/index.md): Deploy your own custom blockchain with built-in Agglayer interoperability. Enterprise-grade rollup infrastructure for payments, compliance, and dedicated chain rails.
- [Polygon Developer Docs](https://docs.polygon.technology/index.md): The only open, full-stack payments infrastructure for global money movement.
- [Architecture](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/architecture.md): AggKit's three-tier architecture: chain domain, synchronization components, and the Agglayer ecosystem, with certificate submission and GER propagation flows
- [AggchainProofGen](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/aggchain-proof-gen.md): How AggchainProofGen generates state transition proofs for chains requiring mathematical verification of internal operations beyond ECDSA signature authorization
- [AggOracle](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/aggoracle.md): How AggOracle propagates Global Exit Root updates from Ethereum L1 to L2 chains, and the v0.3.5 committee mode security improvement
- [AggSender](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/aggsender.md): How AggSender packages L2 state transitions into cryptographically signed certificates and submits them to Agglayer for Pessimistic Proof generation
- [BridgeSync](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/bridge-sync.md): How BridgeSync monitors and indexes bridge events from L1 and L2 networks, and how it provides data to AggSender and Bridge Service
- [Components Overview](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/index.md): The 7 AggKit components, their roles, dependencies, and which combinations are appropriate for different deployment scenarios
- [L1InfoTreeSync](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/l1infotree-sync.md): How L1InfoTreeSync monitors Ethereum L1 and maintains the L1 Info Tree and Rollup Exit Tree for proof generation and certificate building
- [L2GERSync](https://docs.polygon.technology/interoperability/agglayer/core-concepts/aggkit/components/l2ger-sync.md): How L2GERSync indexes Global Exit Root updates on the L2 side and provides fast local GER state access for claim verification and Bridge Service APIs
- [Architecture](https://docs.polygon.technology/interoperability/agglayer/core-concepts/architecture.md): Agglayer's technical architecture: the Agglayer node, Pessimistic Proof, Unified Bridge, and State Transition Proof and how they coordinate
- [Architecture Overview](https://docs.polygon.technology/interoperability/agglayer/core-concepts/pessimistic-proof/architecture.md): How Pessimistic Proofs are generated and validated, and the financial isolation guarantees they provide
- [Benchmarks](https://docs.polygon.technology/interoperability/agglayer/core-concepts/pessimistic-proof/benchmarks.md): Experimental performance analysis and benchmarks across different zkVM implementations
- [Data Structures](https://docs.polygon.technology/interoperability/agglayer/core-concepts/pessimistic-proof/data-structures.md): Reference for the Sparse Merkle Trees and data structures used by Pessimistic Proof: Local Balance Tree, Nullifier Tree, Bridge Exits, MultiBatchHeader, and Certificate
- [Proof Generation](https://docs.polygon.technology/interoperability/agglayer/core-concepts/pessimistic-proof/proof-generation.md): The Pessimistic Proof generation pipeline: certificate submission, native Rust validation, zkVM proof generation, and proof verification
- [Aggchain Proof](https://docs.polygon.technology/interoperability/agglayer/core-concepts/state-transition-proof/aggchain-proof.md): Reference for Aggchain Proof: ECDSA and generic validity proof consensus types, data structures, verification steps, and bridge constraint details
- [Architecture Overview](https://docs.polygon.technology/interoperability/agglayer/core-concepts/state-transition-proof/architecture.md): The State Transition Proof dual proof system: Local Chain, AggProver, and Agglayer roles, and how ECDSA and generic consensus types are handled
- [Architecture Overview](https://docs.polygon.technology/interoperability/agglayer/core-concepts/unified-bridge/architecture.md): The Unified Bridge architecture: onchain contracts, off-chain services, data flow, and security properties
- [Asset Bridging](https://docs.polygon.technology/interoperability/agglayer/core-concepts/unified-bridge/asset-bridging.md): How asset bridging works in the Unified Bridge: token type handling, bridgeAsset/claimAsset function signatures, and Merkle proof verification
- [Bridge Components](https://docs.polygon.technology/interoperability/agglayer/core-concepts/unified-bridge/bridge-components.md): Reference for the Unified Bridge's onchain contracts, off-chain services, and APIs
- [Data Structures](https://docs.polygon.technology/interoperability/agglayer/core-concepts/unified-bridge/data-structures.md): Reference for the Unified Bridge Merkle tree hierarchy: Local Exit Root, Rollup Exit Root, Mainnet Exit Root, Global Exit Root, and Global Index
- [Message Bridging](https://docs.polygon.technology/interoperability/agglayer/core-concepts/unified-bridge/message-bridging.md): How message bridging works in the Unified Bridge: bridgeMessage/claimMessage function signatures, the IBridgeMessageReceiver interface, and execution flows
- [What is Agglayer?](https://docs.polygon.technology/interoperability/agglayer/core-concepts/what-is-agglayer.md): CDK's interoperability layer: how it addresses blockchain fragmentation and what it enables for CDK chains
- [Get Started](https://docs.polygon.technology/interoperability/agglayer/get-started/index.md): Build cross-chain applications on AggLayer-connected CDK chains.
- [Overview](https://docs.polygon.technology/interoperability/agglayer/index.md): Agglayer connects chains with shared liquidity, atomic cross-chain transactions, and cryptographic security.
- [API Reference](https://docs.polygon.technology/interoperability/agglayer/integrations/aggkit-bridge-service/api-reference.md): REST API documentation for the AggKit Bridge Service: endpoints, parameters, and response formats.
- [AggKit Bridge Service](https://docs.polygon.technology/interoperability/agglayer/integrations/aggkit-bridge-service/index.md): REST API for bridge data, transaction status, and proof generation without running AggKit infrastructure.
- [API Reference](https://docs.polygon.technology/interoperability/agglayer/integrations/bridge-hub/api-reference.md): Bridge Hub REST API: endpoints, parameters, and response formats for querying bridge transactions.
- [Architecture](https://docs.polygon.technology/interoperability/agglayer/integrations/bridge-hub/architecture.md): Bridge Hub system architecture: consumer internals, multi-network deployment, and database design.
- [Auto-Claim Service](https://docs.polygon.technology/interoperability/agglayer/integrations/bridge-hub/auto-claim.md): Automated bridge transaction claiming: configuration, deployment, and security.
- [Deployment](https://docs.polygon.technology/interoperability/agglayer/integrations/bridge-hub/deployment.md): Deploy Bridge Hub to production: Docker, Kubernetes, configuration, and troubleshooting.
- [Bridge Hub](https://docs.polygon.technology/interoperability/agglayer/integrations/bridge-hub/index.md): Multi-chain bridge transaction indexing, API, and auto-claim system for AggLayer integrators.
- [Integrations](https://docs.polygon.technology/interoperability/agglayer/integrations/index.md): Tools and APIs for integrating with AggLayer bridge infrastructure.
- [Supported Chains](https://docs.polygon.technology/interoperability/agglayer/supported-chains.md): Chains connected to AggLayer: chain IDs, rollup IDs, RPC endpoints, block explorers, and gas tokens.
- [What is the Open Money Stack?](https://docs.polygon.technology/oms/overview.md): One open stack for global money movement: fiat access, wallets, compliance, routing, and settlement in one vertically integrated, open platform.
- [Start Building](https://docs.polygon.technology/oms/quickstart.md): Choose your path into the Open Money Stack based on what you're building.
- [Use Cases](https://docs.polygon.technology/oms/use-cases.md): How financial institutions are using the Open Money Stack to move money globally.
- [ERC-8004 on Polygon](https://docs.polygon.technology/payment-services/agentic-payments/agent-integration/erc8004.md): Reference and explanation for ERC-8004: onchain Identity, Reputation, and Validation registries for autonomous agents.
- [Agentic Payments Introduction](https://docs.polygon.technology/payment-services/agentic-payments/agent-integration/intro.md): Conceptual overview of agentic payments and how autonomous agents transact on Polygon.
- [Polygon Agentic CLI](https://docs.polygon.technology/payment-services/agentic-payments/polygon-agent-cli.md): A single CLI toolkit for AI agents: smart contract wallets, token operations, x402 micropayments, and onchain identity.
- [Mainnet Facilitator Addresses](https://docs.polygon.technology/payment-services/agentic-payments/x402/analytics.md): Reference list of x402 mainnet facilitator addresses for analytics and payment verification.
- [x402 Directory](https://docs.polygon.technology/payment-services/agentic-payments/x402/directory.md): Directory of x402-gated APIs that settle on Polygon.
- [x402 How It Works](https://docs.polygon.technology/payment-services/agentic-payments/x402/guides/how-it-works.md): Conceptual explanation of the x402 protocol: components, payment flow, design goals, and known limitations.
- [x402 Quickstart for Buyers](https://docs.polygon.technology/payment-services/agentic-payments/x402/guides/quickstart-buyers.md): Tutorial: set up an x402 buyer client on Polygon to automatically pay for and access paywalled API endpoints.
- [x402 Quickstart for Sellers](https://docs.polygon.technology/payment-services/agentic-payments/x402/guides/quickstart-sellers.md): Tutorial: protect API endpoints with x402 payment middleware to accept USDC payments on Polygon.
- [Using the Polygon Facilitator](https://docs.polygon.technology/payment-services/agentic-payments/x402/guides/using-polygon-facilitator.md): Reference for the Polygon x402 facilitator: endpoint URLs and signing addresses.
- [Using x402facilitators package](https://docs.polygon.technology/payment-services/agentic-payments/x402/guides/using-x402facilitators.md): How to use the @swader/x402facilitators package to add multi-facilitator routing to x402 middleware.
- [x402 Introduction](https://docs.polygon.technology/payment-services/agentic-payments/x402/intro.md): What x402 is and how Polygon supports it: available networks, facilitators, and where to start.
- [x402 Autopay](https://docs.polygon.technology/payment-services/agentic-payments/x402/tools/autopay.md): How to install and use the AutoPay Chromium extension for x402 micropayments in the browser.
- [x402 CLI](https://docs.polygon.technology/payment-services/agentic-payments/x402/tools/x402-cli.md): Reference for the x402 CLI tool: usage and prerequisites for testing x402-gated API endpoints.
- [Stripe On-ramp Tutorial](https://docs.polygon.technology/payment-services/stablecoins/onramps-stripe.md): Tutorial: use Stripe's Crypto On-ramp API to let users buy USDC on Polygon inside your app.
- [USDC Gateway Integration](https://docs.polygon.technology/payment-services/stablecoins/usdc-gateway-integration.md): How to integrate USDC on Polygon using Circle's Gateway (CCTP) for cross-chain transfers.
- [USDC Native Integration](https://docs.polygon.technology/payment-services/stablecoins/usdc-native-integration.md): How to read balances and transfer native USDC on Polygon PoS using viem.
- [Introduction](https://docs.polygon.technology/pos/architecture/bor/introduction.md): How Bor, Polygon PoS's block production layer, works: proposer and producer selection, spans, sprints, fork resolution, and state synchronization with Ethereum.
- [Network configuration](https://docs.polygon.technology/pos/architecture/bor/network-config.md): Default ports used by Bor and Heimdall nodes for peer connections, RPC, WebSocket, monitoring, and discovery.
- [State sync](https://docs.polygon.technology/pos/architecture/bor/state-sync.md): How state sync works in Polygon PoS, allowing Ethereum contract state to be reflected in Bor through the StateSender and StateReceiver contracts.
- [Authentication](https://docs.polygon.technology/pos/architecture/heimdall_v2/authentication.md): How the Heimdall auth module handles account types, transaction validation, gas fees, AnteHandlers, and keepers.
- [Balance transfers](https://docs.polygon.technology/pos/architecture/heimdall_v2/balance-transfers.md): How the Heimdall bank module handles multi-asset coin transfers, module accounts, supply tracking, send restrictions, and CLI/gRPC/REST query commands.
- [Chain management](https://docs.polygon.technology/pos/architecture/heimdall_v2/chain-management.md): How the Heimdall chainmanager module stores and exposes PoS protocol parameters, including contract addresses, chain IDs, and confirmation block counts.
- [Changes from v1](https://docs.polygon.technology/pos/architecture/heimdall_v2/changes-from-v1.md): Key differences between Heimdall v1 and v2, including encoding changes, the keyring requirement for validator signing, and vote extensions.
- [Checkpoints](https://docs.polygon.technology/pos/architecture/heimdall_v2/checkpoints.md): How Heimdall checkpoints work, from proposal through Ethereum submission and acknowledgment, including the ABCI++ processing flow and message types.
- [Clerk](https://docs.polygon.technology/pos/architecture/heimdall_v2/clerk.md): How the Heimdall clerk module manages state-sync event records from Ethereum, including the EventRecord structure and the validation flow.
- [Governance](https://docs.polygon.technology/pos/architecture/heimdall_v2/governance.md): How the Heimdall governance module works, including proposal submission, voting, deposit handling, and parameter changes.
- [Heimdall Bor module](https://docs.polygon.technology/pos/architecture/heimdall_v2/heimdall-bor-module.md): How the Heimdall bor module manages span intervals, selects block producers for the Bor chain, and coordinates span proposals through the ABCI++ side-transaction flow.
- [Introduction](https://docs.polygon.technology/pos/architecture/heimdall_v2/introduction.md): What Heimdall-v2 is, what it does in the Polygon PoS architecture, and how it differs from the original Heimdall.
- [Milestones](https://docs.polygon.technology/pos/architecture/heimdall_v2/milestones.md): How Heimdall milestones provide deterministic finality on Polygon PoS without waiting for checkpoints, using CometBFT vote extensions and 2/3 majority agreement.
- [Staking](https://docs.polygon.technology/pos/architecture/heimdall_v2/staking.md): How the Heimdall stake module manages validator state, synchronizes Ethereum stake events to Heimdall, and updates the validator set.
- [Topup](https://docs.polygon.technology/pos/architecture/heimdall_v2/topup.md): How the Heimdall topup module manages validator fee balances on Heimdall, including funding methods, bridge processing, and fee withdrawal.
- [Overview](https://docs.polygon.technology/pos/architecture/overview.md): Architectural overview of Polygon PoS from a node perspective, covering the Heimdall-v2 consensus layer and Bor execution layer.
- [Finality](https://docs.polygon.technology/pos/concepts/finality/finality.md): How finality works on Polygon PoS, including the milestone mechanism and the difference between probabilistic and deterministic finality.
- [MATIC](https://docs.polygon.technology/pos/concepts/tokens/matic.md): What MATIC was as the native token of Polygon PoS, and its relationship to the POL token that replaced it.
- [Migrate to POL](https://docs.polygon.technology/pos/concepts/tokens/matic-to-pol.md): How to migrate MATIC tokens to POL, depending on which chain they are currently on.
- [POL](https://docs.polygon.technology/pos/concepts/tokens/pol.md): What POL is, how it works as the native token of Polygon PoS, and how its emission and governance mechanisms are designed.
- [sPOL](https://docs.polygon.technology/pos/concepts/tokens/spol.md): What sPOL is, how Polygon's liquid staking token works, and how to stake POL to receive sPOL.
- [EIP-1559](https://docs.polygon.technology/pos/concepts/transactions/eip-1559.md): How EIP-1559 changed gas estimation and transaction fees on Polygon PoS, and how Type 2 transactions differ from legacy transactions.
- [EIP-4337](https://docs.polygon.technology/pos/concepts/transactions/eip-4337.md): How ERC-4337 account abstraction works on Polygon PoS, including UserOperations, Bundlers, EntryPoints, and Paymasters.
- [Meta transactions](https://docs.polygon.technology/pos/concepts/transactions/meta-transactions.md): What meta transactions are, why they matter, and how the relayer model decouples gas payment from transaction signing on Polygon PoS.
- [Becoming a validator](https://docs.polygon.technology/pos/get-started/becoming-a-validator.md): Requirements, responsibilities, and links to the step-by-step guides for joining and operating the Polygon PoS validator set.
- [Building on PoS](https://docs.polygon.technology/pos/get-started/building-on-polygon.md): How to connect to Polygon PoS, deploy contracts, bridge tokens, and find the right tooling for your project.
- [Governance fundamentals](https://docs.polygon.technology/pos/governance/governance-fundamentals.md): How Polygon PoS governance works, from off-chain ecosystem consensus through onchain upgrade execution.
- [Ethereum to PoS](https://docs.polygon.technology/pos/how-to/bridging/ethereum-polygon/ethereum-to-matic.md): Deploy sender and receiver contracts to transfer arbitrary data from Ethereum to Polygon PoS using the state sync mechanism.
- [PoS to Ethereum](https://docs.polygon.technology/pos/how-to/bridging/ethereum-polygon/matic-to-ethereum.md): Deploy child and root contracts to transfer data from Polygon PoS back to Ethereum using checkpoints and the RootChainManager.
- [Polygon Portal](https://docs.polygon.technology/pos/how-to/bridging/ethereum-polygon/portal-ui.md): Reference overview of the Polygon Portal bridge, including how tokens are locked and minted when crossing between Ethereum and Polygon PoS.
- [Submit mapping request](https://docs.polygon.technology/pos/how-to/bridging/ethereum-polygon/submit-mapping-request.md): Steps to submit a token mapping request to enable bridging between Ethereum and Polygon PoS.
- [Delegate tokens](https://docs.polygon.technology/pos/how-to/delegate.md): Steps to delegate POL tokens to a validator, withdraw rewards, restake, and manage your stake on Polygon PoS.
- [Run an Erigon archive node](https://docs.polygon.technology/pos/how-to/erigon-archive-node.md): Steps to install, configure, and start an Erigon archive node for Polygon PoS mainnet or Amoy testnet.
- [Using Ansible](https://docs.polygon.technology/pos/how-to/full-node/full-node-ansible.md): Steps to deploy and manage a Polygon PoS full node using an Ansible playbook.
- [Using binaries](https://docs.polygon.technology/pos/how-to/full-node/full-node-binaries.md): Steps to install Heimdall and Bor binaries, configure, and start a Polygon PoS full node.
- [Using Docker](https://docs.polygon.technology/pos/how-to/full-node/full-node-docker.md): Steps to run a Polygon PoS full node using official Docker images, including Heimdall and Bor setup on Linux.
- [Using GCP](https://docs.polygon.technology/pos/how-to/full-node/full-node-gcp.md): Steps to deploy a Polygon PoS node in a Google Cloud Platform VM instance using the gcloud CLI.
- [Using packages](https://docs.polygon.technology/pos/how-to/full-node/full-node-packages.md): Steps to install Heimdall and Bor packages, configure, and start a Polygon PoS full node.
- [Change owner and signer address](https://docs.polygon.technology/pos/how-to/operate-validator-node/change-signer-address.md): Steps to transfer your validator NFT to a new owner address or update the signer address for your Polygon PoS validator node.
- [Next steps](https://docs.polygon.technology/pos/how-to/operate-validator-node/next-steps.md): Steps to stake tokens, set commission, claim rewards, and complete onboarding after your validator node joins the Polygon PoS active set.
- [Top up Heimdall fee](https://docs.polygon.technology/pos/how-to/operate-validator-node/topup-heimdall-fee.md): Steps to top up the Heimdall fee for a Polygon PoS validator using the Staking UI or Etherscan.
- [Validator performance requirements](https://docs.polygon.technology/pos/how-to/operate-validator-node/validator-performance.md): Reference for the validator performance parameters, benchmarks, grace periods, and forced unstaking process defined in PIP-4.
- [Prerequisites](https://docs.polygon.technology/pos/how-to/prerequisites.md): System requirements, port configuration, and setup checklist for running a Polygon PoS full node or validator node.
- [Sync node using snapshots](https://docs.polygon.technology/pos/how-to/snapshots.md): Steps to download and apply community snapshots to sync a Polygon PoS sentry, validator, or full node without syncing from scratch.
- [Known issues and errors](https://docs.polygon.technology/pos/how-to/troubleshoot/known-issues.md): Diagnosis and resolution steps for common Bor and Heimdall errors encountered while running a Polygon PoS validator node.
- [Reporting issues](https://docs.polygon.technology/pos/how-to/troubleshoot/reporting-issues.md): Where to report bugs, security vulnerabilities, and node issues for Polygon PoS, including bug bounty programs and support channels.
- [Technical FAQs](https://docs.polygon.technology/pos/how-to/troubleshoot/technical-faqs.md): Reference answers to common technical questions about running Polygon PoS validator nodes, including key management, default directories, and troubleshooting commands.
- [Using Ansible](https://docs.polygon.technology/pos/how-to/validator/validator-ansible.md): Steps to deploy a Polygon PoS sentry node and validator node using an Ansible playbook.
- [Validator best practices](https://docs.polygon.technology/pos/how-to/validator/validator-best-practices.md): Security and operational best practices for running a Polygon PoS validator node, covering key management, OS hardening, networking, and monitoring.
- [Using binaries](https://docs.polygon.technology/pos/how-to/validator/validator-binaries.md): Steps to install Heimdall and Bor binaries, configure sentry and validator nodes, and start a Polygon PoS validator using binaries.
- [Using packages](https://docs.polygon.technology/pos/how-to/validator/validator-packages.md): Steps to install Heimdall and Bor packages, configure sentry and validator nodes, and start a Polygon PoS validator.
- [Overview](https://docs.polygon.technology/pos/overview.md): Conceptual overview of Polygon PoS: its dual-layer architecture, how transactions reach finality, and the role of core Ethereum contracts.
- [Common commands](https://docs.polygon.technology/pos/reference/commands.md): Reference for common Bor and Heimdall commands used by Polygon PoS node operators.
- [PoS mainnet multi-signatures](https://docs.polygon.technology/pos/reference/commit-chain-multisigs.md): Reference for active multi-signature wallets on the Polygon PoS mainnet and commitchain.
- [Delegation via validator shares](https://docs.polygon.technology/pos/reference/contracts/delegation.md): Contract reference for the validator share delegation mechanism on Polygon PoS.
- [Genesis contracts](https://docs.polygon.technology/pos/reference/contracts/genesis-contracts.md): List of genesis contracts deployed on Polygon PoS mainnet and Amoy testnet, with contract addresses.
- [Staking manager](https://docs.polygon.technology/pos/reference/contracts/stakingmanager.md): Contract reference for the StakeManager contract on Polygon PoS, covering validator management, staking, and reward distribution.
- [Mapped tokens](https://docs.polygon.technology/pos/reference/mapped-tokens.md): List of token mappings on the Polygon PoS mainnet and Amoy testnet.
- [Network upgrade process](https://docs.polygon.technology/pos/reference/network-upgrade-process.md): Reference for Polygon PoS hardfork activations, versions, and the network upgrade process.
- [Default ports for nodes](https://docs.polygon.technology/pos/reference/port-management.md): Reference for default ports used by Bor and Heimdall nodes on Polygon PoS.
- [Rewards and staking incentives](https://docs.polygon.technology/pos/reference/rewards.md): Reference for Polygon PoS validator and delegator reward rates, staking incentives, and transaction fee distribution.
- [RPC endpoints](https://docs.polygon.technology/pos/reference/rpc-endpoints.md): Network details and RPC endpoints for the Polygon PoS mainnet and Amoy testnet.
- [Seed and bootnodes](https://docs.polygon.technology/pos/reference/seed-and-bootnodes.md): List of seed nodes and bootnodes for the Polygon PoS mainnet and Amoy testnet, for Bor and Heimdall.
- [Setting Up Telemetry](https://docs.polygon.technology/pos/reference/telemetry-setup-guide.md): Configuration reference for setting up telemetry monitoring for Bor and Heimdall nodes.
- [Build with AI](https://docs.polygon.technology/resources/build-with-ai.md): AI tools and integrations for building on OMS with your IDE or coding assistant.
- [Overview](https://docs.polygon.technology/resources/guides.md): Browse guides across the Open Money Stack, filterable by product and use case.
- [Compliance](https://docs.polygon.technology/stablecoins-payments/compliance.md): How the Open Money Stack handles KYC, KYB, AML, and transaction monitoring for regulated payment products.
- [Overview](https://docs.polygon.technology/stablecoins-payments/index.md): How the Open Money Stack handles payments, stablecoin settlement, and compliant fiat access end to end.
- [Off-ramps](https://docs.polygon.technology/stablecoins-payments/offramps.md): Crypto-to-fiat off-ramp providers for converting assets on Polygon to local currency.
- [On-ramps](https://docs.polygon.technology/stablecoins-payments/onramps.md): Fiat-to-crypto on-ramp providers and integration guides for Polygon.
- [Payment Providers](https://docs.polygon.technology/stablecoins-payments/payment-providers.md): Directory of payment infrastructure projects supporting Polygon.
- [Stablecoins on Polygon](https://docs.polygon.technology/stablecoins-payments/stablecoins.md): Overview of stablecoins available on Polygon Chain, with integration guides for USDC and cross-chain transfers.
- [Use Cases](https://docs.polygon.technology/stablecoins-payments/use-cases.md): How payment networks, card issuers, remittance platforms, and financial institutions use Polygon for payments.
- [Overview](https://docs.polygon.technology/tools/chain-indexer-framework/overview.md): How the Chain Indexer Framework works and why it is useful for building event-driven dApp backends on EVM chains.
- [Usage](https://docs.polygon.technology/tools/chain-indexer-framework/usage.md): How to install the Chain Indexer Framework and run the provided example pipelines.
- [Hardhat](https://docs.polygon.technology/tools/dApp-development/common-tools/hardhat.md): Build, test, and deploy a smart contract to Polygon Amoy using Hardhat.
- [Remix](https://docs.polygon.technology/tools/dApp-development/common-tools/remix.md): Deploy a HelloWorld smart contract to Polygon Amoy using Remix IDE and MetaMask.
- [Replit](https://docs.polygon.technology/tools/dApp-development/common-tools/replit.md): Deploy a Solidity smart contract to Polygon Amoy using Replit IDE, without any local environment setup.
- [Commands](https://docs.polygon.technology/tools/dApp-development/launchpad/commands.md): Complete reference for all dApp Launchpad CLI commands and their options.
- [Common pitfalls](https://docs.polygon.technology/tools/dApp-development/launchpad/common-pitfalls.md): Known issues in dApp Launchpad with their causes and solutions.
- [Contributing](https://docs.polygon.technology/tools/dApp-development/launchpad/contributing.md): How to build dApp Launchpad from source and run a local development environment for the tool itself.
- [Frontend](https://docs.polygon.technology/tools/dApp-development/launchpad/frontend.md): How to work with the Next.js frontend in a dApp Launchpad project, including wallet connections, contract interactions, and deployment.
- [Introduction](https://docs.polygon.technology/tools/dApp-development/launchpad/intro.md): What dApp Launchpad is, what it automates, and when to use it.
- [Quickstart](https://docs.polygon.technology/tools/dApp-development/launchpad/quickstart.md): Build and run your first dApp Launchpad project from installation to a live local development environment.
- [Smart contracts](https://docs.polygon.technology/tools/dApp-development/launchpad/smart-contracts.md): How to work with smart contracts in a dApp Launchpad project, including local deployment, the block explorer, and production deployment.
- [Tutorials](https://docs.polygon.technology/tools/dApp-development/third-party-tutorials.md): Index of third-party resources and tutorials for developing, deploying, and managing dApps on Polygon.
- [Interact with a node RPC](https://docs.polygon.technology/tools/dApp-development/tutorials/access-node.md): How to connect to a Polygon RPC provider and send your first blockchain request using Alchemy.
- [The Graph](https://docs.polygon.technology/tools/data/thegraph.md): How to create, deploy, and query a subgraph for a Polygon smart contract using The Graph.
- [Test token faucets](https://docs.polygon.technology/tools/gas/matic-faucet.md): How to obtain test POL and ETH tokens for Polygon testnets using third-party faucets.
- [Estimate gas fees](https://docs.polygon.technology/tools/gas/polygon-gas-station.md): How to query Polygon Gas Station for gas price recommendations, and how to interpret the response.
- [Overview](https://docs.polygon.technology/tools/index.md): Tools, integrations, and infrastructure for building on Polygon Chain.
- [ABI manager](https://docs.polygon.technology/tools/matic-js/advanced/abi-manager.md): matic.js internally uses ABIManager for handling ABI management, configuration for you. All of the ABI and config are taken from static repo.
- [Exit util](https://docs.polygon.technology/tools/matic-js/advanced/exit-util.md): matic.js internally use ExitUtil for generating proofs. It is a class which has different methods for helping with exit utilities.
- [Plugin](https://docs.polygon.technology/tools/matic-js/advanced/plugin.md): Using plugin you can inject your code into matic.js. It can be used to write common set of generic codes which can be provided to anyone using a package.
- [API overview](https://docs.polygon.technology/tools/matic-js/api-architecture.md): The Matic.js library follows common api architecture throughout and the APIs are divided into two types:
- [Get started](https://docs.polygon.technology/tools/matic-js/get-started.md): Matic.js a JavaScript library that facilitates interaction with the Polygon network. It provides developers with simplified operations such as depositing, trans
- [POS client](https://docs.polygon.technology/tools/matic-js/pos/client.md): Make sure you have set up Matic.js by following the get started guide.
- [Deposit ETH](https://docs.polygon.technology/tools/matic-js/pos/deposit-ether.md): Use the depositEther method to deposit ETH from ethereum to polygon. For example:
- [approveAll](https://docs.polygon.technology/tools/matic-js/pos/erc1155/approve-all.md): The approveAll method can be used to approve all tokens on root token.
- [approveAllForMintable](https://docs.polygon.technology/tools/matic-js/pos/erc1155/approve-all-for-mintable.md): The approveAllForMintable method can be used to approve all mintable tokens on root token.
- [deposit](https://docs.polygon.technology/tools/matic-js/pos/erc1155/deposit.md): The deposit method can be used to deposit required amount of a token from ethereum to polygon chain.
- [depositMany](https://docs.polygon.technology/tools/matic-js/pos/erc1155/deposit-many.md): The depositMany method can be used to deposit required amounts of multiple token from ethereum to polygon chain.
- [getBalance](https://docs.polygon.technology/tools/matic-js/pos/erc1155/get-balance.md): The getBalance method can be used to get the balance of user for a token. It is available on both child and parent token.
- [index](https://docs.polygon.technology/tools/matic-js/pos/erc1155/index.md): POSClient provides erc1155 method which helps you to interact with a erc1155 token.
- [isApprovedAll](https://docs.polygon.technology/tools/matic-js/pos/erc1155/is-approved-all.md): The isApprovedAll method checks if all tokens are approved for a user. It returns boolean value.
- [isWithdrawExited](https://docs.polygon.technology/tools/matic-js/pos/erc1155/is-withdraw-exited.md): The isWithdrawExited method check if a withdraw has been exited. It returns boolean value.
- [isWithdrawExitedMany](https://docs.polygon.technology/tools/matic-js/pos/erc1155/is-withdraw-exited-many.md): The isWithdrawExitedMany method check if withdraw has been exited for multiple tokens. It returns boolean value.
- [transfer](https://docs.polygon.technology/tools/matic-js/pos/erc1155/transfer.md): The transfer method can be used to transfer tokens from one user to another user.
- [withdrawExit](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-exit.md): The withdrawExit method can be used to exit the withdraw process by using the txHash from withdrawStart method.
- [withdrawExitFaster](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-exit-faster.md): The withdrawExitFaster method can be used to exit the withdraw process by using the txHash from withdrawStart method.
- [withdrawExitFasterMany](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-exit-faster-many.md): The withdrawExitFasterMany method can be used to exit the withdraw process by using the txHash from withdrawStartMany method.
- [withdrawExitMany](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-exit-many.md): The withdrawExitMany method can be used to exit the withdraw process by using the txHash from withdrawStartMany method.
- [withdrawStart](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-start.md): The withdrawStart method can be used to initiate the withdraw process which will burn the specified amount of tokenId on polygon chain.
- [withdrawStartMany](https://docs.polygon.technology/tools/matic-js/pos/erc1155/withdraw-start-many.md): The withdrawStartMany method can be used to initiate the withdraw process which will burn the specified amounts of multiple token respectively on polygon chain.
- [approve](https://docs.polygon.technology/tools/matic-js/pos/erc20/approve.md): The approve method can be used to approve required amount on the root token.
- [approveMax](https://docs.polygon.technology/tools/matic-js/pos/erc20/approve-max.md): The approveMax method can be used to approve max amount on the root token.
- [deposit](https://docs.polygon.technology/tools/matic-js/pos/erc20/deposit.md): The deposit method can be used to deposit required amount from root token to child token.
- [getAllowance](https://docs.polygon.technology/tools/matic-js/pos/erc20/get-allowance.md): The getAllowance method can be used to get the approved amount for the user.
- [getBalance](https://docs.polygon.technology/tools/matic-js/pos/erc20/get-balance.md): The getBalance method can be used to get the balance of user. It is available on both child and parent token.
- [Overview](https://docs.polygon.technology/tools/matic-js/pos/erc20/index.md): The POSClient has an erc20 method which returns an object of an ERC20 token.
- [isWithdrawExited](https://docs.polygon.technology/tools/matic-js/pos/erc20/is-withdraw-exited.md): The isWithdrawExited method can be used to know whether the withdraw has been exited or not.
- [transfer](https://docs.polygon.technology/tools/matic-js/pos/erc20/transfer.md): The transfer method can be used to transfer amount from one address to another address.
- [withdrawExit](https://docs.polygon.technology/tools/matic-js/pos/erc20/withdraw-exit.md): The withdrawExit method can be used to exit the withdraw process by using the txHash from withdrawStart method.
- [withdrawExitFaster](https://docs.polygon.technology/tools/matic-js/pos/erc20/withdraw-exit-faster.md): The withdrawExitFaster method can be used to exit the withdraw process faster by using the txHash from withdrawStart method.
- [withdrawStart](https://docs.polygon.technology/tools/matic-js/pos/erc20/withdraw-start.md): The withdrawStart method can be used to initiate the withdraw process which will burn the specified amount on polygon chain.
- [approve](https://docs.polygon.technology/tools/matic-js/pos/erc721/approve.md): The approve method can be used to approve required amount on root token.
- [approveAll](https://docs.polygon.technology/tools/matic-js/pos/erc721/approve-all.md): The approveAll method can be used to approve all tokens.
- [deposit](https://docs.polygon.technology/tools/matic-js/pos/erc721/deposit.md): The deposit method can be used to deposit a token from ethereum to polygon chain.
- [depositMany](https://docs.polygon.technology/tools/matic-js/pos/erc721/deposit-many.md): The depositMany method can be used to deposit multiple token from ethereum to polygon chain.
- [getAllTokens](https://docs.polygon.technology/tools/matic-js/pos/erc721/get-all-tokens.md): The getAllTokens method returns all tokens owned by specified user.
- [getTokenIdAtIndexForUser](https://docs.polygon.technology/tools/matic-js/pos/erc721/get-token-id-at-index-for-user.md): The getTokenIdAtIndexForUser method returns token id on supplied index for user.
- [getTokensCount](https://docs.polygon.technology/tools/matic-js/pos/erc721/get-tokens-count.md): The getTokensCount method returns tokens count for specified user.
- [Overview](https://docs.polygon.technology/tools/matic-js/pos/erc721/index.md): POSClient provides erc721 method which helps you to interact with a erc721 token.
- [isApproved](https://docs.polygon.technology/tools/matic-js/pos/erc721/is-approved.md): The isApproved method checks if token is approved for specified tokenId. It returns boolean value.
- [isApprovedAll](https://docs.polygon.technology/tools/matic-js/pos/erc721/is-approved-all.md): The isApprovedAll method checks if all token is approved. It returns boolean value.
- [isWithdrawExited](https://docs.polygon.technology/tools/matic-js/pos/erc721/is-withdraw-exited.md): The isWithdrawExited method check if a withdraw has been exited. It returns boolean value.
- [isWithdrawExitedMany](https://docs.polygon.technology/tools/matic-js/pos/erc721/is-withdraw-exited-many.md): The isWithdrawExitedMany method check if withdraw has been exited for multiple tokens. It returns boolean value.
- [transfer](https://docs.polygon.technology/tools/matic-js/pos/erc721/transfer.md): The transfer method can be used to transfer tokens from one user to another user.
- [withdrawExit](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-exit.md): withdrawExit method can be used to exit the withdraw process by using the txHash from withdrawStart method.
- [withdrawExitFaster](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-exit-faster.md): The withdrawExitFaster method can be used to exit the withdraw process by using the txHash from withdrawStart method.
- [withdrawExitFasterMany](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-exit-faster-many.md): The withdrawExitFasterMany method can be used to exit the withdraw process by using the txHash from withdrawStartMany method.
- [withdrawExitMany](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-exit-many.md): The withdrawExitMany method can be used to exit the withdraw process by using the txHash from withdrawStartMany method.
- [withdrawStart](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-start.md): The withdrawStart method can be used to initiate the withdraw process which will burn the specified token on polygon chain.
- [withdrawStartMany](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-start-many.md): The withdrawStartMany method can be used to initiate the withdraw process which will burn the multiple token on polygon chain.
- [withdrawStartWithMetaData](https://docs.polygon.technology/tools/matic-js/pos/erc721/withdraw-start-with-meta-data.md): The withdrawStartWithMetaData method can be used to initiate the withdraw process which will burn the specified token on polygon chain. Under the hood it calls
- [isCheckPointed](https://docs.polygon.technology/tools/matic-js/pos/is-check-pointed.md): The isCheckPointed method can be used to know if a transaction has been check-pointed.
- [isDeposited](https://docs.polygon.technology/tools/matic-js/pos/is-deposited.md): The isDeposited method shows if a deposit has been completed.
- [Set proof API](https://docs.polygon.technology/tools/matic-js/set-proof-api.md): The API links have been changed from https://apis.matic.network → https://proof-generator.polygon.technology. Please make sure to update the links.
- [Ethers](https://docs.polygon.technology/tools/matic-js/setup/ethers.md): ethers.js is a library for interacting with the Ethereum Blockchain and its ecosystem.
- [Web3js](https://docs.polygon.technology/tools/matic-js/setup/web3js.md): Web3.js is a collection of libraries that allow you to interact with a local or remote Ethereum node using HTTP, IPC or WebSocket.
- [Chainlink](https://docs.polygon.technology/tools/oracles/chainlink.md): How to read a Chainlink price feed in a Solidity smart contract on Polygon.
- [Chronicle](https://docs.polygon.technology/tools/oracles/chronicle.md): How to read Chronicle oracle price data in a Solidity smart contract on Polygon zkEVM.
- [Getting started](https://docs.polygon.technology/tools/oracles/getting-started.md): An explanation of blockchain oracles and how they connect smart contracts to external data on Polygon.
- [Supra](https://docs.polygon.technology/tools/oracles/supra.md): How to integrate Supra Pull Oracle and Push Oracle into a Polygon smart contract or JavaScript application.
- [Bug bounty programs](https://docs.polygon.technology/tools/security/bugbounty.md): Active bug bounty programs for Polygon infrastructure, including platforms, scopes, and reward ranges.
- [Contact us](https://docs.polygon.technology/tools/security/contact.md): Contact information for the Polygon Labs security team.
- [Responsible disclosure](https://docs.polygon.technology/tools/security/disclosure.md): Steps for reporting a security vulnerability or CVE in Polygon technology to the security team before public disclosure.
- [Governance & management](https://docs.polygon.technology/tools/security/governance.md): How Polygon Labs structures its security program using ISO/IEC 27001, including ISMS design, risk management, and policy governance.
- [Human resources](https://docs.polygon.technology/tools/security/hr.md): Polygon Labs' security practices for personnel onboarding, offboarding, access provisioning, and security awareness training.
- [Infrastructure](https://docs.polygon.technology/tools/security/infrastructure.md): Security practices for Polygon network infrastructure, including onchain monitoring and multisig signer requirements.
- [Security operations](https://docs.polygon.technology/tools/security/operations.md): Polygon Labs' security operations practices, including logging, monitoring, incident response, and access control.
- [Overview](https://docs.polygon.technology/tools/security/overview.md): How Polygon Labs approaches information security: team structure, monitoring, assessments, and bug bounties.
- [Security reports](https://docs.polygon.technology/tools/security/reports.md): Public security audits, penetration tests, and certifications for Polygon infrastructure and applications.
- [Risk management](https://docs.polygon.technology/tools/security/risk.md): Polygon Labs' approach to security risk management, including risk assessment methodology, control standards, residual risk handling, and compliance mapping.
- [Software development](https://docs.polygon.technology/tools/security/sdlc.md): Security practices applied throughout Polygon Labs' software development lifecycle, including threat modeling, CI/CD controls, and pre-production assessments.
- [Smart contracts](https://docs.polygon.technology/tools/security/smartcontracts.md): Polygon Labs' approach to smart contract security, including coding standards, internal review processes, and external audit practices.
- [Vulnerability management](https://docs.polygon.technology/tools/security/vulnerability.md): How Polygon Labs identifies, tracks, prioritizes, and remediates security vulnerabilities across its systems and applications.
- [Crust network](https://docs.polygon.technology/tools/storage/crusthelpers.md): How to integrate Crust Network decentralized storage with your Polygon dApp using available helper tools.
- [Filecoin](https://docs.polygon.technology/tools/storage/filecoinhelpers.md): How to use Filecoin and IPFS storage services in your Polygon dApp for persistent, decentralized file storage.
- [IPFS](https://docs.polygon.technology/tools/storage/ipfs.md): How to use IPFS for decentralized file storage in Polygon dApps, including example projects.
- [AppKit](https://docs.polygon.technology/tools/wallets/appkit.md): How to integrate Reown AppKit for wallet connections in a Polygon dApp.
- [Getting started](https://docs.polygon.technology/tools/wallets/getting-started.md): An overview of wallet options compatible with Polygon networks and how to choose one.
- [MetaMask Embedded Wallets](https://docs.polygon.technology/tools/wallets/metamask-ew.md): Please view the third-party content disclaimer here.
- [Add Polygon network](https://docs.polygon.technology/tools/wallets/metamask/add-polygon-network.md): How to add Polygon PoS and zkEVM network configurations to MetaMask using ChainList, Polygonscan, or manual entry.
- [Overview](https://docs.polygon.technology/tools/wallets/metamask/overview.md): MetaMask key properties and security tips for use with Polygon networks.
- [Polygon Portal](https://docs.polygon.technology/tools/wallets/portal.md): How to connect a wallet, bridge tokens, claim bridged assets, and add custom tokens using Polygon Portal.
- [Reown](https://docs.polygon.technology/tools/wallets/reown.md): How to integrate Reown AppKit or WalletKit for wallet connections and Web3 UX on Polygon.
- [WalletConnect](https://docs.polygon.technology/tools/wallets/walletconnect.md): Please view the third-party content disclaimer here.
- [WalletKit](https://docs.polygon.technology/tools/wallets/walletkit.md): Please view the third-party content disclaimer here.
- [Fund your protocol](https://docs.polygon.technology/trails/fund.md): Let users fund your app, wallet, or protocol from any token on any chain, or directly from a credit card or bank account.
- [Cross-Chain Money Movement (Trails)](https://docs.polygon.technology/trails/index.md): Move tokens across any chain, with any token, from any wallet.
- [Cross-Chain Money Actions](https://docs.polygon.technology/trails/money-actions.md): Execute a swap, bridge, and protocol interaction as a single atomic transaction across any chain.
- [Agentic Payments](https://docs.polygon.technology/wallets/agentic-wallets.md): Infrastructure for AI agents that initiate, negotiate, and settle payments autonomously on Polygon.
- [Wallet Architecture](https://docs.polygon.technology/wallets/architecture.md): How embedded wallets work end-to-end: smart sessions, identity attestation, Merkleized configuration, and the Guard Firewall.
- [Authentication](https://docs.polygon.technology/wallets/authentication.md): Configure sign-in methods for embedded wallets: social login, email OTP, passkeys, and guest wallets.
- [Custodial Wallets](https://docs.polygon.technology/wallets/custodial-wallets.md): Enterprise-grade custodial wallets with full compliance and managed key infrastructure.
- [Custom Wallet](https://docs.polygon.technology/wallets/custom-wallet.md): Build a fully custom embedded wallet using the Wallet Development Kit on top of Sequence infrastructure. Self-host critical components if needed.
- [Overview](https://docs.polygon.technology/wallets/embedded-wallets.md): Non-custodial account abstraction wallets built directly into your app, no browser extension required.
- [Interactive Demo](https://docs.polygon.technology/wallets/examples/interactive-demo.md): An interactive walkthrough of a neobank built on Polygon embedded wallets, using mock data.
- [Guard Firewall](https://docs.polygon.technology/wallets/guard-firewall.md): Ecosystem-level transaction review that evaluates every transaction against policies, threat simulations, and blacklists before allowing onchain execution.
- [Hosted Wallet](https://docs.polygon.technology/wallets/hosted-wallet.md): Launch an embedded wallet on your domain with Sequence-operated infrastructure, branding control, Smart Sessions, and passkey-based auth.
- [Identity Instrument](https://docs.polygon.technology/wallets/identity-instrument.md): Enclave-backed service that verifies user identity, binds device Auth Keys, and signs session attestations for embedded wallets.
- [Offer Yield Accounts to Your Users](https://docs.polygon.technology/wallets/morpho-vault-deposit.md): Add an interest-bearing savings feature to your fintech app. Users deposit funds, earn yield automatically, and withdraw at any time, with no crypto knowledge required.
- [Quickstart](https://docs.polygon.technology/wallets/quickstart.md): Integrate a Polygon embedded wallet into your React app in three steps.
- [Recovery](https://docs.polygon.technology/wallets/recovery.md): How users recover access to their embedded wallet using passkeys and timed recovery.
- [Getting Started](https://docs.polygon.technology/wallets/sdk/getting-started.md): Set up the Embedded Wallet Web SDK in a Vite or Next.js application.
- [useChain](https://docs.polygon.technology/wallets/sdk/hooks/use-chain.md): Hook to retrieve blockchain network configuration details by chain ID.
- [useExplicitSessions](https://docs.polygon.technology/wallets/sdk/hooks/use-explicit-sessions.md): Hook for creating, retrieving, and modifying explicit sessions in embedded wallet connections.
- [useFeeOptions](https://docs.polygon.technology/wallets/sdk/hooks/use-fee-options.md): Hook for handling fee token selection for unsponsored transactions.
- [useHasPermission](https://docs.polygon.technology/wallets/sdk/hooks/use-has-permission.md): Hook to check whether the current session has permission to execute a batch of transactions.
- [useListAccounts](https://docs.polygon.technology/wallets/sdk/hooks/use-list-accounts.md): Hook to retrieve all accounts connected to a WaaS session.
- [useOpenConnectModal](https://docs.polygon.technology/wallets/sdk/hooks/use-open-connect-modal.md): Hook to control the wallet connection modal.
- [useProjectAccessKey](https://docs.polygon.technology/wallets/sdk/hooks/use-project-access-key.md): Hook to retrieve the project access key from the connect configuration.
- [useSendWalletTransaction](https://docs.polygon.technology/wallets/sdk/hooks/use-send-wallet-transaction.md): Hook to send a transaction via the embedded wallet popup.
- [useSequenceSessionState](https://docs.polygon.technology/wallets/sdk/hooks/use-sequence-session-state.md): Hook to access embedded wallet and session state information.
- [useSignInEmail](https://docs.polygon.technology/wallets/sdk/hooks/use-sign-in-email.md): Hook to retrieve the email address associated with the connected wallet.
- [useStorage](https://docs.polygon.technology/wallets/sdk/hooks/use-storage.md): Hook to access the storage instance used by the connect client.
- [useTheme](https://docs.polygon.technology/wallets/sdk/hooks/use-theme.md): Hook to access and modify theme and modal position settings.
- [useWalletSettings](https://docs.polygon.technology/wallets/sdk/hooks/use-wallet-settings.md): Hook to access and modify wallet configuration settings.
- [useWallets](https://docs.polygon.technology/wallets/sdk/hooks/use-wallets.md): Hook for managing connected wallets, both embedded and external.
- [Smart Sessions Examples](https://docs.polygon.technology/wallets/sdk/smart-sessions/examples.md): Example smart session configurations for common DeFi operations.
- [Smart Sessions Overview](https://docs.polygon.technology/wallets/sdk/smart-sessions/overview.md): Grant dApps temporary, limited permissions instead of requiring approval for every transaction.
- [Smart Sessions Utilities](https://docs.polygon.technology/wallets/sdk/smart-sessions/utils.md): Helper functions for creating smart session permissions.
- [Security Architecture](https://docs.polygon.technology/wallets/security.md): How keys are secured, transactions are validated, and the wallet remains non-custodial end to end.
- [Smart Sessions](https://docs.polygon.technology/wallets/smart-sessions.md): Scope transaction permissions so your app can execute payments on behalf of users without repeated approval prompts.
- [Smart Sessions: Technical Deep Dive](https://docs.polygon.technology/wallets/smart-sessions-deep-dive.md): How implicit and explicit sessions work under the hood, their security guarantees, and how to combine them for payment flows.
- [Timed Recovery: Technical Reference](https://docs.polygon.technology/wallets/timed-recovery-technical.md): Full technical specification of the timed recovery flow, onchain observability, Sequence independence, and recovery FAQ.
- [Automate USDC collection with a Treasury Wallet](https://docs.polygon.technology/wallets/treasury-wallet.md): Use Sequence Embedded Wallets and Smart Sessions to automate pull-and-push USDC flows from client wallets to a central treasury, with no per-transfer approvals.
- [Wallet Configuration](https://docs.polygon.technology/wallets/wallet-configuration.md): How the Merkleized wallet configuration works: single onchain root, signers, sessions, recovery, and cross-chain coherency.
- [Wallet Linking](https://docs.polygon.technology/wallets/wallet-linking.md): Create a verifiable association between an embedded wallet and an external wallet address for compliance, asset verification, and fund migration.
- [Wallet Operations](https://docs.polygon.technology/wallets/wallet-operations.md): Send transactions, transfer stablecoins, sign messages, and read balances from an embedded wallet.

## OpenAPI Specs

- [openapi](https://docs.polygon.technology/api-reference/openapi.yaml)