--- category: Reference description: Glossary, governance structures, origin tracks, and technical specifications. page_count: 67 token_estimate: 9179 updated: '2026-06-25T12:38:13.291384+00:00' --- ## Account Management Method Group https://docs.polkadot.com/reference/apps/protocol/truapi/account-management.md TrUAPI Account Management method group for resolving sub-accounts, reading account state, and using @parity/product-sdk-signer to get Product accounts. ### Sections - Introduction `#introduction` - Conceptual Contract `#conceptual-contract` - Where to Go Next `#where-to-go-next` --- ## App Development Reference https://docs.polkadot.com/reference/apps.md Technical reference for building Polkadot Products, including Hosts, TrUAPI between Host and Product, and the on-chain infrastructure they consume. ### Sections - Introduction `#introduction` - Architecture `#architecture` - Hosts `#hosts` - Protocol `#protocol` - Infrastructure `#infrastructure` - Skills `#skills` - Where to Go Next `#where-to-go-next` --- ## Bulletin Chain Authorization https://docs.polkadot.com/reference/apps/infrastructure/bulletin-chain/authorization.md How writes to the Bulletin Chain are gated — the explicit per-account authorization model, the transaction-and-byte quota, and the expiration lifecycle. ### Sections - Introduction `#introduction` - What an Authorization Records `#what-an-authorization-records` - What a Write Costs `#what-a-write-costs` - Expiration `#expiration` - Provisioning on TestNet `#provisioning-on-testnet` - Where to Go Next `#where-to-go-next` --- ## Bulletin Chain Reference https://docs.polkadot.com/reference/apps/infrastructure/bulletin-chain.md Reference for the Bulletin Chain — Polkadot's decentralized, content-addressed storage layer for Products, with authorization, chunked uploads, and renewal. ### Sections - Introduction `#introduction` - Architecture `#architecture` - When to Use Bulletin `#when-to-use-bulletin` - Where to Go Next `#where-to-go-next` --- ## Bulletin Chain Renewal https://docs.polkadot.com/reference/apps/infrastructure/bulletin-chain/renewal.md The retention lifecycle for data on the Bulletin Chain — default window, what happens at expiration, and the mechanics of renewing data before it falls off. ### Sections - Introduction `#introduction` - The Default Retention Window `#the-default-retention-window` - What Renewal Does `#what-renewal-does` - What Renewal Costs `#what-renewal-costs` - What Happens to Forgotten Data `#what-happens-to-forgotten-data` - Where to Go Next `#where-to-go-next` --- ## Chain Interaction Method Group https://docs.polkadot.com/reference/apps/protocol/truapi/chain-interaction.md TrUAPI method group for reading chain state and subscribing to changes, behind @parity/product-sdk-chain-client and the typed PAPI API exposed per chain. ### Sections - Introduction `#introduction` - Conceptual Contract `#conceptual-contract` - Where to Go Next `#where-to-go-next` --- ## Chat in the Polkadot App https://docs.polkadot.com/reference/apps/hosts/polkadot-app/chat.md Reference for Polkadot App Chat, room and bot registration, typed messages, custom rendering, and how it composes Statement Store with Bulletin Chain. ### Sections - Introduction `#introduction` - Room and Bot Registration `#room-and-bot-registration` - Message Types `#message-types` - Custom Message Rendering `#custom-message-rendering` - Message Queueing `#message-queueing` - Composition: Statement Store + Bulletin Chain `#composition-statement-store-bulletin-chain` - Where to Go Next `#where-to-go-next` --- ## Chat Method Group https://docs.polkadot.com/reference/apps/protocol/truapi/chat.md TrUAPI method group for in-App chat, including room and bot registration, typed message publishing, and custom message rendering by subscription. ### Sections - Introduction `#introduction` - Conceptual Contract `#conceptual-contract` - Where to Go Next `#where-to-go-next` --- ## Chunked Uploads on the Bulletin Chain https://docs.polkadot.com/reference/apps/infrastructure/bulletin-chain/chunked-upload.md How payloads larger than the per-transaction byte limit are uploaded as chunks under a DAG-PB manifest, transparently to the Product. ### Sections - Introduction `#introduction` - What Happens Internally `#what-happens-internally` - What This Costs `#what-this-costs` - What a Product Sees `#what-a-product-sees` - Where to Go Next `#where-to-go-next` --- ## Coinage in the Polkadot App https://docs.polkadot.com/reference/apps/hosts/polkadot-app/coinage.md Reference for Coinage, the Polkadot App's peer-to-peer payment flow with the privacy and personhood-gating properties of the pallet-coinage primitive. ### Sections - Introduction `#introduction` - Conceptual Model `#conceptual-model` - Where to Go Next `#where-to-go-next` --- ## Cross-Chain Bulletin Storage via People Chain https://docs.polkadot.com/reference/apps/infrastructure/bulletin-chain/cross-chain.md How a Bulletin Chain storage call initiated from the People Chain — where a Product's Proof of Personhood identity lives — reaches the Bulletin Chain via XCM. ### Sections - Introduction `#introduction` - The Flow `#the-flow` - When to Use the Cross-Chain Path `#when-to-use-the-cross-chain-path` - Where to Go Next `#where-to-go-next` --- ## dotNS Architecture https://docs.polkadot.com/reference/apps/infrastructure/dotns/architecture.md The cooperating contracts on Asset Hub that back the dotNS registry — name records, ownership, content references, and PopRules enforcement. ### Sections - Introduction `#introduction` - Conceptual Responsibilities `#conceptual-responsibilities` - Where to Go Next `#where-to-go-next` --- ## dotNS CLI Reference https://docs.polkadot.com/reference/apps/infrastructure/dotns/cli.md Reference for @parity/dotns-cli — the command-line tool for managing .dot name registrations, contenthash updates, transfers, and renewals. ### Sections - Introduction `#introduction` - Command Families `#command-families` - Installing and Authenticating `#installing-and-authenticating` - Command Surface `#command-surface` - Where to Go Next `#where-to-go-next` --- ## dotNS Reference https://docs.polkadot.com/reference/apps/infrastructure/dotns.md Reference for dotNS — the .dot name system on Asset Hub that resolves Product names to published bundles, with PopRules pricing and contract architecture. ### Sections - Introduction `#introduction` - Where to Go Next `#where-to-go-next` --- ## dotNS TestNet Contracts https://docs.polkadot.com/reference/apps/infrastructure/dotns/testnet-contracts.md Current Paseo TestNet contract addresses for the dotNS registry — registry core, registration and pricing, and lifecycle contract families. ### Sections - Introduction `#introduction` - Contract Address Table `#contract-address-table` - How to Use These Addresses `#how-to-use-these-addresses` - Where to Go Next `#where-to-go-next` --- ## Entropy Method Group https://docs.polkadot.com/reference/apps/protocol/truapi/entropy.md TrUAPI method group for deriving deterministic per-Product entropy from the user's root key, suitable for seeding Product-local key material. ### Sections - Introduction `#introduction` - Conceptual Contract `#conceptual-contract` - Where to Go Next `#where-to-go-next` --- ## Glossary https://docs.polkadot.com/reference/glossary.md Glossary of terms used within the Polkadot ecosystem, Polkadot SDK, its subsequent libraries, and other relevant Web3 terminology. ### Sections - Alias `#alias` - Allowance `#allowance` - Asset Hub `#asset-hub` - Authority `#authority` - Authority Round (Aura) `#authority-round-aura` - Blake2b-256 `#blake2b-256` - Blind Assignment of Blockchain Extension (BABE) `#blind-assignment-of-blockchain-extension-babe` - Block Author `#block-author` - Browse `#browse` - Bulletin Chain `#bulletin-chain` - Byzantine Fault Tolerance (BFT) `#byzantine-fault-tolerance-bft` - Byzantine Failure `#byzantine-failure` - Practical Byzantine Fault Tolerance (pBFT) `#practical-byzantine-fault-tolerance-pbft` - Call `#call` - Chain Specification `#chain-specification` - Chain State `#chain-state` - Chat `#chat` - Coin (in Coinage) `#coin-in-coinage` - Coinage `#coinage` - Collator `#collator` - Collective `#collective` - Consensus `#consensus` - Consensus Algorithm `#consensus-algorithm` - Consensus Engine `#consensus-engine` - Content Identifier (CID) `#content-identifier-cid` - Coretime `#coretime` - Cross-Consensus Messaging (XCM) `#cross-consensus-messaging-xcm` - DAG-PB `#dag-pb` - Derived Sub-Account `#derived-sub-account` - Development Phrase `#development-phrase` - Digest `#digest` - Dimension of Individuality Measurement (DIM) `#dimension-of-individuality-measurement-dim` - Dispatchable `#dispatchable` - DOT `#dot` - dot Address `#dot-address` - DotNS `#dotns` - Entropy `#entropy` - Ephemeral `#ephemeral` - Events `#events` - Executor `#executor` - Existential Deposit `#existential-deposit` - Extrinsic `#extrinsic` - Fork Choice Rule/Strategy `#fork-choice-rulestrategy` - Framework for Runtime Aggregation of Modularized Entities (FRAME) `#framework-for-runtime-aggregation-of-modularized-entities-frame` - Full Node `#full-node` - Genesis Configuration `#genesis-configuration` - GHOST-based Recursive Ancestor Deriving Prefix Agreement (GRANDPA) `#ghost-based-recursive-ancestor-deriving-prefix-agreement-grandpa` - Handoff Protocol (HOP) `#handoff-protocol-hop` - Header `#header` - HOLLAR `#hollar` - Host `#host` - Host API `#host-api` - Hybrid Consensus `#hybrid-consensus` - Inherent Transactions `#inherent-transactions` - InterPlanetary File System (IPFS) `#interplanetary-file-system-ipfs` - JSON-RPC `#json-rpc` - Keystore `#keystore` - Kusama `#kusama` - libp2p `#libp2p` - Light Client `#light-client` - Manifest `#manifest` - Metadata `#metadata` - Nominated Proof of Stake (NPoS) `#nominated-proof-of-stake-npos` - Oracle `#oracle` - Origin `#origin` - Pairing `#pairing` - Pallet `#pallet` - PAPI `#papi` - Parachain `#parachain` - PAS `#pas` - Paseo TestNet `#paseo-testnet` - People Chain `#people-chain` - Pocket `#pocket` - Polkadot `#polkadot` - Polkadot App `#polkadot-app` - Polkadot Cloud `#polkadot-cloud` - Polkadot Desktop `#polkadot-desktop` - Polkadot Hub `#polkadot-hub` - Polkadot SDK `#polkadot-sdk` - Polkadot Virtual Machine (PVM) `#polkadot-virtual-machine-pvm` - Polkadot Web `#polkadot-web` - PoP Full `#pop-full` - PoP Lite `#pop-lite` - PoP Tier `#pop-tier` - Preimage `#preimage` - Product `#product` - Proof of Personhood (PoP) `#proof-of-personhood-pop` - pUSD `#pusd` - Recycler `#recycler` - Relay Chain `#relay-chain` - Ring-VRF `#ring-vrf` - Rococo `#rococo` - Runtime `#runtime` - Sandbox `#sandbox` - Session Public Key `#session-public-key` - Shield States `#shield-states` - Sign In with Polkadot `#sign-in-with-polkadot` - Signing Model `#signing-model` - Simple Concatenated Aggregate Little-Endian (SCALE) `#simple-concatenated-aggregate-little-endian-scale` - Slot `#slot` - Smoldot `#smoldot` - Sovereign Account `#sovereign-account` - Sr25519 `#sr25519` - SS58 Address Format `#ss58-address-format` - State Transition Function (STF) `#state-transition-function-stf` - Statement `#statement` - Statement Store `#statement-store` - Storage Item `#storage-item` - Substrate `#substrate` - Transaction `#transaction` - Transaction Era `#transaction-era` - Triangle `#triangle` - Triangle User-Agent Programming Interface (TrUAPI) `#triangle-user-agent-programming-interface-truapi` - Trie (Patricia Merkle Tree) `#trie-patricia-merkle-tree` - Validator `#validator` - WebAssembly (Wasm) `#webassembly-wasm` - Weight `#weight` - Westend `#westend` --- ## HOP Recipient Journey https://docs.polkadot.com/reference/apps/infrastructure/hop/recipient.md The receiving side of a HOP transfer — observing the incoming hop on the destination chain, validating the proof, and settling the resulting state. ### Sections - Introduction `#introduction` - The Flow at a Glance `#the-flow-at-a-glance` - What the Recipient's Product Sees `#what-the-recipients-product-sees` - Where to Go Next `#where-to-go-next` --- ## HOP Reference https://docs.polkadot.com/reference/apps/infrastructure/hop.md Reference for HOP — Polkadot's cross-chain hop protocol that moves assets and messages between chains, with current maturity-state caveats clearly flagged. ### Sections - Introduction `#introduction` - Where HOP Fits `#where-hop-fits` - Where to Go Next `#where-to-go-next` --- ## HOP Sender Journey https://docs.polkadot.com/reference/apps/infrastructure/hop/sender.md The sender side of a HOP transfer — dispatching a multi-hop send, tracking it as it routes through intermediate chains, and observing the final outcome. ### Sections - Introduction `#introduction` - The Flow at a Glance `#the-flow-at-a-glance` - What Can Go Wrong `#what-can-go-wrong` - Where to Go Next `#where-to-go-next` --- ## Host API on Polkadot Web https://docs.polkadot.com/reference/apps/hosts/polkadot-web/host-api.md Reference for the TrUAPI Host API surface exposed by Polkadot Web, including shared Desktop behavior and where browser-context behavior differs. ### Sections - Introduction `#introduction` - What Is the Same `#what-is-the-same` - Where Browser-Context Differs `#where-browser-context-differs` - Where to Go Next `#where-to-go-next` --- ## How HOP Works https://docs.polkadot.com/reference/apps/infrastructure/hop/how-it-works.md The HOP protocol's conceptual model — what a hop is, how multi-hop routing is constructed, and how the verifier model proves cross-chain correctness. ### Sections - Introduction `#introduction` - What a Single Hop Is `#what-a-single-hop-is` - How Multi-Hop Routing Is Constructed `#how-multi-hop-routing-is-constructed` - The Verifier Model `#the-verifier-model` - What a Product Sees `#what-a-product-sees` - Where to Go Next `#where-to-go-next` --- ## JSON-RPC APIs https://docs.polkadot.com/smart-contracts/for-eth-devs/json-rpc-apis.md JSON-RPC APIs guide for Polkadot Hub, covering supported methods, parameters, and examples for interacting with the chain. ### Sections - Introduction `#introduction` - Available Methods `#available-methods` - eth_accounts `#eth_accounts` - eth_blockNumber `#eth_blocknumber` - eth_call `#eth_call` - eth_chainId `#eth_chainid` - eth_estimateGas `#eth_estimategas` - eth_gasPrice `#eth_gasprice` - eth_getBalance `#eth_getbalance` - eth_getBlockByHash `#eth_getblockbyhash` - eth_getBlockByNumber `#eth_getblockbynumber` - eth_getBlockTransactionCountByNumber `#eth_getblocktransactioncountbynumber` - eth_getBlockTransactionCountByHash `#eth_getblocktransactioncountbyhash` - eth_getCode `#eth_getcode` - eth_getLogs `#eth_getlogs` - eth_getStorageAt `#eth_getstorageat` - eth_getTransactionCount `#eth_gettransactioncount` - eth_getTransactionByHash `#eth_gettransactionbyhash` - eth_getTransactionByBlockNumberAndIndex `#eth_gettransactionbyblocknumberandindex` - eth_getTransactionByBlockHashAndIndex `#eth_gettransactionbyblockhashandindex` - eth_getTransactionReceipt `#eth_gettransactionreceipt` - eth_maxPriorityFeePerGas `#eth_maxpriorityfeepergas` - eth_sendRawTransaction `#eth_sendrawtransaction` - eth_sendTransaction `#eth_sendtransaction` - eth_syncing `#eth_syncing` - net_listening `#net_listening` - net_peerCount `#net_peercount` - net_version `#net_version` - system_health `#system_health` - web3_clientVersion `#web3_clientversion` - debug_traceBlockByNumber `#debug_traceblockbynumber` - debug_traceTransaction `#debug_tracetransaction` - debug_traceCall `#debug_tracecall` - Response Format `#response-format` - Error Handling `#error-handling` --- ## Local Storage Method Group https://docs.polkadot.com/reference/apps/protocol/truapi/local-storage.md TrUAPI Local Storage method group for per-Product, per-device key-value persistence, Host-managed namespaces, JSON helpers, and KvStore use. ### Sections - Introduction `#introduction` - Conceptual Contract `#conceptual-contract` - Where to Go Next `#where-to-go-next` --- ## Name Transfers https://docs.polkadot.com/reference/apps/infrastructure/dotns/transfer.md Transferring ownership of a .dot name to another account — the flow, the validation rules, and what changes on the new owner's side. ### Sections - Introduction `#introduction` - What Changes on Transfer `#what-changes-on-transfer` - When the Tier Lock Matters `#when-the-tier-lock-matters` - What a Product Should Know `#what-a-product-should-know` - Where to Go Next `#where-to-go-next` --- ## Networks https://docs.polkadot.com/reference/parachains/networks.md Explore Polkadot's networks, with Paseo as the official Polkadot TestNet for parachain and dApp development, plus Kusama and Westend for specialized use cases. ### Sections - Introduction `#introduction` - Network Overview `#network-overview` - Recommended Development Path `#recommended-development-path` - Alternative Networks `#alternative-networks` - Polkadot MainNet `#polkadot-mainnet` - Polkadot TestNet (Paseo) `#polkadot-testnet-paseo` - Other Networks `#other-networks` - Kusama Network `#kusama-network` - Westend `#westend` - Local Test Networks `#local-test-networks` - Zombienet `#zombienet` - Chopsticks `#chopsticks` --- ## On-Chain polkadot.com https://docs.polkadot.com/reference/apps/hosts/polkadot-web/onchain-polkadot-com.md Reference for the on-chain-published presence backing polkadot.com discovery, a Polkadot Product that indexes and points at other Polkadot Products. ### Sections - Introduction `#introduction` - Why an On-Chain Discovery Layer `#why-an-on-chain-discovery-layer` - Implications for a Product Developer `#implications-for-a-product-developer` - Where to Go Next `#where-to-go-next` --- ## pallet-coinage Reference https://docs.polkadot.com/reference/apps/infrastructure/pop/pallet-coinage.md The PoP pallet behind the Polkadot App's Coinage feature — personhood-aware peer-to-peer payments with privacy properties beyond a standard Balances transfer. ### Sections - Introduction `#introduction` - Conceptual Surface `#conceptual-surface` - Relationship to Coinage in the App `#relationship-to-coinage-in-the-app` - Pallet Surface `#pallet-surface` - Where to Go Next `#where-to-go-next` --- ## pallet-game Reference https://docs.polkadot.com/reference/apps/infrastructure/pop/pallet-game.md The PoP pallet for personhood-gated on-chain games and randomized selection — fair-draw mechanics that rely on Ring-VRF aliases for unique participation. ### Sections - Introduction `#introduction` - What the Pallet Guarantees `#what-the-pallet-guarantees` - What a Product Uses It For `#what-a-product-uses-it-for` - Where to Go Next `#where-to-go-next` --- ## pallet-identity Reference https://docs.polkadot.com/reference/apps/infrastructure/pop/pallet-identity.md The People Chain identity record associated with a PoP account — what it stores, how it relates to aliases, and how a Product reads from it. ### Sections - Introduction `#introduction` - What the Pallet Records `#what-the-pallet-records` - Identity vs. Aliases `#identity-vs-aliases` - When to Use From a Product `#when-to-use-from-a-product` - Where to Go Next `#where-to-go-next` --- ## pallet-people Reference https://docs.polkadot.com/reference/apps/infrastructure/pop/pallet-people.md The foundational Proof of Personhood pallet — personhood registration, ring membership, alias issuance, and the under_alias runtime origin. ### Sections - Introduction `#introduction` - Ring Membership `#ring-membership` - Alias Issuance `#alias-issuance` - `under_alias` Dispatch `#under_alias-dispatch` - Pallets That Depend on This One `#pallets-that-depend-on-this-one` - Where to Go Next `#where-to-go-next` --- ## pallet-score Reference https://docs.polkadot.com/reference/apps/infrastructure/pop/pallet-score.md The PoP pallet for personhood-anchored reputation and scoring — per-alias scores that accumulate while staying unlinkable to user accounts. ### Sections - Introduction `#introduction` - What the Pallet Records `#what-the-pallet-records` - Read and Write Paths `#read-and-write-paths` - Use Cases `#use-cases` - Where to Go Next `#where-to-go-next` --- ## pallet-ubc Reference https://docs.polkadot.com/reference/apps/infrastructure/pop/pallet-ubc.md The Universal Basic Capacity pallet — per-person on-chain capacity primitives, including the periodic fee-free transaction quota for verified persons. ### Sections - Introduction `#introduction` - What the Pallet Provides `#what-the-pallet-provides` - When a Product Reaches for UBC `#when-a-product-reaches-for-ubc` - Eligibility Constraints `#eligibility-constraints` - Where to Go Next `#where-to-go-next` --- ## Payment Method Group https://docs.polkadot.com/reference/apps/protocol/truapi/payment.md TrUAPI method group for payment flows, including the standard Balances transfer surface and the Pocket peer-to-peer flow for Product payments. ### Sections - Introduction `#introduction` - Conceptual Contract `#conceptual-contract` - Where to Go Next `#where-to-go-next` --- ## Permissions in Polkadot Desktop https://docs.polkadot.com/reference/apps/hosts/polkadot-desktop/permissions.md Reference for how Polkadot Desktop enforces sandbox permissions a Product declares, including capability types, manifest declaration, and denial UX. ### Sections - Introduction `#introduction` - Capability Types `#capability-types` - Declaring Permissions `#declaring-permissions` - Denial UX `#denial-ux` - Where to Go Next `#where-to-go-next` --- ## Permissions Method Group https://docs.polkadot.com/reference/apps/protocol/truapi/permissions.md TrUAPI method group for declaring, querying, and gating on Product capabilities, including the ChainSubmit, ExternalRequest, and Microphone surfaces. ### Sections - Introduction `#introduction` - Conceptual Contract `#conceptual-contract` - Where to Go Next `#where-to-go-next` --- ## Pocket Recipient in the Polkadot App https://docs.polkadot.com/reference/apps/hosts/polkadot-app/pocket.md Reference for how the Polkadot App receives a Pocket transfer initiated from Desktop, including the recipient-side flow for funds or assets. ### Sections - Introduction `#introduction` - Conceptual Model `#conceptual-model` - Where to Go Next `#where-to-go-next` --- ## Pocket Send Flow in Polkadot Desktop https://docs.polkadot.com/reference/apps/hosts/polkadot-desktop/pocket.md Reference for Pocket, Polkadot Desktop's peer-to-peer send flow with personhood-aware addressing, and how it pairs with the App-side recipient view. ### Sections - Introduction `#introduction` - Conceptual Model `#conceptual-model` - What the User Sees `#what-the-user-sees` - Where to Go Next `#where-to-go-next` --- ## Polkadot App Reference https://docs.polkadot.com/reference/apps/hosts/polkadot-app.md Reference for the Polkadot App, the mobile Host in the Triangle that holds the user's signing key, runs PoP, and approves every Product transaction. ### Sections - Introduction `#introduction` - How It Works `#how-it-works` - Where the App Fits in the SDK Surface `#where-the-app-fits-in-the-sdk-surface` - Where to Go Next `#where-to-go-next` --- ## Polkadot Desktop Reference https://docs.polkadot.com/reference/apps/hosts/polkadot-desktop.md Reference for Polkadot Desktop, the desktop Host that loads Products by .dot name, mediates signing to the App, and enforces sandbox permissions. ### Sections - Introduction `#introduction` - How It Works `#how-it-works` - Where Desktop Fits in the SDK Surface `#where-desktop-fits-in-the-sdk-surface` - Where to Go Next `#where-to-go-next` --- ## Polkadot Product Skills https://docs.polkadot.com/reference/apps/skills.md Reference for the product-sdk skills — modular instructions that teach an AI agent how to work effectively across the Polkadot Products stack. ### Sections - Introduction `#introduction` - Skills List `#skills-list` - How to Install `#how-to-install` - Updating `#updating` - Where to Go Next `#where-to-go-next` --- ## Polkadot Web Reference https://docs.polkadot.com/reference/apps/hosts/polkadot-web.md Reference for Polkadot Web (dot.li), the browser-based Host that loads Polkadot Products by their .dot name without requiring a desktop installation. ### Sections - Introduction `#introduction` - Architecture `#architecture` - Visiting and Shield States `#visiting-and-shield-states` - Host API on Web `#host-api-on-web` - On-Chain `polkadot.com` `#on-chain-polkadotcom` - Upload Journeys `#upload-journeys` - Where to Go Next `#where-to-go-next` --- ## PopRules and dotNS Pricing https://docs.polkadot.com/reference/apps/infrastructure/dotns/poprules-pricing.md The pricing ladder for .dot name registration — who can register what name length at what cost, organized by PoP tier and suffix shape. ### Sections - Introduction `#introduction` - The Two PoP Tiers `#the-two-pop-tiers` - The Pricing Ladder `#the-pricing-ladder` - Lite → Full Migration Reservation `#lite-full-migration-reservation` - Where to Go Next `#where-to-go-next` --- ## Preimage Method Group https://docs.polkadot.com/reference/apps/protocol/truapi/preimage.md TrUAPI method group for submitting off-chain content that on-chain operations dereference by hash, with preimage and Statement Store distinction. ### Sections - Introduction `#introduction` - Conceptual Contract `#conceptual-contract` - Where to Go Next `#where-to-go-next` --- ## Preimage Submission via Polkadot Desktop https://docs.polkadot.com/reference/apps/hosts/polkadot-desktop/preimage.md Reference for how Polkadot Desktop mediates preimage submission for Products, and the Statement vs Preimage distinction for off-chain content. ### Sections - Introduction `#introduction` - What the Preimage Surface Does `#what-the-preimage-surface-does` - Statement vs Preimage `#statement-vs-preimage` - Where to Go Next `#where-to-go-next` --- ## Proof of Personhood in the Polkadot App https://docs.polkadot.com/reference/apps/hosts/polkadot-app/pop.md Reference for how the Polkadot App runs Proof of Personhood, with biometric verification, Ring-VRF aliases on People Chain, and the PoP tier model. ### Sections - Introduction `#introduction` - Ring-VRF Aliases `#ring-vrf-aliases` - PoP Tiers: Full vs. Lite `#pop-tiers-full-vs-lite` - What This Unlocks for a Product `#what-this-unlocks-for-a-product` - Where to Go Next `#where-to-go-next` --- ## Proof of Personhood Reference https://docs.polkadot.com/reference/apps/infrastructure/pop.md Reference for Polkadot's Proof of Personhood infrastructure — Ring-VRF and aliases, plus per-pallet documentation for the pallets that gate logic on personhood. ### Sections - Introduction `#introduction` - The Mechanism `#the-mechanism` - The Pallets `#the-pallets` - Where to Go Next `#where-to-go-next` --- ## Ring-VRF and Aliases https://docs.polkadot.com/reference/apps/infrastructure/pop/ring-vrf-and-aliases.md How Polkadot's Proof of Personhood produces unlinkable per-Product aliases with Ring-VRF, and how under_alias lets pallets gate on aliases. ### Sections - Introduction `#introduction` - What PoP Produces `#what-pop-produces` - What an Alias Is `#what-an-alias-is` - The `under_alias` Runtime Origin `#the-under_alias-runtime-origin` - Cross-Product Aliases `#cross-product-aliases` - Where to Go Next `#where-to-go-next` --- ## Sandbox and Sub-Accounts in TrUAPI https://docs.polkadot.com/reference/apps/protocol/truapi/sandbox.md Why a Polkadot Product gets a per-domain sub-account, why the Host API is the only egress, and how permissions selectively relax that isolation. ### Sections - Introduction `#introduction` - Why Derived Sub-Accounts, Not Root Identity `#why-derived-sub-accounts-not-root-identity` - Why the Host API Is the Only Egress `#why-the-host-api-is-the-only-egress` - How Permissions Selectively Relax Isolation `#how-permissions-selectively-relax-isolation` - Where to Go Next `#where-to-go-next` --- ## Shield States in Polkadot Web https://docs.polkadot.com/reference/apps/hosts/polkadot-web/shield-states.md Reference for the shield-state UI in Polkadot Web, including how the Host surfaces the trust posture of the loaded Product and what each state means. ### Sections - Introduction `#introduction` - Conceptual Model `#conceptual-model` - Why Products Should Care `#why-products-should-care` - Where to Go Next `#where-to-go-next` --- ## Sign In with Polkadot https://docs.polkadot.com/reference/apps/hosts/polkadot-app/sign-in.md Reference for Sign In with Polkadot, the Host-level authentication handshake between Polkadot Desktop or Polkadot Web and the paired Polkadot App. ### Sections - Introduction `#introduction` - How the Handshake Works `#how-the-handshake-works` - Where Sign In Differs from Per-Transaction Signing `#where-sign-in-differs-from-per-transaction-signing` - Where to Go Next `#where-to-go-next` --- ## Signing in Polkadot Desktop https://docs.polkadot.com/reference/apps/hosts/polkadot-desktop/signing.md Reference for how Polkadot Desktop mediates transaction signing, including the App signer, ChainSubmit permission, approval, timeout, and rejection. ### Sections - Introduction `#introduction` - The Three-Actor Model `#the-three-actor-model` - `ChainSubmit`: Ability to Request ≠ Auto-Sign `#chainsubmit-ability-to-request-auto-sign` - What the User Sees `#what-the-user-sees` - Asynchronous Approval and Timeouts `#asynchronous-approval-and-timeouts` - Where to Go Next `#where-to-go-next` --- ## Signing Method Group https://docs.polkadot.com/reference/apps/protocol/truapi/signing.md TrUAPI method group for dispatching transactions through the Host to the paired Polkadot App for per-transaction approval, signing, and results. ### Sections - Introduction `#introduction` - Conceptual Contract `#conceptual-contract` - Auto-Signing `#auto-signing` - Where to Go Next `#where-to-go-next` --- ## Statement Lifecycle https://docs.polkadot.com/reference/apps/infrastructure/statement-store/lifecycle.md How a Statement Store submission moves through validation, gossip propagation, TTL expiry, and eviction — and what each step guarantees. ### Sections - Introduction `#introduction` - The Five Steps `#the-five-steps` - What Each Step Guarantees `#what-each-step-guarantees` - On-Chain Trigger (Forthcoming) `#on-chain-trigger-forthcoming` - Where to Go Next `#where-to-go-next` --- ## Statement Store Allowance https://docs.polkadot.com/reference/apps/infrastructure/statement-store/allowance.md How per-account statement quota is enforced — max_count for live statements and max_size for total bytes — and why submissions are gated rather than fee-priced. ### Sections - Introduction `#introduction` - What an Allowance Records `#what-an-allowance-records` - How the Limits Interact `#how-the-limits-interact` - Per-Statement Size Limit `#per-statement-size-limit` - Provisioning on TestNet `#provisioning-on-testnet` - Where to Go Next `#where-to-go-next` --- ## Statement Store Channels https://docs.polkadot.com/reference/apps/infrastructure/statement-store/channels.md The last-write-wins primitive on top of statements — a channel field causes the pallet to replace older entries from the same account on the same channel. ### Sections - Introduction `#introduction` - When to Reach for Channels `#when-to-reach-for-channels` - Scope and Replacement Rules `#scope-and-replacement-rules` - The Channel-Store API `#the-channel-store-api` - Where to Go Next `#where-to-go-next` --- ## Statement Store Method Group https://docs.polkadot.com/reference/apps/protocol/truapi/statement-store.md TrUAPI method group for publishing and subscribing to gossip-distributed signed statements on the People Chain through the Host and SDK client. ### Sections - Introduction `#introduction` - Conceptual Contract `#conceptual-contract` - Where to Go Next `#where-to-go-next` --- ## Statement Store Reference https://docs.polkadot.com/reference/apps/infrastructure/statement-store.md Reference for the Statement Store — Polkadot's network-layer pub/sub primitive on the People Chain, with on-chain rules and off-chain payloads via gossip. ### Sections - Introduction `#introduction` - How a Statement Reaches Subscribers `#how-a-statement-reaches-subscribers` - Delivery Semantics `#delivery-semantics` - Where to Go Next `#where-to-go-next` --- ## Statement Store Subscriptions https://docs.polkadot.com/reference/apps/infrastructure/statement-store/subscriptions.md How a subscriber registers a topic filter against the People Chain node — primary topic, optional secondary topic, dedup behavior, and unsubscription. ### Sections - Introduction `#introduction` - How Topics Filter `#how-topics-filter` - What the Callback Receives `#what-the-callback-receives` - Subscription Lifecycle `#subscription-lifecycle` - Initial-State Behavior `#initial-state-behavior` - Where to Go Next `#where-to-go-next` --- ## Statement Store via Polkadot Desktop's Host API https://docs.polkadot.com/reference/apps/hosts/polkadot-desktop/statement-store.md Reference for how Polkadot Desktop mediates Statement Store access, including proof routing, account context, and Bulletin Chain composition pattern. ### Sections - Introduction `#introduction` - What Desktop Adds `#what-desktop-adds` - What Desktop Does Not Do `#what-desktop-does-not-do` - Composition with the Bulletin Chain `#composition-with-the-bulletin-chain` - Where to Go Next `#where-to-go-next` --- ## Technical Reference Overview https://docs.polkadot.com/reference.md Learn about Polkadot's technical architecture, governance framework, parachain ecosystem, and the tools you need to build and interact with the network. ### Sections - Introduction `#introduction` - Polkadot Hub `#polkadot-hub` - Parachains `#parachains` - On-Chain Governance `#on-chain-governance` - Glossary `#glossary` - Tools `#tools` - Where to Go Next `#where-to-go-next` --- ## The .dot Name Mechanism https://docs.polkadot.com/reference/apps/infrastructure/dotns/name-mechanism.md How a .dot name resolves to a Polkadot Product — namehash derivation, contenthash to CID mapping, and the IPFS gateway and Bulletin Chain delivery path. ### Sections - Introduction `#introduction` - Layer 1: The Registry on Asset Hub `#layer-1-the-registry-on-asset-hub` - Layer 2: Namehash Derivation `#layer-2-namehash-derivation` - Layer 3: `contenthash` → CID `#layer-3-contenthash-cid` - Layer 4: Delivery (IPFS Gateway or Bulletin Peer-to-Peer) `#layer-4-delivery-ipfs-gateway-or-bulletin-peer-to-peer` - End-to-End Resolution `#end-to-end-resolution` - Where to Go Next `#where-to-go-next` --- ## TrUAPI Calls Method Group https://docs.polkadot.com/reference/apps/protocol/truapi/calls.md The lifecycle calls a Product uses to identify itself to its Host, the Host capability introduction, and the setup every TrUAPI group relies on. ### Sections - Introduction `#introduction` - Conceptual Contract `#conceptual-contract` - Where to Go Next `#where-to-go-next` --- ## TrUAPI Packages https://docs.polkadot.com/reference/apps/protocol/truapi/packages.md Which SDK package wraps which TrUAPI method group, and where the boundary between Product code and Host code lives in the package reference. ### Sections - Introduction `#introduction` - Package Map `#package-map` - The Boundary Between Product Code and Host Code `#the-boundary-between-product-code-and-host-code` - Where to Go Next `#where-to-go-next` --- ## TrUAPI Reference https://docs.polkadot.com/reference/apps/protocol/truapi.md TrUAPI is the protocol between Polkadot Hosts and the Products that run inside them, covering signing, chain interaction, storage, and messaging. ### Sections - Introduction `#introduction` - Two Audiences `#two-audiences` - The Eleven Method Groups `#the-eleven-method-groups` - High-Level Diagram `#high-level-diagram` - Where to Go Next `#where-to-go-next` --- ## TrUAPI Versioning https://docs.polkadot.com/reference/apps/protocol/truapi/versioning.md How TrUAPI versions evolve, what compatibility a Product can rely on across Host versions, and how to target a specific version range safely. ### Sections - Introduction `#introduction` - What a Version Number Identifies `#what-a-version-number-identifies` - What a Product Targets `#what-a-product-targets` - How the SDK Maps to Versions `#how-the-sdk-maps-to-versions` - Where to Go Next `#where-to-go-next` --- ## Visiting a Product on Polkadot Web https://docs.polkadot.com/reference/apps/hosts/polkadot-web/visiting.md How Polkadot Web resolves a .dot name and loads the resulting Product inside a browser tab, including the visiting flow that differs from Desktop. ### Sections - Introduction `#introduction` - The Visiting Flow `#the-visiting-flow` - How This Differs from Polkadot Desktop `#how-this-differs-from-polkadot-desktop` - Where to Go Next `#where-to-go-next`