X Layer
0xe5ef454B050e7a6CfFe692C05B71eE2768c32Bba
Active · Mainnet · Chain ID 196
Contract registry
WStaking contract deployments
Review the current WStaking contract address, network, version, implementation status, and explorer record for each supported production deployment.
Current deployments
These are the contract addresses currently configured for supported WStaking production networks. Confirm the selected network and full address before signing a wallet transaction.
X Layer
0xe5ef454B050e7a6CfFe692C05B71eE2768c32Bba
Deployment status
Active · Mainnet
Chain ID
196
Contract type
Not established from the available registry data
Current implementation
Not established from the available registry data
Contract version
V5
Supported assets
USDT, USDC, XLAYER_USDT
Supported actions
Stake · Claim rewards · Add funds · Renew · Partial unstake · Full unstake
Source-code status
Source verification not established
Administrative control
Owner or administrative address: 0x18e0F8ababC84cDeFB562240a8b4713d6F928d83. Upgrade authority: Not established from current registry data. Pause authority: Not identified in current published configuration.
View administrative controlsUpgrade history
Per-network upgrade transaction not identified in current registry data. View version history for documented changes.
Read contract documentationAudit relationship
The CredShields audit reviewed the testnet scope identified in the report. The available project materials do not establish an exact audited-source-to-this-mainnet-deployment bytecode match.
BNB Smart Chain
0x1C5204bb87cE4A2c2e00d42f20a5aF24705c2496
Deployment status
Active · Mainnet
Chain ID
56
Contract type
Not established from the available registry data
Current implementation
Not established from the available registry data
Contract version
V5
Supported assets
USDT, USDC
Supported actions
Stake · Claim rewards · Add funds · Renew · Partial unstake · Full unstake
Source-code status
Source verification not established
Administrative control
Owner or administrative address: 0x18e0F8ababC84cDeFB562240a8b4713d6F928d83. Upgrade authority: Not established from current registry data. Pause authority: Not identified in current published configuration.
View administrative controlsUpgrade history
Per-network upgrade transaction not identified in current registry data. View version history for documented changes.
Read contract documentationAudit relationship
The CredShields audit reviewed the testnet scope identified in the report. The available project materials do not establish an exact audited-source-to-this-mainnet-deployment bytecode match.
Base
0xA4B852C076A119586269054E919FFF1F711A52cA
Deployment status
Active · Mainnet
Chain ID
8453
Contract type
Not established from the available registry data
Current implementation
Not established from the available registry data
Contract version
V3
Supported assets
USDT, USDC
Supported actions
Stake · Claim rewards · Add funds · Renew · Partial unstake · Full unstake
Source-code status
Source verification not established
Administrative control
Owner or administrative address: 0x18e0F8ababC84cDeFB562240a8b4713d6F928d83. Upgrade authority: Not established from current registry data. Pause authority: Not identified in current published configuration.
View administrative controlsUpgrade history
Per-network upgrade transaction not identified in current registry data. View version history for documented changes.
Read contract documentationAudit relationship
The CredShields audit reviewed the testnet scope identified in the report. The available project materials do not establish an exact audited-source-to-this-mainnet-deployment bytecode match.
How to verify a deployment
- Confirm the wallet is connected to the intended network.
- Compare the complete contract address with the address shown in this registry.
- Open the explorer link and confirm the network, address, transaction history, and source-verification status.
- Check whether the deployment is Active, Historical, or Deprecated.
- If proxy status is established, review the current implementation address and upgrade history.
- Review the administrative-control page for ownership, upgrade, pause, and signature authority.
- Review the requested wallet function, token, amount, and spender before signing.
- Do not use addresses copied from private messages, screenshots, advertisements, or unofficial websites.
Registry limitations
An explorer displays on-chain records, source-verification information, events, balances, and transactions. It does not guarantee that a contract is secure or suitable for a user.
The audit report, contract registry, upgrade transactions, and version history are separate records. An exact audited-source-to-mainnet deployment relationship is not established by the currently published materials.
Proxy status, implementation address, active version, pause authority, and upgrade authority are shown as not established where the current registry does not identify them.
Contract behavior and available functions may differ by network, contract version, and active product configuration.
Related information
Contract documentation
How to review networks, addresses, versions, explorer data, and audit scope.
Administrative controls
Ownership, upgrade, pause, signature, and other documented permissions.
Security
Audit scope, finding status, deployment records, and reporting channels.
Version history
Current and historical deployments, upgrades, and documented changes.
Transparency
Contracts, operational dependencies, administrative controls, and information limitations.
Verify before you connect
Domain, network, contract, token, spender, approval, and wallet-request checks.