Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Smart Contract Risk

Smart Contract Risk

WANNA and G-Series Stablecoin 2.0 are implemented as smart contracts deployed on EVM-compatible blockchains. Smart contracts execute automatically according to code and are typically difficult or impossible to reverse once executed.

This architecture enables transparency and permissionless access, but also introduces specific risks that users should carefully understand.

1. Code Bugs and Vulnerabilities

Even with careful design and review, smart contracts may contain:

  • Logic errors or design flaws

  • Security vulnerabilities

  • Unhandled edge cases

These weaknesses may be exploited by attackers to:

  • steal or freeze collateral assets

  • cause unintended minting or burning of stablecoins

  • manipulate internal accounting or risk parameters

  • create losses for specific users, pools, or the protocol as a whole

Mitigation efforts (such as internal review, external audits, formal verification, and bug bounties) can reduce but never eliminate this risk. No audit can guarantee that the contracts are free of bugs or immune to future attack vectors.

2. Upgrade and Governance Risk

Some components of the Protocol may be implemented as upgradeable contracts (e.g., using proxy patterns) or be controlled by governance.

This means that, over time, the following may change:

  • fee and reward structures

  • collateral parameters (CR, LCR, haircuts, exposure caps)

  • oracle configurations and price feed logic

  • pause / emergency mechanisms

  • integration with external protocols

Risks include:

  • Unintended consequences of upgrades (new bugs, broken integrations)

  • Governance attacks (e.g., vote capture, malicious proposals)

  • Conflicts of interest between different stakeholder groups

Even if changes are technically valid on-chain, they may produce outcomes that are unfavorable or unexpected from a user’s perspective.

3. External Dependency Risk (Oracles, Bridges, and Integrations)

The Protocol relies on multiple external systems, including:

  • Oracles – for FX rates, crypto prices, and other market data

  • Bridges – for cross-chain transfers and liquidity

  • External DeFi protocols – for yield, RWA access, or lending

If these external systems experience:

  • incorrect or manipulated oracle data

  • bridge exploits, censorship, or downtime

  • smart contract failures, hacks, or insolvency in integrated protocols

then the Protocol can be negatively impacted in a cascading way. Examples include:

  • incorrect FX rates affecting G-Series mint/burn calculations

  • loss of collateral locked in external protocols or bridges

  • inability to withdraw or rebalance reserves in a timely manner

Because G-Series Stablecoin 2.0 relies on a multi-layer pegging model and accurate price feeds, the reliability and integrity of oracles and external integrations are critical risk factors.

4. Operational & Implementation Risk

Beyond pure code security, smart contract systems can also be affected by:

  • Deployment errors (wrong parameters, misconfigured addresses)

  • Key management failures (compromised admin/multisig keys, lost keys)

  • Incorrect integration by third parties (wallets, exchanges, dApps)

These issues may result in:

  • funds getting stuck in contracts

  • certain functions being unusable or restricted

  • unexpected pauses or restrictions on minting, burning, or transfers

While the Protocol aims to minimize such risks through internal processes and best practices, they cannot be completely ruled out.

5. User Responsibility

Using smart contract–based systems requires users to:

  • manage their own wallets and private keys securely

  • verify that they are interacting with official contract addresses

  • exercise caution when:

    • approving token allowances

    • signing transactions

    • connecting wallets to third-party interfaces

The Protocol cannot:

  • recover assets sent to the wrong address or wrong network

  • reverse malicious transactions signed by the user

  • fully protect users from phishing, wallet compromise, or UI-level attacks

6. Summary

Smart contracts enable transparency and automation, but they also introduce:

  • bugs and exploit risks

  • upgrade and governance risks

  • oracle, bridge, and integration risks

  • operational and key management risks

Users should:

  • only interact with the Protocol if they understand these risks at a basic level

  • only commit funds they can afford to lose

  • stay informed about contract addresses, audits, and official security updates

For additional risk categories, please refer to:

  • Regulatory and Policy Risk

  • Collateral Asset Risk

PreviousOverviewNextRegulatory and Policy Risk

Last updated