Security

Security and audit overview

Review the CredShields smart-contract audit, finding status, contract references, deployment records, and security-reporting channels.

Open audit PDF CredShields report repository

Audit summary

Our CredShields smart contract audit was conducted on BNB Smart Chain Testnet between March 10, 2026 and March 19, 2026, with a retest performed on March 20, 2026. The report identified 16 findings during the audit window. The retest confirmed that the listed issues were either remediated or acknowledged as documented in the report.

Audit window

CredShields audited our smart contract scope on BNB Smart Chain Testnet from March 10, 2026 through March 19, 2026.

Retest confirmation

The follow-up retest was completed on March 20, 2026, confirming the reported fixes and acknowledgements documented in the final report.

Security contact

For security-related questions, responsible disclosure requests, or audit verification follow-up, contact us through our official support channel at service@wstaking.net.

We recommend using only the official links published on this page, our homepage, and our verified social channels when sharing security reports or contract references.

Open Verification Guide Responsible Disclosure

Severity summary

Critical
1 finding. The critical APR fallback issue identified in the audit was remediated and passed retest.
High
2 findings. One high-severity issue was remediated, and one business-logic item was acknowledged as documented in the report.
Medium
3 findings. Two medium findings were remediated, and one business-logic item was acknowledged as documented in the report.
Low / Info / Gas
All listed low, informational, and gas items were remediated. These improvements include pause control, ownership transfer hardening, hot-wallet rotation support, explicit revert behavior, receipt-hash integrity, and gas optimizations.

Audit certificate preview

We also publish the certificate image issued alongside our audit materials so reviewers can match the report and certificate set from the same public source.

Audit-to-Deployment Mapping

The CredShields audit and retest were completed before the listed mainnet upgrade transactions. The transactions document later implementation changes on X Layer, BNB Smart Chain, and Base. However, the exact audited-source-to-mainnet bytecode mapping is not currently established by the published materials. Users should review the audit report, current implementation information, contract registry, version history, and explorer records as separate sources.

Auditor

CredShields

Audit window

March 10-19, 2026

Retest date

March 20, 2026

Audit report / certificate

Available from the official WStaking link and CredShields audit-reports repository

CredShields report repository

Open report repository entry

Audited scope

Testnet contract 0xf7edfbf075b48daa47b3405c190b126fb6f02dcd; reviewed by CredShields before the later mainnet transactions

Retested scope

Testnet contract 0x6B6b5eca778BcFdbC9D8b2d718e01233A1C1d5eD; retested on March 20, 2026

Mainnet transaction note

The listed transactions record later implementation changes on X Layer, BNB Smart Chain, and Base; they do not by themselves establish an exact audited-source match.

Remediation summary

The report records the findings as fixed or acknowledged. Review those statuses in the audit report; the current mainnet implementation relationship remains a separate verification question.

Audited commit hash

Not identified in the published report

Traceability note

The audit report documents the reviewed findings and their recorded status. The listed mainnet upgrade transactions document later implementation changes, but the exact audited-source-to-mainnet bytecode mapping is not currently established by the published materials. Users should review the audit PDF, certificate, current implementation information, contract registry, version history, and explorer records as separate sources. This page is a reference summary, not a standalone security guarantee.