The decentralized infrastructure protocol powering WalletConnect's network with cross-chain token economics and governance.
WalletConnect Protocol is a comprehensive smart contract system that powers the decentralized WalletConnect network. The protocol introduces WCT (WalletConnect Token), a cross-chain governance and utility token that enables staking, rewards, and network participation across Ethereum, Optimism, and Solana.
Key features:
- Cross-chain token with native bridging via Wormhole NTT
- Vote-escrowed staking with time-weighted rewards (stWCT)
- Perpetual staking for long-term network alignment
- Infrastructure rewards for network participants
- Timelock governance with multi-signature controls
The protocol consists of several interconnected modules:
- WCT Token: ERC-20 governance token on Ethereum with Wormhole NTT integration
- L2WCT Token: L2-native token with transfer restrictions and staking capabilities
- StakeWeight: Vote-escrowed staking with time-weighted rewards and perpetual positions
- StakingRewardDistributor: Handles reward distribution to stakers
- Timelocks: 1-week admin timelock, 3-day manager timelock
- Pauser: Emergency pause functionality for critical contracts
- WalletConnectConfig: Central configuration registry
- Wormhole NTT: Native Token Transfer for Ethereum ↔ Optimism ↔ Solana bridging
- Rate Limits: Configurable transfer limits between chain pairs
- Bridge Security: Multi-signature controls and emergency pause capabilities
| Network | Chain ID | WCT Token | Documentation |
|---|---|---|---|
| Ethereum | 1 | 0xeF4461891DfB3AC8572cCf7C794664A8DD927945 |
Full Deployment |
| Optimism | 10 | 0xeF4461891DfB3AC8572cCf7C794664A8DD927945 |
Full Deployment |
| Solana | - | WCTk5xWdn5SYg56twGj32sUF3W4WFQ48ogezLBuYTBY |
Full Deployment |
For complete deployment addresses including staking contracts, governance, and bridges, see DEPLOYMENT_ADDRESSES.md.
- Foundry for smart contract development
- Node.js v18+ and pnpm for deployment scripts
- Environment variables (see
.common.example.env)
# Clone the repository
git clone https://github.com/WalletConnect/contracts
cd contracts
# Install dependencies
cd evm && forge install
# Copy environment variables
cp .common.example.env .common.env
# Edit .common.env with your API keys# Compile contracts
forge build
# Generate documentation
forge doc# Run all tests
forge test
# Run specific test suites
forge test --match-path test/unit # Unit tests
forge test --match-path test/integration # Integration tests
forge test --match-path test/invariant # Invariant tests
forge test --match-path test/fork # Fork tests (requires RPC)
# Run with coverage
forge coverage
# Gas reporting
forge test --gas-reportDeployment scripts use Foundry's forge script system:
# Deploy to testnet
forge script script/deploy/OptimismDeploy.s.sol --rpc-url sepolia --broadcast
# Deploy to mainnet (requires hardware wallet)
forge script script/deploy/OptimismDeploy.s.sol --rpc-url optimism --broadcast --ledgerSee deployment scripts for network-specific deployments.
- All contracts use OpenZeppelin's battle-tested implementations
- Comprehensive test coverage including unit, integration, and invariant tests
- Timelock governance with multi-signature controls
- Emergency pause functionality on critical operations
- Rate-limited cross-chain transfers
We welcome contributions! Please see CONTRIBUTING.md for guidelines.
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Write tests for your changes
- Ensure all tests pass (
forge test) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
- Discord: Join our Discord
- Forum: Governance Forum
- Twitter: @walletconnect
- Blog: walletconnect.network/blog
- Technical Documentation - Smart contract architecture and design decisions
This project is licensed under the MIT License - see LICENSE.md for details.
Built with ❤️ by the WalletConnect team
