WStaking

    Contract references

    Supported networks and contracts

    Verify the WStaking contract address, network, and version before approving a staking or wallet transaction.

    Contract references

    Use only the contract address assigned to the selected network. An address used on one blockchain must not be treated as valid on another blockchain, even when the address format appears identical.

    • X Layer - Chain ID 196 - Active - OKLink: 0xe5ef454b050e7a6cffe692c05b71ee2768c32bba
    • Supported assets: USDT, USDC, and XLAYER_USDT. Supported actions: staking, reward claims, adding funds, renewal, partial unstaking, and full unstaking.
    • BNB Smart Chain - Chain ID 56 - Active - BscScan: 0x1C5204bb87cE4A2c2e00d42f20a5aF24705c2496
    • Supported assets: USDT and USDC. Supported actions: staking, reward claims, adding funds, renewal, partial unstaking, and full unstaking.
    • Base - Chain ID 8453 - Active - BaseScan: 0xA4B852C076A119586269054E919FFF1F711A52cA
    • Supported assets: USDT and USDC. Supported actions: staking, reward claims, adding funds, renewal, partial unstaking, and full unstaking.

    How to verify a contract

    Before interacting with a WStaking contract, complete the following checks:

    • Confirm the wallet is connected to the intended network.
    • Compare the complete contract address with the address shown on this page. Do not rely only on the first or last characters.
    • Open the address through the listed blockchain explorer and confirm that the network is correct.
    • Check whether the address is marked as active, historical, deprecated, or testnet.
    • Before signing, review the contract address, token, amount, requested function, and network fee shown in the wallet.
    • Do not use contract addresses copied from social-media posts, advertisements, search results, private messages, screenshots, or unofficial websites.

    Differences between networks and versions

    WStaking may use different contract versions on different supported networks. Available functions, staking terms, supported assets, and administrative permissions can differ between deployments.

    A newer contract version does not automatically replace every earlier deployment. Historical contracts may remain relevant for users whose positions were created through those addresses.

    Before creating a new position, confirm that the application is using the active contract for the selected network. For an existing position, use the contract associated with that position.

    Proxy or implementation status is not established for the deployments listed on this page, so no proxy-specific explanation is provided.

    Explorer verification and audit scope

    A blockchain explorer can display contract transactions, token transfers, events, balances, source-code verification status, and other on-chain records. It does not guarantee that a contract is secure or appropriate for a particular user.

    Source-code verification means that published source code can be compared with deployed bytecode. It is not equivalent to an independent security audit.

    Where an audit report is available, review the exact contract address, version, network, source revision, and scope stated in the report. An audit of one version must not be assumed to cover another deployment.

    Review the Security and Version History pages for audit limitations, contract changes, and historical deployments.

    Related information

    Security

    Open page

    Transparency

    Open page

    Version history

    Open page

    More WStaking documentation

    How It WorksRewardsSecurityFAQReferralRisksDocs hub