One World Chain Token Docs
  • Summary
  • DOCUMENTATION
    • Learn about the OWCT Platform
      • OWCT Overview: vision, strategy and platform components
      • The OWCT Blockchain
        • Discovering the Network
        • OWCT Consensus
        • Delegation through Staking with Validators
        • Ethereum (EVM) Compatibility and Smart Contracts
        • Boosting OWCT's Scalability
      • OWCT
        • OWCT Tokenomics
        • Wallets Supporting OWCT
        • OWCT on Other Chains
      • Interoperability
      • OWCT Governance and Development
        • OWCT Assembly
    • OWCT for Business
  • Developers
    • Network Details
      • OWCT Mainnet
      • OWCT Testnet
      • Token Faucets
      • Network Upgrades
        • Upgrade Guide
        • Upgrade Guide (explorer nodes)
        • Block 13,800,000 Fork
        • FIP's
    • OWCT Consensus
      • Contracts Overview
      • Stake, Delegate and Withdraw
      • Vote
      • End-of-Cycle Flow
      • Contract Addresses
    • How to run network nodes
    • Resources & Tools
      • TheGraph
      • WalletConnect on OWCT
    • Important smart contracts
      • OWCT Token
      • OWCT Dollar
      • Major Deployed Contracts
      • Bridges
        • OWCT (Mainnet) <=> OWCT (ETH)
        • OWCT (Mainnet) <=> OWCT (BSC)
        • OWCT (Mainnet) <=> OWCT (BASE)
        • ETH (Ethereum network) <=> ETH (OWCT network)
        • USDT (Ethereum network) <=> USDT (OWCT network)
        • USDC (Ethereum network) <=> USDC (OWCT network)
        • BNB (Binance network) <=> BNB (OWCT network)
    • How to become a validator
      • Getting started as a validator
      • Getting started on the OWCT testnet
  • Links
    • Discord
    • Facebook
    • GitHub
    • LinkedIn
    • Medium
    • Telegram
    • Twitter
    • YouTube
Powered by GitBook
On this page
  1. Developers
  2. Resources & Tools

WalletConnect on OWCT

PreviousTheGraphNextImportant smart contracts

Last updated 1 year ago

is an open-source protocol for data exchange between wallets and decentralized applications (dApps). The process takes place via a specialized server and the flow of data is encrypted in both directions.

From the user’s perspective, although the exact details may vary from wallet to wallet, there are two ways of using WalletConnect. In the mobile-to-mobile mode, the user opens the website of the dApp that they are interested in, clicks the “connect wallet” tab there and chooses their preferred wallet. The desktop-to-mobile approach involves using the Wallet Connect-enabled wallet on the mobile phone to scan the QR code of the dApp displayed in the desktop browser. After the session, the dApp may be disconnected, and users are even advised to disconnect dApps for security reasons.

For developers who wish to integrate the WalletConnect functionality into their dApps running on OWCT, we recommend using .

WalletConnect
this library