Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia Ethereum · Entry 233

WalletConnect sessions: pairing a wallet with an application

AI-assisted research · separate automated verificationCorrections

Theme
Ethereum
Sources
4 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for WalletConnect sessions: pairing a wallet with an application
FactDetailSource
ProposalThe application requests session capabilities.[1]
ApprovalThe wallet controls whether the proposed session is accepted.[1]
Separate stateOnchain operator approval belongs to the token contract.[3]
01

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.

02

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.

03

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.

Direct answers

Questions people ask

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.

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.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

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: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Proposal: The application requests session capabilities.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Approval: The wallet controls whether the proposed session is accepted.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Separate state: Onchain operator approval belongs to the token contract.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and separate automated verification.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. WalletConnect Sign conceptsWalletConnect

    Session negotiation, supported chains/methods/accounts and request permission boundaries.

    Locator: Session proposal; namespaces; session requests · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:24.458ZOpen source
  2. NamespacesWalletConnect 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 · Version / scope: WalletConnect Sign v2 documentation retrieved 2 October 2026 · Retrieved: 2026-10-02T19:20:32.372ZOpen source
  3. ERC-721 NFT standardEthereum Improvement Proposals

    Ownership, receiver checks, token-level and operator approvals, mint/burn event semantics.

    Locator: safeTransferFrom; approve; setApprovalForAll; Transfer; metadata · Version / scope: ERC-721 · Retrieved: 2026-10-02T18:55:25.399ZOpen source
  4. Ethereum security and scam preventionethereum.org contributors

    Primary community guidance on wallet secrets, phishing, malicious sites and transaction checking.

    Locator: Wallet security; common scams; hardware wallets · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:24.140ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

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/