# WalletConnect sessions: pairing a wallet with an application WalletConnect lets an application propose a session with a wallet, including requested chains, methods and events. The wallet accepts or rejects that proposal and shares approved public-account information. A session establishes a communication channel; each later signing request still has its own meaning, and disconnecting it does not undo permissions already recorded onchain. Evidence: [WalletConnect Sign concepts](https://specs.walletconnect.com/2.0/specs/clients/sign/session-proposal); [Namespaces](https://specs.walletconnect.com/2.0/specs/clients/sign/namespaces); [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721) Canonical: https://degreesofsatoshi.com/encyclopedia/walletconnect-sessions/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Proposal:** The application requests session capabilities. ([WalletConnect Sign concepts](https://specs.walletconnect.com/2.0/specs/clients/sign/session-proposal)) - **Approval:** The wallet controls whether the proposed session is accepted. ([WalletConnect Sign concepts](https://specs.walletconnect.com/2.0/specs/clients/sign/session-proposal)) - **Separate state:** Onchain operator approval belongs to the token contract. ([ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721)) ## A QR code begins a connection flow The documented Sign flow uses a pairing link or QR code so the wallet and application can establish communication. The application then proposes namespaces describing the chains, methods and account capabilities it wants. Inspect the application identity and requested scope before accepting. A working connection does not verify the application’s business promises. Evidence: [WalletConnect Sign concepts](https://specs.walletconnect.com/2.0/specs/clients/sign/session-proposal); [Namespaces](https://specs.walletconnect.com/2.0/specs/clients/sign/namespaces) ## A connection and an NFT sale require different decisions Suppose a marketplace session is approved for one chain and your public account. It subsequently requests an NFT operator approval. That second request changes a contract permission if signed and executed; it is not merely another name for connecting. Check later messages individually. Session scope describes what the app may ask the wallet to do, rather than proving that every request is appropriate. Evidence: [WalletConnect Sign concepts](https://specs.walletconnect.com/2.0/specs/clients/sign/session-proposal); [Namespaces](https://specs.walletconnect.com/2.0/specs/clients/sign/namespaces); [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721) ## Close the channel and inspect lasting permissions separately Ending a session stops using that session for wallet communication. It does not call a token contract’s approval-revocation function or reverse an already executed transfer. When cleaning up an old connection, distinguish the session list from onchain approvals. A token operator granted earlier can remain authorized even if the marketplace no longer appears as connected. Evidence: [WalletConnect Sign concepts](https://specs.walletconnect.com/2.0/specs/clients/sign/session-proposal); [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721) ## Questions ### Does scanning a WalletConnect QR code transfer funds? The documented pairing and session proposal are connection steps. Any subsequent transaction or signature request should be evaluated separately before approval. Evidence: [WalletConnect Sign concepts](https://specs.walletconnect.com/2.0/specs/clients/sign/session-proposal) ### Does a session require revealing my seed phrase? No. The protocol negotiates a wallet session and approved accounts. A separate request for the recovery phrase is not part of that flow. Evidence: [WalletConnect Sign concepts](https://specs.walletconnect.com/2.0/specs/clients/sign/session-proposal); [Ethereum security and scam prevention](https://ethereum.org/en/security/) ## Claims and scope ### walletconnect-sessions-quick-answer WalletConnect lets an application propose a session with a wallet, including requested chains, methods and events. The wallet accepts or rejects that proposal and shares approved public-account information. A session establishes a communication channel; each later signing request still has its own meaning, and disconnecting it does not undo permissions already recorded onchain. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### walletconnect-sessions-fact-proposal Proposal: The application requests session capabilities. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### walletconnect-sessions-fact-approval Approval: The wallet controls whether the proposed session is accepted. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### walletconnect-sessions-fact-separate-state Separate state: Onchain operator approval belongs to the token contract. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [WalletConnect Sign concepts](https://specs.walletconnect.com/2.0/specs/clients/sign/session-proposal) — WalletConnect. Session negotiation, supported chains/methods/accounts and request permission boundaries. Locator: Session proposal; namespaces; session requests. Retrieved: 2026-10-02T18:55:24.458Z. - [Namespaces](https://specs.walletconnect.com/2.0/specs/clients/sign/namespaces) — WalletConnect specifications. Proposal and session namespace fields define requested chains, methods, events and approved accounts. Locator: Definition; Session Namespaces; Approving a Session Response; Rejecting a Session Response. Retrieved: 2026-10-02T19:20:32.372Z. - [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721) — Ethereum Improvement Proposals. Ownership, receiver checks, token-level and operator approvals, mint/burn event semantics. Locator: safeTransferFrom; approve; setApprovalForAll; Transfer; metadata. Retrieved: 2026-10-02T18:55:25.399Z. - [Ethereum security and scam prevention](https://ethereum.org/en/security/) — ethereum.org contributors. Primary community guidance on wallet secrets, phishing, malicious sites and transaction checking. Locator: Wallet security; common scams; hardware wallets. Retrieved: 2026-10-02T18:55:24.140Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “WalletConnect sessions: pairing a wallet with an application.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/walletconnect-sessions/