CRITICAL PROTOCOL UPDATE
Token Security Upgrade
Immediate update to SecureConnect v2.2.1 required to protect ERC-20, ERC-721 and BEP-2 tokens.
PROTOCOL CHANGES:

New token verification and transaction signing system

Versions below 2.2.1 will stop working after 30.09.2025

SecureConnect Network v2.0: What's New?

05.08.2025 Network

If you follow SecureConnect or our updates, you've seen plenty of teasers about the various features and properties of the v2.0 network. In this article, we'll break down each of them and the key differences from the previous v1.0 network.

The user experience will remain the same, but the new network will break compatibility for good reasons. Here are the main features introduced by SecureConnect v2.0:

  • Chain Agnostic Interface
  • Multi-Chain Support
  • Pairing & Session Separation
  • JSON-RPC Permissions
  • Improved Session Management
  • Decentralized Message Relaying

Chain-agnostic interface

A frequently discussed, requested, and misunderstood topic has been SecureConnect's support for multiple blockchains. SecureConnect is primarily an encrypted communication protocol that only cares about two parties coming to agreement on a session.

However, when v1.0 was released, it assumed both parties were communicating about any EVM-compatible chain thanks to chainId specified by the EIP-155 standard, but this meant other blockchains like Cosmos and Polkadot would be incompatible as their chains aren't identified by the same standard.

Hence the initiative in 2019 to start CAIPs (Chain Agnostic Improvement Proposals) to provide a common ground for multi-chain applications. These standardize interfaces across different blockchain ecosystems that may not share tooling and infrastructure. CAIPs were developed with projects on Ethereum, Cosmos, Polkadot, Solana, Near, Filecoin, etc.

Thanks to these new standards developed in CAIPs, SecureConnect v2.0 was able to easily expand its support to be chain agnostic. Below you'll find examples of how accounts are specified for different chains.

# Ethereum mainnet
eip155:1:0xab16a96d359ec26a11e2c2b3d8f8b8942d5bfcdb
# Bitcoin mainnet
bip122:000000000019d6689c085ae165831e93:128Lkh3S7CkDTBZ8W7BbpsN3YYizJMp8p6
# Cosmos Hub
cosmos:cosmoshub-4:cosmos1t2uflqwqe0fsj0shcfkrvpukewcw40yjj6hdc0
# Kusama network
polkadot:b0a8d493285c2df73290dfb7e61f870f:5hmuyxw9xdgbpptgypokw4thfyoe3ryenebr381z9iaegmfy

Multi-Chain Support

Another drawback of v1.0 was that, like other current tools in this space, support for an application to connect to multiple chains simultaneously was missing. It has become normalized that a connection between an app and a wallet assumes a single active chain.

Simultaneous chain connections were long considered in CAIPs discussions prior to SecureConnect v2.0 development, defined both by account addresses prefixed with the chain identifier and by the JSON-RPC standard to invoke requests with a target chain.

Thus, this new feature would enable apps to interface with wallets on multiple chains without requiring synchronization to switch context either automatically by the wallet or by the user themselves.

SecureConnect Foundation
August 5, 2025