Igra Labs says Tangem wallet version 6.1.3 can connect to the Igra application ecosystem through WalletConnect, giving Tangem users a hardware-backed route into Kaspa-native decentralised applications. Users retain control of their keys in the Tangem wallet while approving requests initiated by an Igra application (Igra Labs).
The integration changes the access layer rather than moving custody into Igra. WalletConnect passes an application request to the wallet, where the user can inspect and approve it. Tangem remains responsible for key storage and signing, while Igra applications provide the transaction or application flow. Igra described the release as bringing Kaspa-native DeFi to more than one million Tangem users and told users to upgrade to Tangem 6.1.3.
Hardware-wallet access has been a recurring constraint for emerging application ecosystems. A web wallet can integrate a new transaction format quickly, but users who keep keys on a dedicated signing device need compatible session handling, transaction presentation and approval. WalletConnect provides a familiar bridge between those surfaces without asking the application to receive a seed phrase or private key.
For Igra, the change puts its application layer in front of an existing wallet user base instead of requiring a separate account or imported key. For Tangem users, it creates a route from custody into applications while preserving the wallet as the approval boundary. That distinction matters for any DeFi interaction because connecting a wallet is not the same as granting an application unrestricted control.
The first-party announcement confirms the Igra side of the rollout and names Tangem 6.1.3 as the required version. It does not provide a detailed compatibility matrix for every Igra application or transaction type. Users should verify the requested network, contract or covenant operation and transaction details inside Tangem before signing, and should begin with small values while the integration is new.
The rollout also does not remove application risk. Hardware-backed signing protects the private key from being handed to a website, but it cannot determine whether a transaction is economically sound or whether the connected application behaves as expected. Wallet prompts need to expose enough detail for users to recognise what they are approving.
Igra previously required users to reach its applications through compatible software-wallet flows. WalletConnect support in a current Tangem build broadens that route to hardware-backed accounts and gives Kaspa-native applications another standard connection surface. Adoption will depend on how clearly Tangem presents Igra transaction requests and how consistently individual applications support the connection, but the access path is now available according to Igra Labs.
