WStaking platform and contract information

Current contract deployments

The listed addresses are the current mainnet references for X Layer (Chain ID 196), BNB Smart Chain (Chain ID 56), and Base (Chain ID 8453). The shared registry does not establish a current implementation address, contract version, or proxy status for each deployment; review the relevant explorer, version history, and controls page before interacting. Treat each listed deployment as Active only for the network and address shown here.

Operational dependencies and asset movement

Blockchain explorers can show transactions, token transfers, contract events, balances, source-code verification status, and upgrade activity associated with the listed addresses. Depending on the contract version, users may also inspect position creation, deposits, claims, additions, renewals, partial unstaking, full unstaking, and related events.

The available information does not establish a complete source of independently verifiable data for post-stake asset custody and operational fund movement. The contract interfaces and application flow indicate dependencies on payout liquidity, operational processing, and, where enabled, a seven-day unlock-request period before a later wallet-signed unstake transaction.

Backend availability, payout checks, administrative processing, and operational liquidity can affect when an action completes. These dependencies create risks that cannot be evaluated solely from the initial staking transaction or contract address.

On-chain records do not necessarily show backend calculations, administrative review, off-chain signatures, internal operational decisions, external account activity, custody arrangements outside the listed contract, or future liquidity availability. No private wallet, exchange account, trading position, treasury credential, or unpublished operational detail is disclosed here.

Controls, audit limits, and information sources

The current contract admin address is 0x18e0F8ababC84cDeFB562240a8b4713d6F928d83 for contract-level administration where supported. The controls page does not establish a multisig or timelock for the listed mainnet deployments. Where a deployment is upgradeable, an authorized administrative control may change implementation logic; review the current explorer data and upgrade history.

• Transparency DashboardWSTAKING
• Contract ReferencesWSTAKING
• Administrative ControlsWSTAKING
• Verification GuideWSTAKING
• Rewards DocumentationWSTAKING
• Risk DocumentationWSTAKING
• Security PageWSTAKING
• Risk DisclosureWSTAKING
• WhitepaperWSTAKING
• DocumentationWSTAKING
• FAQWSTAKING
• Version HistoryWSTAKING
• DefiLlamaEXTERNAL
• CredShields Audit ReportAUDITOR
• CredShields X AnnouncementAUDITOR
• CredShields LinkedIn AnnouncementAUDITOR
• WStaking Trust RepositoryWSTAKING
• WStaking Product RepositoryWSTAKING
• Official XWSTAKING
• Official TelegramWSTAKING
• Official InstagramWSTAKING
• Support EmailWSTAKING

The audit report covers the stated smart-contract scope and does not automatically cover later implementations, frontend code, backend services, administrative procedures, custody, or external integrations. Mainnet upgrade transactions document implementation changes but do not by themselves prove that deployed bytecode is identical to the audited source. Review the audit PDF, certificate, current implementation information, contract registry, version history, and explorer records separately.