Executive Overview
WStaking is a multi-chain staking platform that combines on-chain contract accounting with off-chain operational execution.
Users create staking positions through supported WStaking smart contracts. Depending on the deployed contract version, these contracts record staking positions, applicable terms, rewards, claims, additional deposits, renewals, partial unstaking, and full unstaking.
After a staking transaction is confirmed, assets move through WStaking’s operational liquidity infrastructure according to the applicable operational flow. This includes designated hot wallets, strategy accounts, exchange sub-accounts, and other operational accounts used to support trading activity, liquidity management, exchange-fee rebate programs, and reward distribution.
Core Operating Model
Operating principle
WStaking does not rely on token inflation as the sole source of staking rewards. Reward availability depends on the applicable staking terms, platform operations, liquidity conditions, and the contract version used by each staking position.
Architectural Model
WStaking operates through two connected layers.
On-Chain Contract Layer
On-Chain Contract Layer: The on-chain layer manages the user-facing staking relationship with the supported blockchain network. Depending on the deployed contract generation, contract functions may include stake creation, position accounting, reward accounting, reward claims, additional deposits, position renewal, partial unstaking, full unstaking, token configuration, administrative controls, upgrade-related functions, and emergency or maintenance functions.
Off-Chain Operational Layer
Off-Chain Operational Layer: The operational layer supports functions that are not fully represented inside the staking contracts. These may include operational hot-wallet liquidity, strategy allocation, exchange master accounts, strategy or proxy sub-accounts, trading execution, exchange partnership and fee-rebate programs, liquidity preparation for claims and unstaking, administrative processing, monitoring, and reconciliation.
Current Production Contract Generations
| Network | Production generation |
|---|---|
| X Layer | V5 |
| BNB Smart Chain | V5 |
| Base | V3 |
Current production deployments use different contract generations: X Layer — V5; BNB Smart Chain — V5; Base — V3. The core staking model is shared across these deployments, while individual functions may differ according to contract generation and deployment configuration.
Because these operations occur outside the staking contract, not every operational activity can be reconstructed from blockchain records alone.
Revenue Generation Model
WStaking's operating model uses multiple sources of operational revenue rather than relying solely on token issuance or user inflows.
A portion of the operating model involves exchange-related activity conducted through designated strategy and exchange accounts.
Operating Revenue Sources
Public Verifiability
WStaking maintains exchange relationships, including participation in exchange partnership and rebate programs. Trading activity and exchange-account operations occur outside the staking contracts. Blockchain explorers therefore do not provide a complete view of strategy execution, exchange balances, fee rebates, or account-level operating performance.
Reward Relationship
Staking rewards should be understood as part of WStaking's broader operating model and not as a guaranteed return generated by any single revenue source.
Smart Contract Evolution & Security
Contract Evolution
WStaking's smart contract system has evolved through multiple contract generations as the product has added staking functions, accounting improvements, and operational safeguards.
Current generations
V3 and V5
Partial unstaking
Introduced from V3 onward
Functions Introduced or Improved
Audit Timeline
March 10, 2026
Audit begins
March 19, 2026
Audit window completed
March 20, 2026
CredShields retest
Later
Remediated implementation deployed to supported production networks
Audit Scope
CredShields conducted a smart contract audit on the WStaking contract implementation using BNB Smart Chain Testnet from March 10 to March 19, 2026, followed by a retest on March 20, 2026. WStaking subsequently deployed the remediated contract implementation to supported production networks. The current contract registry and deployment history should be reviewed together with the CredShields report because production deployments may use different contract generations and network-specific configurations.
Important limitation
The audit should not be interpreted as a guarantee that smart contracts, frontend systems, backend infrastructure, operational systems, wallets, networks, or future contract versions are free from risk.
Staking Mechanics
Introduction
Users create staking positions by selecting an available asset, network, duration, and staking option in the WStaking application and approving the required wallet transaction.
Available staking options may vary according to network, asset, contract generation, and current product configuration. Users should review the values shown in the application before confirming a stake.
Current Staking Plan Structure
| Duration | APR Range | Minimum Stake |
|---|---|---|
| 1 Month | 10% | 10 |
| 3 Months | 12% – 15% | 10 |
| 6 Months | 15% – 24% | 10 |
| 12 Months | 24% – 36% | 10 |
Reward Claims
Claim minimum
No separate minimum reward amount
Earliest claim availability
After at least one minute where applicable
Current production scope
V3 and V5
Reward Claims: There is no separate minimum reward amount required for a claim. Subject to the applicable contract and staking state, accrued rewards may become claimable after at least one minute of staking. The one-minute claim rule applies to the current V3 and V5 production contract generations. Claim execution may still depend on applicable contract rules, wallet approval, available payout liquidity, network execution, and blockchain confirmation. Claiming rewards and unstaking are separate actions.
Additional Deposits
Additional Deposits: Users may add funds to an existing supported staking position. Where supported, the additional amount becomes part of the existing position and the position timing restarts from the confirmed additional-deposit transaction. The applicable duration and APR remain subject to the rules of the active position and contract generation.
Renewal
Renewal: Eligible positions may be renewed according to the rules available for the applicable contract version. Renewal creates a new staking period according to the applicable product configuration and wallet-confirmed transaction.
Partial Unstaking
Partial Unstaking: Partial unstaking is supported for applicable positions created under V3 and later contract generations. A partial unstake removes only the selected supported amount while leaving the remaining position active according to the applicable contract rules.
Full Unstaking
Full Unstaking: A full unstake exits the applicable staking position. Under normal conditions, unstaking proceeds through the contract and wallet transaction flow. If sufficient payout liquidity is not immediately available, the position may enter the unlock-request process described in Section 06.
Early Unstake
| Plan | Penalty Rule |
|---|---|
| 1 Month | 10% |
| 3 Months | 15% reducing toward 10% over time |
| 6 Months | 24% reducing toward 10% over time |
| 12 Months | 36% reducing toward 10% over time |
The exact result of an early unstake depends on the applicable staking position, elapsed duration, contract generation, and current product rules. Users should review the displayed unstake terms before confirming an early unstake.
Fund Flow Architecture
WStaking Operational Fund-Flow Model
Operational Fund-Flow Model
User Wallet
WStaking Smart Contract
Operational Hot Wallet
Fund Allocation
Exchange Master Accounts
Strategy / Proxy Sub-Accounts
Strategy Execution
Exchange Fee Rebates
Operating Revenue Aggregation
Liquidity Management
Reward Accounting
Claim / Unstake Liquidity
User Wallet Settlement
User Wallet
WStaking Smart Contract
Operational Hot Wallet
Fund Allocation
Exchange Master Accounts
Strategy / Proxy Sub-Accounts
Strategy Execution
Exchange Fee Rebates
Operating Revenue Aggregation
Liquidity Management
Reward Accounting
Claim / Unstake Liquidity
User Wallet Settlement
WStaking operational fund-flow model
This model describes the operating architecture at a system level. Individual transaction paths, exchanges, accounts, strategy execution methods, liquidity sources, and processing steps may vary. Not every stage of this operational process is independently visible through public blockchain records.
How to Read This Model
User Wallet: The user initiates and approves the staking transaction from their own wallet.
WStaking Smart Contract: The staking contract records the position and executes the applicable on-chain staking functions.
Operational Hot Wallet: After staking, funds may move from the staking contract into designated operational liquidity infrastructure.
Fund Allocation: Operational funds may be allocated according to WStaking's internal liquidity and strategy requirements.
Exchange Master Accounts and Strategy / Proxy Sub-Accounts: Supported exchange accounts and separate strategy accounts may be used to segregate operational activities.
Strategy Execution and Exchange Fee Rebates: WStaking may conduct trading and volume-based strategies through supported exchange accounts. Exchange relationships may generate fee rebates, affiliate revenue, or other partner benefits according to each exchange's program terms.
Operating Revenue Aggregation and Liquidity Management: Rebates and other operating revenue may form part of the operating model, while operational liquidity is prepared to support eligible claims and unstaking activity.
Reward Accounting, Claim / Unstake Liquidity, and User Wallet Settlement: Rewards are calculated according to applicable terms and system rules. The user reviews and signs the wallet transaction required to complete a claim or unstake action.
Conditional Unlock Request
The seven-day process is conditional. It is not the standard withdrawal period.
Conditional Unlock Request: The seven-day unlock process is not the standard withdrawal period for every user. When sufficient payout liquidity is available, unstaking proceeds through the normal applicable contract flow. If operational liquidity is temporarily insufficient, an unlock request may be created. The request may remain in processing for up to seven days, may be released earlier when liquidity becomes available, and still requires a wallet-signed unstake transaction and blockchain confirmation. Submitting an unlock request does not itself complete the unstake.
Risk Disclosure
Participation in WStaking involves risk. APR figures, reward rates, and staking terms do not guarantee future profit or a fixed financial outcome.
Risk Matrix
| Risk area | Examples | Relevant dependency |
|---|---|---|
| Smart Contract & Technical | Defects, version differences, network, RPC, wallet, transaction, frontend, and backend failures | Contract generation, network, wallet, and application systems |
| Operational | Backend, wallets, administration, exchanges, strategies, liquidity systems, and third parties | Off-chain operations and service availability |
| Counterparty & Custody | Centralized exchanges, wallet infrastructure, providers, and operational accounts | Counterparty access, custody, and withdrawal conditions |
| Liquidity | Reward claims, unstaking, and temporary shortages | Available operational payout liquidity |
| Market | Volatility, liquidity, exchange, execution, and asset-specific conditions | Strategy and market conditions |
| Stablecoin | Issuer, reserve, market, liquidity, smart contract, and de-pegging risk | Supported asset and issuer conditions |
| Regulatory | Blockchain, staking, digital-asset, exchange, tax, and financial regulations | Jurisdiction and regulatory change |
Smart Contract & Technical Risk: Users may be exposed to smart contract defects, contract-version differences, network failures, RPC interruptions, wallet errors, transaction failures, and frontend or backend failures. An audit reduces some technical uncertainty but does not eliminate smart contract or platform risk.
Operational Risk: WStaking uses systems outside the staking contracts, including backend infrastructure, operational wallets, administrative processing, exchange accounts, strategy accounts, liquidity-management systems, and third-party services. Failures or delays may affect certain operations.
Counterparty & Custody Risk: Operational activity may involve centralized exchanges, wallet infrastructure, third-party providers, and operational accounts. Users may therefore be exposed to counterparty, custody, withdrawal, exchange, or operational-access risk.
Liquidity Risk: Reward claims and unstaking may depend on available operational liquidity. Temporary shortages may trigger the conditional unlock-request process.
Market Risk: Strategy performance can be affected by market volatility, liquidity conditions, exchange conditions, execution conditions, and asset-specific risks.
Stablecoin Risk: Supported stablecoins may be affected by issuer, reserve, market, liquidity, smart contract, or de-pegging risk.
Regulatory Risk: Blockchain, staking, digital-asset, exchange, tax, and financial regulations may change and may differ by jurisdiction. Users are responsible for determining whether they may lawfully use WStaking in their jurisdiction.
Governance & Controls
WStaking contracts include administrative functionality according to the deployed contract generation and network configuration. Administrative functions may include contract administration, token configuration, reward-setting configuration, maintenance functions, contract upgrades, implementation changes, and operational pause or emergency functions where supported.
Administrative Functions
| Administrative function | Possible scope | Verification |
|---|---|---|
| Contract administration | Contract-level administration | Verified source and explorer records |
| Token configuration | Supported-token configuration | Contract source and deployment state |
| Reward settings | Reward-setting configuration | Current contract terms |
| Maintenance | Maintenance functions | Explorer transactions |
| Contract upgrades | Implementation or proxy changes | Proxy, implementation, and upgrade history |
| Pause / emergency | Where supported by the deployment | Deployment-specific permissions |
Contract upgrades and implementation changes require the relevant blockchain transactions associated with the applicable deployment authority. Not every deployment necessarily exposes identical administrative functions.
How to Verify
Users and reviewers should verify deployment-specific permissions through verified contract source code, blockchain explorer records, contract ownership records, proxy and implementation information, upgrade transaction history, and WStaking's published controls documentation.
Legal Positioning
WStaking is a hybrid staking infrastructure platform involving blockchain contracts and operational systems.
Participation is voluntary and involves exposure to blockchain, smart contract, market, liquidity, counterparty, operational, and exchange-related risks.
Nothing in this whitepaper constitutes investment, legal, tax, or financial advice.
Users are responsible for reviewing applicable staking terms, risk disclosures, wallet transactions, and legal requirements relevant to their jurisdiction before participating.
The information in this whitepaper describes WStaking's current operating model and may be updated as the platform, contracts, integrations, or product configuration change.
Referral System & Payout Controls
WStaking operates a referral program that attributes qualifying staking activity to the referral code associated with a user's wallet.
Referral Binding
Referral Binding: When a user validly binds a referral code, the wallet becomes associated with that referrer according to the applicable referral rules. The binding applies to qualifying current and future staking activity associated with that wallet. Self-referral is not permitted.
Referral Reward Cycle
Referral Reward Cycle: The production referral reward cycle is based on 30-day periods. Referral rewards are calculated on qualifying staking activity according to the applicable referral rules. The currently published referral reward rate may be up to 0.5% per month on qualifying active stake.
Reward cycle
30 days
Reward rate
Up to 0.5% per month on qualifying active stake
Attribution
Qualifying current and future stakes associated with the bound wallet
Referral Claim Processing
Referral Claim Processing: Referral claim requests are reviewed before payout execution. An approved referral claim does not necessarily mean that the payout has already been completed. Where a payout is completed, transaction evidence may be recorded for the applicable payment.
Referral users should distinguish between accrued or estimated referral earnings, claimable earnings, approved claims, and confirmed payouts. Referral terms and eligibility may be updated as the referral program evolves.
Disclaimer
This whitepaper is provided for informational purposes and describes the WStaking platform and its operating model as of August 10, 2026. Participation in staking involves risk, including possible loss of principal. APR, reward, rebate, strategy, liquidity, or referral information should not be interpreted as a guarantee of future earnings. Users should review current product terms, contract information, risk disclosures, and wallet transaction details before participating.