Risks and important considerations

APR is an annualized rate used to describe the reward terms of a staking option. It is not an immediate payment or a guaranteed return.

The reward shown for a position may depend on the deposited amount, elapsed staking time, contract version, reward rules, claims, additional deposits, renewals, unstaking activity, and operational data.

A displayed reward may still be subject to claim requirements, wallet approval, contract execution, operational processing, available liquidity, and blockchain confirmation. Terms recorded when an active position is created generally remain associated with that position; later settings normally apply to new positions.

A staking position may be subject to a lock period. During that period, full or partial withdrawal may be unavailable, delayed, or subject to penalties.

Claiming rewards, adding funds, renewing, partially unstaking, and fully unstaking are separate actions. Each can affect the position amount, start time, duration, rewards, lock period, and remaining balance differently.

In the current implementation, adding funds to a supported position restarts timing from the confirmed add-fund transaction while retaining the applicable duration and APR. Behavior can still differ by contract version and product configuration.

Where the unlock-request flow is enabled, submitting an unstaking request begins a seven-day processing period. The position becomes eligible for release after the required waiting period or an applicable early release, and the user must still return to sign the final unstake transaction.

A displayed reward does not necessarily mean that the amount can be claimed immediately. There is no universal one-minute claim guarantee stated here for every live contract version.

A claim may depend on the position state, contract rules, wallet approval, contract execution, operational checks, and blockchain confirmation. Claims can fail or be delayed because of network congestion, insufficient gas, contract state, or unavailable liquidity.

Some WStaking operations may depend on systems and asset-management processes outside the staking contract. This can create operational, liquidity, custody, and counterparty risk.

Withdrawal or reward payment may depend on assets being available when required. Delays, restrictions, account freezes, counterparty failure, or operational interruption could affect user outcomes. The published materials do not establish that every asset remains in the staking contract or that every withdrawal is independent of operational processing.

A stablecoin may lose its intended value, experience reduced liquidity, or become subject to issuer controls.

Token issuers may be able to freeze addresses, blacklist assets, pause transfers, or upgrade token contracts. These actions are outside WStaking's control.

Token behavior can differ across networks and contract versions. WStaking does not guarantee that a supported asset will maintain its price, liquidity, transferability, or regulatory status.

Smart contracts may contain defects, unexpected behavior, integration problems, or vulnerabilities that were not identified before deployment.

Where a deployment is upgradeable, an authorized owner or administrative control may be able to change implementation logic. Published upgrade transaction references do not by themselves prove that a deployment uses a multisig, timelock, or any particular governance structure.

A contract audit reduces some risk but does not guarantee that code is free from vulnerabilities. Audit coverage is limited to the scope, version, network, and source identified in the report.

Blockchain transactions may fail, remain pending, cost more than expected, or behave differently because of network congestion, RPC issues, gas-price changes, chain instability, or wallet-provider problems.

Confirmed transactions are generally irreversible. A transaction sent to the wrong network, contract, address, or token may not be recoverable.

Users are responsible for reviewing wallet prompts, contract addresses, token approvals, transaction amounts, and requested functions before signing. WStaking support should never request a seed phrase, recovery phrase, private key, or wallet password.

Some WStaking functions may depend on backend services, administrative signatures, RPC providers, wallet providers, token issuers, external APIs, or other third-party systems.

Service interruption, incorrect data, delayed processing, provider outages, compromised credentials, or external policy changes may affect access, reward display, claims, unstaking, or support.

Laws and regulatory treatment of staking, digital assets, stablecoins, rewards, and related services differ by jurisdiction and may change.

Local law, sanctions, asset controls, tax rules, licensing requirements, or regulator and service-provider actions may affect access to WStaking.

Users are responsible for determining whether their use of WStaking is permitted in their jurisdiction and for obtaining independent legal or tax advice where necessary.

An audit reviews defined source code, assumptions, and conditions during a specific period. It does not guarantee that the audited code has no vulnerabilities.

The published CredShields report identifies a defined smart-contract scope and does not automatically extend to later upgrades, other contract versions, different networks, frontend code, backend systems, operational processes, or third-party integrations.

Users should compare the audited contract, version, network, and source reference with the deployment currently used by the application. The published report does not establish exact audited-source-to-mainnet equivalence on its own.

Before creating a position, review the official domain, selected network and asset, complete contract address and version, amount, APR, duration, lock period, claim and unstaking conditions, applicable penalties, administrative or operational dependencies, audit scope, Terms, Privacy Policy, Risk Disclosure, and wallet transaction details.