Gains Network

Gains Network is a decentralized leveraged / perpetuals trading protocol (gTrade) using a synthetic architecture to offer high-leverage trading on crypto, FX, indices, commodities and stocks. Identification

• Name: Gains Network / gTrade
• Website: gains.trade (app and governance hub)
• Docs: docs.gains.trade and associated technical reference (GitBook) for smart contracts.
• Category: DeFi derivatives / decentralized perpetuals exchange using synthetic leverage.
• Launch dates (per chain):
• Polygon: initial launch of gTrade around December 2021.
• Arbitrum: expansion in January 2023.
• Base, MegaETH: later multi‑chain deployments; by 2026 gTrade operates on Arbitrum (primary), Polygon, Base, MegaETH, ApeChain; Solana trading via a separate front-end.
• Chains (per question): Arbitrum, Base, MegaETH, Polygon confirmed in FAQ and third‑party analyses.
• Native token: GNS – ERC‑20 utility/governance token for the ecosystem; example address on Arbitrum: 0x18c11FD286C5EC11c3b683Caa813B77f5163A122. Main contract addresses & verification (non‑on‑chain)
• The official docs list chain‑specific contract pages for Arbitrum, Base, MegaETH, Polygon (including trading core, NFTs, etc.), with direct links to the respective explorers where contracts are marked as verified.
• Historical GitHub repos (gTrade v5, v6.1) include Polygon mainnet addresses for Trading, Storage/Vault/Pool, again matching explorer records, providing a second independent source.
• Precise up‑to‑date on‑chain balances and verification status via Dune or direct explorer queries are Not verifiable as of 2026‑08‑29 within this environment. Fork lineage / origin
• Public documentation and third‑party analyses describe gTrade as a bespoke synthetic‑perps design, not as a fork of a specific upstream protocol (e.g., GMX, Perpetual Protocol); its architecture centers on synthetic exposures backed by collateral pools and GNS‑linked mechanisms.
• GitHub repos show multiple major versions (v5, v6.1, v8 diamond refactor) with their own codebases rather than a light fork of an existing project. Changes, audits, and fork‑risk
• gTrade v8 introduced a diamond proxy refactor and extensive NatSpec documentation for smart contracts, suggesting structured engineering and audit‑readiness.
• Independent security write‑ups classify Gains Network as a multi‑chain synthetic perps platform, noting open‑source code and recent audit activity (April 2026), but detailed audit reports and their scope are Not verifiable as of 2026‑08‑29.
• No credible records of malicious modifications in forks of Gains Network were identified; however, coverage of third‑party forks is incomplete, so broader fork exploit history is Not verifiable as of 2026‑08‑29. TVL / chain split (aggregator only, not on‑chain)
• Aggregators report most TVL on Arbitrum, with smaller amounts on Base, Polygon, MegaETH, ApeChain; for example, one analysis shows ~73% on Arbitrum with the remainder split across other chains.
• All such figures are analytics‑platform interpretations, not raw on‑chain; definitive TVL per chain is Not verifiable as of 2026‑08‑29.

Gains Network appears to be a real, mature product portal rather than a pure landing page: the main site points to live trading, staking, vault, OTC, referrals, and bridge applications, and the docs index explicitly covers trading, liquidity, protocol mechanics, and developer integrations. The documentation also exposes public backend API surfaces with no auth required for read endpoints, including chain-specific services for Arbitrum, Base, and Polygon, which is a strong sign of operational product depth. The documented frontend applications are chain-aware, and the API reference explicitly supports chain IDs for Arbitrum, Base, and Polygon.

CertiK’s public Skynet page lists 8 audits for Gains Network, with the latest audit delivered on Jun 24, 2022. The page shows 7 findings total: 0 critical, 1 major, 1 medium, 4 minor, and 1 informational. The major issue is listed as a centralization/privilege finding and is marked acknowledged; the page also indicates some findings were resolved/partially resolved, but it does not provide a full per-finding fix matrix in the snippet available.

Pashov Audit Group published a time-boxed security review of the GainsNetwork-org/gTrade-contracts repository. The visible report excerpt states the review focused on smart-contract security, lists the reviewed and fixed commit hashes, and includes at least one high-severity finding: H-01 storage slot collision, described as a potential collision between PriceAggregatorStorage and OtcStorage. The snippet does not show a complete critical/high/medium inventory or a definitive final fix-status table for all findings.

Gains Network has an active bug bounty program on Immunefi. The program started on 10 March 2022 and was still listed as live as of 29 January 2026. Parameters: Immunefi lists a maximum bounty of $200,000 and requires a proof of concept (PoC) for submissions. An earlier Gains Network announcement from March 2022 says payouts are based on Immunefi’s severity classification system, with rewards for smart-contract issues up to $100,000 for critical and $50,000 for high; for websites/apps, up to $50,000 for critical and $25,000 for high. Results: The publicly available sources here do not provide a complete, verifiable tally of total submissions or total paid out. A third-party security note claims “total paid to date: $364,280” and that the maximum bounty was reduced from $400,000 to $200,000 in January 2026, but this is not independently confirmed by Immunefi in the provided sources. Therefore, the total results are Not verifiable as of 2026-08-29.

Gains Network (gTrade) is a perps & synthetic trading protocol with material dependencies on price oracles, liquidity counterparties, stablecoins/LSTs and infra across Arbitrum, Base, MegaETH and Polygon. On‑chain verification: Not verifiable as of 2026‑08‑29. ### 1. Oracle & Price Manipulation Risk

• Chainlink oracles are the primary price source; gTrade historically uses Chainlink price feeds plus internal mechanisms (off‑chain order execution, synthetic liquidity model). This creates dependence on: (i) Chainlink outages or bad feeds, (ii) short‑term oracle deviations, and (iii) concentration on a single oracle vendor.
• Synthetic perps with high leverage are sensitive to short‑window price spikes; thin liquidity on underlying spot markets or on CEXes can be exploited to move oracle prices and trigger liquidations. ### 2. Liquidity, Counterparty & Stablecoin Exposure
• gTrade uses a GLP‑style or vault/liquidity pool model where LPs act as the counterparty to traders; LP insolvency or severe drawdowns (e.g., extreme trader PnL) can impair protocol solvency.
• On Polygon/Arbitrum/Base, trading collateral and vault assets are usually stablecoins (USDC/USDT/DAI) and volatile tokens. If a major stablecoin (e.g., USDC) or RWA‑backed asset depegs or faces issuer insolvency, LPs and traders see direct losses and potential protocol halt. Not verifiable as of 2026‑08‑29 for exact asset mix. ### 3. Bridges & Cross‑Chain Architecture
• Gains Network deploys separate instances per chain (Polygon, Arbitrum, Base; MegaETH is experimental). Cross‑chain liquidity or treasury movements rely on third‑party bridges (e.g., official chain bridges or popular L2 bridges). Bridge exploits or censorship can strand funds or desync capital between deployments, though each chain’s trading engine is logically siloed. ### 4. CEX / Market‑Maker & Off‑Chain Exposure
• Underlying asset prices for Chainlink feeds are heavily driven by CEX markets; exchange outages, manipulation or delistings can propagate via the oracle to gTrade.
• Any off‑chain execution layer (matching engine, keeper network) introduces operational and latency risk; if centralized or run by the team, this is a form of custodian / operational counterparty risk. Specific infra topology: Not verifiable as of 2026‑08‑29. ### 5. Governance, Admin Keys & Protocol Dependencies
• Smart contract upgradeability, emergency controls, and fee routing depend on multisig / team‑controlled keys; compromise, collusion, or regulator action against key‑holders could freeze or drain funds. Governance details (multisig composition, timelocks) are Not verifiable as of 2026‑08‑29. ### 6. LST / Restaking & RWA
• No evidence of direct restaking or LST‑based risk or specific RWA issuer/SPV exposure; if vaults hold LSTs (e.g., stETH) or RWA‑backed stablecoins, depeg/issuer default would transmit to LP solvency. Asset composition per chain: Not verifiable as of 2026‑08‑29.

Gains Network is non-custodial for traders: the docs state that users keep custody of their funds and there is no deposit/sign-up model for trading. For gTrade, users connect a wallet and trade synthetic positions directly from their own wallets; the protocol does not take possession of the trader’s underlying crypto. For liquidity providers, custody is organized through gToken vaults (for example, gDAI), which are ERC-4626-style vaults where deposited assets are pooled and represented by vault shares; those vaults act as the counterparty to trades and manage collateral, withdrawals, fees, and profit/loss distribution. In practice, this means trader funds stay under user control, while LP funds are temporarily custodied in protocol vault contracts rather than by the team. For the selected chains, the custody model is the same in principle across Arbitrum and Polygon based on the available sources, but the exact deployment and chain-by-chain exposure on Base and MegaETH are not verifiable as of 2026-08-29 from the provided results.

Bug bounty: a GitHub security note states the maximum payout was reduced to $200,000 from $400,000 as of 2026-01-29, but this is not independently verified from a bounty platform in the provided sources.

For Gains Network, key management is not verifiable as of 2026-08-29 from the provided results. The only directly relevant source is a secondary wiki describing NFT “master keys,” reward pools, and vault mechanics, but it does not explain operational key custody, signer roles, multisig setup, hardware wallets, or chain-specific admin controls for Arbitrum, Base, MegaETH, or Polygon. The other search results are generic pages about cryptographic or physical key management and are not about this protocol.

Gains Network (gTrade) uses a multi‑contract, upgradeable architecture across several chains, with significant but partially mitigated admin risk. On‑chain verification via Dune is Not verifiable as of 2026‑08‑29. ### 1. Core contracts & verification

• Public docs identify gDAI vault, trading engine, and perps DEX contracts on Polygon, Arbitrum, Base, plus newer deployments like MegaETH, but addresses are scattered across docs, GitHub, and explorers, not a single canonical registry.
• Key contracts on Polygon/Arbitrum are verified on Etherscan‑style explorers, allowing source inspection and confirming use of proxy patterns in some deployments. ### 2. Upgradeability & admin architecture
• Earlier deployments used proxy contracts (e.g., TransparentUpgradeableProxy / custom proxy) with a separate proxy admin/owner that can upgrade logic and change critical parameters.
• Protocol governance has shifted over time from more centralized multisig control toward a DAO‑controlled multisig/timelock for major upgrades and parameter changes, but exact timelock duration per chain is Not verifiable as of 2026‑08‑29.
• Some contracts (e.g., older vaults) have non‑renounced ownership, preserving the ability to upgrade, pause, or change fees. ### 3. Admin roles & emergency powers Typical privileged capabilities (vary slightly by chain/version):
• Pause / emergency stop: admin or guardian can halt new trades, sometimes withdrawals or funding mechanisms, to contain oracle/logic failures.
• Withdrawal control: vaults usually allow user withdrawals of collateral even when trading is paused, but this is contract‑specific; full cross‑chain confirmation is Not verifiable as of 2026‑08‑29.
• Fee & parameter changes: admin can adjust trading fees, max leverage, open interest caps, referral parameters, and risk limits.
• Oracle & strategy management: admin can switch price feeds or risk modules; oracle mis‑configuration is a material risk. ### 4. User exit & worst‑case scenarios
• Design intent is that users can always withdraw their collateral from the vault, but if an owner/guardian can both pause and gate withdrawals, user exit may depend on admin behavior in some contracts; this is Not verifiable as of 2026‑08‑29 across all chains.
• If admin keys or multisig are compromised:
• Attacker could upgrade logic to a malicious implementation, drain vaults, manipulate balances, or freeze withdrawals.
• They could change oracle sources and parameters to liquidate users unfairly.
• Rug/freeze risk is therefore non‑negligible, especially on newer chains (Base, MegaETH) where the governance setup is less documented independently. ### 5. Architecture snapshot (conceptual)
• Frontend → Router/Exchange contract → Perps engine → gDAI vault & collateral token contracts → Oracles.
• Control plane: DAO/multisig + (optional) timelock → proxy admin/owner → upgradeable logic contracts. Due to missing on‑chain tooling here, detailed per‑contract role status (renounced vs active) and exact timelock delays remain Not verifiable as of 2026‑08‑29.

Gains Network is a decentralized leveraged trading protocol (gTrade) originally launched on Polygon and later expanded to Arbitrum, Base and other chains. Identity and organization around the founding team are partially public, partially pseudonymous, and key corporate facts are Not verifiable as of 2026-08-29. ### Founders & Core Team

• The protocol is commonly described as created by founder “Seb” / “Sebastien” (sometimes “Sebastien B.”) and a small early team, but most are pseudonymous. Direct, verifiable real‑world identity links (full legal name, company registry entries) are Not verifiable as of 2026-08-29.
• Public-facing contributors include developers and community managers active on Twitter/X, Discord, and GitHub, but these accounts generally do not disclose full legal identities or employment details, which limits institutional KYC/AML comfort. ### Prior Track Record & Incidents
• Gains Network began as a synthetic leveraged trading protocol on Polygon in late 2021; there is no widely reported prior DeFi protocol by the same team with a distinct brand.
• As of recent media and analytics coverage, no major protocol-level hack or exploit of gTrade has been reported (beyond normal trading liquidations and minor technical incidents). This is based on public news and analytics; full incident history via on-chain forensics is Not verifiable as of 2026-08-29. ### Public vs Anonymous, Corporate Reality
• The project operates as a largely pseudonymous DeFi team, with founders and core contributors known primarily by handles; this is standard for many DeFi derivatives protocols but materially raises key‑person, governance and enforcement risk.
• Existence of a registered operating entity (e.g., DAO LLC, foundation, or commercial company), its jurisdiction, and whether there is a physical office are Not verifiable as of 2026-08-29 from independent sources.
• There is no clear evidence in independent media or regulator databases of a formal onshore corporate structure backing the protocol; Gains Network appears to function as a web‑native, DAO‑style project with treasury/governance on-chain and operations coordinated online. ### Credibility & Reality Check (Institutional Lens)
• Positive factors: multi-year uptime, significant usage on Polygon/Arbitrum, repeated coverage by analytics platforms and DeFi media, and absence of known major exploits support technical credibility.
• Negative factors: pseudonymous founders, unclear incorporation status, and lack of audited on-chain verification here increase counterparty, regulatory and recourse risk for institutions. Overall, Gains Network should be treated as a pseudonymous, web-native DeFi protocol with no independently confirmed traditional corporate footprint as of this review date.

Gains Network currently has a generally positive security reputation, backed by multiple audits and an active bug bounty, with no public fraud/rug/insolvency allegations identified. However, team KYC is limited, and some contract-privilege concerns have been noted, so institutional risk remains non‑zero. ### Security audits and bug bounty

• CertiK lists 8 audits for Gains Network, with a security score of 92/100 and “Very High” audit impact, last major audit delivered June 24, 2022.
• An independent security review (GainsNetwork-security-review.pdf) is available via the pashov/audits GitHub, indicating at least one non‑CertiK review.
• Gains Network maintains a bug bounty on Immunefi with a maximum reward of $200,000, covering critical impacts such as direct theft of user funds, insolvency, and permanent freezing of funds.
• IQ.wiki notes partnerships with Immunefi and InsurAce, and that Gains Network “prioritizes security” and has its smart contracts audited by CertiK before updates; this is an unverified marketing claim until cross‑checked against primary audit records. ### Identified concerns and criticisms
• A 2026 security skill assessment summarizing Gains Network cites CertiK’s Skynet entry but flags the token contract as HIGH risk in GoPlus data: hidden owner, owner can change balances, and minting ability. These are centrally controlled privileges and represent governance/abuse risk rather than an exploit in itself.
• CertiK’s page states “Team Verification: Not Verified by CertiK; CertiK KYC: No; 3rd Party KYC: No”, meaning the team has not undergone formal KYC with this auditor, which may be a concern for institutional counterparties. ### Fraud, rug pull, insolvency, and sanctions
• No sources retrieved report rug pulls, exit scams, or insolvency events specifically tied to Gains Network on Arbitrum, Polygon, Base, or MegaETH as of the latest data.
• The California DFPI Crypto Scam Tracker and recent rug‑pull case reports do not list Gains Network among targets or defendants; therefore, no direct regulatory fraud action or sanctions involving Gains Network were found.
• Absence of evidence is not proof of safety; this is “no known allegations”, not an on‑chain verification. Not verifiable as of 2026‑08‑29. ### Overall sentiment and institutional takeaways
• Community and media references (IQ.wiki, Immunefi listing, CertiK page) portray Gains Network as a serious, security‑conscious derivatives protocol with structured audits and bounty coverage.
• For institutional use, key ongoing concerns are:
• Admin/owner powers on token/contract level and centralization risk.
• Non‑KYC team status at major auditor level.
• Lack of fully independent, chain‑by‑chain on‑chain verification of solvency and risk exposures. Not verifiable as of 2026‑08‑29.

Gains Network (gTrade) is a perps and leveraged trading DEX where users’ yield comes from acting as counterparty/liquidity providers to leveraged traders, not from lending or farming. 1. Strategy & assets in/out

• Core product: synthetic leveraged trading (crypto, FX, indices, commodities) on Polygon, Arbitrum, Base, MegaETH.
• Users deposit stablecoins (e.g., USDC/DAI-like on each chain) into the GLP-style pool ("gToken"/Dai vault equivalents) or stake GNS to earn protocol fees.
• Assets out: trading PnL, funding payments, and fee revenue distributions to LPs/stakers. 2. Yield source & economic exposure
• Primary yield = trading fees, borrow/funding fees, liquidations paid by leveraged traders.
• LPs are effectively the house: they earn when traders lose and lose when traders win; this is directional exposure to trader PnL, not pure market-neutral.
• A portion of fees goes to GNS stakers and protocol treasury, creating protocol revenue. 3. Organic vs subsidized
• Yield is mostly organic fee/PNL-based; historical liquidity incentives (GNS emissions, bonus multipliers) have existed but are not structurally required for core yield.
• Any incentives listed by Gains (trading rewards, referrals) are unverified marketing claims unless corroborated by third-party analytics. 4. Leverage, restaking, external risk
• Traders can use high leverage (up to 150x+ on some pairs), funded from the LP pool.
• No evidence of rehypothecating LP collateral into external DeFi (e.g., restaking, lending) – risk is mainly internal PnL variance and oracle risk.
• Protocol relies on Chainlink and custom oracles for pricing; oracle failure is a key systemic risk. 5. Lock-ups, withdrawals, mechanics
• LP deposits and withdrawals are generally non-custodial and on-demand, subject to:
• Cooldowns or caps in extreme conditions (e.g., when pool skew vs open interest is high).
• Possible slippage / discount when exiting under stress due to pool imbalances. 6. Fees, gates, limits
• Fee stack typically includes:
• Opening/closing trading fee (bps on notional).
• Borrow/funding fee over time.
• Liquidation fee, partly to liquidators/treasury.
• Position size, leverage, and open interest limits per pair are enforced to manage risk. 7. Protocol revenue & token
• Protocol revenue = share of trading-related fees; split between GNS stakers, LPs, and treasury, implementation varies by chain/product.
• GNS is a utility/governance token; buyback-and-burn or fee-sharing mechanisms have been used historically, but parameters can change via governance – treat as governance risk. 8. TVL & APY
• Total TVL, TVL by chain/product, and APY history Not verifiable as of 2026-08-29 due to lack of on-chain/Dune access in this run and inconsistent aggregator numbers.
• Published APYs on dashboards are highly volatile, driven by trader PnL and volume; sustainability depends on sustained trading activity and balanced win/loss distribution.

Gains Network’s public reserve/treasury picture is only partially verifiable from the provided web results. DefiLlama reports a treasury of $294,662 as an aggregator estimate, with composition broken out as majors $3,185, stablecoins $87,745, and own tokens $203,730; it also breaks TVL by chain as Arbitrum $11.17m, Base $2.54m, Polygon $808,449, and MegaETH $256,551. The protocol FAQ states the minimum reserve amounts are 1,500 DAI on Polygon and 7,500 DAI on Arbitrum, which indicates a reserve policy floor but does not provide a full treasury or custody map. The protocol homepage claims “No deposits, no black boxes” and that every order is transparent on-chain, but that is an unverified marketing claim unless matched to independently verified treasury addresses and balances. Not verifiable as of 2026-08-29: the actual treasury/control addresses, custody arrangement, reserve controller or multisig signers, on-chain balances by chain via Dune, and any independent attestation of reserves were not confirmed in the provided sources. The results also do not establish a complete cross-chain reserve composition for Arbitrum, Base, MegaETH, and Polygon, so any chain-by-chain reserve split beyond DefiLlama’s treasury estimate would be speculative.

Gains Network has a single native token GNS used across Polygon, Arbitrum and Base; MegaETH deployment is recent and token-related data there is Not verifiable as of 2026-08-30. ### Token basics

• Name / ticker: Gains Network (GNS).
• Key contracts (non-exhaustive):
• Polygon: GNS at 0xE5417Af564e4bFDAE... (standard reference across analytics).
• Arbitrum & Base: bridged GNS; detailed canonical contract mapping is Not verifiable as of 2026-08-30.
• Total vs circulating supply: Multiple sources report max supply ~100M GNS, current supply ~30–40M GNS due to past burns and buybacks. Exact live figures are Not verifiable as of 2026-08-30.
• Market cap / FDV: Aggregators show a mid-cap range (hundreds of millions USD) with FDV moderately above circulating market cap, consistent with reduced supply post-burns. Specific values are stale data if >7 days old; precise current figures are Not verifiable as of 2026-08-30. ### Utility, governance, and value accrual
• Utility: GNS is used for staking to earn a share of protocol fees, and as the core token in the ecosystem’s liquidity and reward design.
• Governance: GNS holders participate in protocol governance voting over risk parameters and upgrades; details mostly documented in protocol materials (unverified marketing claim).
• Revenue share / buybacks / burns: Fees from trading on Gains Network have historically funded buybacks and burns of GNS; several major burn events are documented in analytics and media. Exact amounts burned and buyback pace are Not verifiable as of 2026-08-30.
• Staking rewards: Stakers receive a portion of protocol fees (in stablecoins or native tokens) plus potential GNS incentives; specific APR/emission figures are unverified marketing claims. ### Emissions, unlocks, and allocations
• Emissions schedule & unlocks: Public tokenomics charts show allocations to team, investors, community incentives, and treasury with multi‑year vesting. Verification that each announced unlock occurred on-chain is Not verifiable as of 2026-08-30.
• Allocations: Rough split: significant share to community incentives and liquidity, with smaller but meaningful allocations to team and early investors. Exact percentages vary by source and are not on-chain verified.
• Top-holder concentration / insider wallets: Concentration data and identification of insider wallets (team, investors, treasury) are Not verifiable as of 2026-08-30. ### Contract powers and liquidity
• Admin / mint / blacklist / fee-switch: Whether GNS contracts retain minting, pausing, blacklist, or fee-switch functionality and who controls them is Not verifiable as of 2026-08-30.
• DEX liquidity & listings: GNS is listed on major DEXes on Polygon and Arbitrum (e.g., Quickswap, Uniswap forks) and several CEXs, with substantial but mid-tier liquidity depth according to aggregators. Exact pool sizes per chain are Not verifiable as of 2026-08-30. Contradiction box: Various analytics disagree on current circulating supply and burn totals for GNS. Without on-chain Dune access, these conflicts cannot be resolved and are Not verifiable as of 2026-08-30.

For a Gains Network stress scenario where Bitcoin falls below $10,000, the most relevant conclusion is that this is a high-severity, low-probability macro shock rather than a base case; the public market commentary in the provided results consistently frames sub-$10k BTC as requiring an extreme liquidity crisis, major deleveraging, or broader systemic stress. For a leveraged DeFi protocol like Gains Network, the main risk transmission would be rapid collateral impairment, forced liquidations, and possible oracle/market-dislocation stress if BTC gaps lower faster than positions can be rebalanced; however, protocol-specific exposure across Arbitrum, Base, MegaETH, and Polygon is Not verifiable as of 2026-08-29 because no on-chain data was available in this run. What can be said with confidence is that a BTC move below $10,000 would likely coincide with a broad risk-off event and liquidity contraction, which is the kind of environment that typically increases liquidation frequency and sharpens price gaps in leveraged markets. If Gains Network has BTC-denominated or BTC-referenced markets open across those chains, the stress would be most acute on the chain(s) with the largest open interest and weakest liquidity, but the chain-by-chain exposure split is Not verifiable as of 2026-08-29. Key monitoring points for this scenario:

• Open interest concentration in BTC and correlated crypto pairs.
• Collateral quality and whether users are posting volatile assets.
• Liquidation speed vs. oracle update frequency during fast markets.
• Cross-chain fragmentation, because exposures can differ materially between Arbitrum, Base, MegaETH, and Polygon.
• Protocol backstop capacity if liquidations outpace matching liquidity. If you want, I can turn this into a concise risk memo format with sections for *impact, likely failure modes, and monitoring thresholds*.

Gains Network uses separate vault risk by collateral, so a 20% depeg in the *largest collateral* would primarily stress that collateral’s own vault rather than all markets at once. The docs state that each collateral has its own gToken vault and that max open interest is calculated separately per vault, so the relevant loss is concentrated in the largest vault, not automatically spread across Arbitrum, Base, MegaETH, and Polygon. Under a 20% depeg, the immediate economic effect is that every unit of that collateral held in the vault would mark down by 20%, which reduces the vault’s collateral value and can push its collateralization ratio lower. If that reduction is large enough to move the vault below 130%, buyback-and-burn mechanics stop; if it moves below 100%, the protocol’s backstop logic can require minting and selling GNS to refill the vault, creating dilution pressure on GNS holders. What I can verify from the provided sources is the mechanism, not the size of the loss. The exact impact on GNS, trader withdrawals, or protocol solvency is Not verifiable as of 2026-08-29 because current chain balances, largest-collateral TVL by chain, and vault PnL data are not available in the supplied results. Practical interpretation:

• Largest direct loss: 20% of the largest collateral’s balance in its vault.
• Main secondary risk: a lower vault collateralization ratio, potentially triggering delayed withdrawals and, in the worst case, GNS mint-and-sell backstop pressure.
• Chain scope: risk is isolated per collateral/vault; no source here supports an all-chain aggregate estimate.

For Gains Network, the top-counterparty-insolvent stress path is: trader profits exceed the relevant vault’s capacity, so the gToken/gDAI vault is the first loss absorber; if the position is liquidated, the remaining collateral goes to the vault and if the trader closes in profit, the vault pays the profit.

• Arbitrum / Base / Polygon / MegaETH: the same economic path applies, but the documentation fetched here does not provide chain-specific contract flows or vault allocations for each chain, so chain-by-chain exposure is Not verifiable as of 2026-08-29.
• Expected loss path: unrealized PnL becomes realized when positions are closed or liquidated; liquidation transfers the collateral to the vault, while profitable closes debit the vault.
• Who absorbs it: initially the vault absorbs trader wins and keeps trader losses; the docs also state that when the vault is over-collateralized, excess value is used to buy back and burn GNS, indicating upside accrual to tokenholders only after the buffer is filled.
• Compensation: the platform’s compensation mechanism for LPs/stakers is fee yield from trading activity; the fetched materials also describe fee revenue flowing to GNS holders/stakers, but any exact loss-sharing or backstop mechanics beyond that are Not verifiable as of 2026-08-29.
• Impact path through smart contracts: position PnL is settled against the vault at close; if liquidation triggers, collateral is routed to the vault; the docs indicate liquidation logic and thresholds determine when this happens, but the exact per-chain contract addresses and fallback/deficit settlement code paths were not verifiable in the available sources. Contradiction callout: one independent explanation claims that if the vault goes negative, losses are distributed pro-rata across GNS stakers, but that specific backstop mechanism was not confirmed in the primary documentation fetched here, so it should be treated as unverified.

For Gains Network, a committed fraud by the DAO or owners is not verifiable from the available web sources. The strongest evidence found instead points to a different stress pattern: past vulnerability research showed that some Gains Network forks had bugs that could let traders extract outsized profits, but the reports say those issues were fixed in Gains Network or were present only in forks, not as confirmed owner/DAO fraud. What is verifiable is that Gains Network’s governance is described as Snapshot-based and advisory, with execution depending on the team rather than binding on-chain DAO control. That creates centralization and governance-risk exposure, but it is not evidence of fraud by the DAO or owners. No regulator, audit, or independent media source in the provided results alleges that Gains Network’s DAO or owners committed fraud. Therefore, the correct stress-scenario classification here is Not verifiable as of 2026-08-29 rather than confirmed fraud.

For Gains Network, a primary yield source negative 30d stress case is not verifiable as of 2026-08-29 from the available web results. The retrieved sources only describe macro stress-test frameworks and Gains Network’s trading interface; they do not provide chain-specific, protocol-level 30-day yield attribution for Arbitrum, Base, MegaETH, or Polygon. What can be stated is that the stress context you should apply is a severely adverse / risk-off regime with declining risky-asset prices and higher volatility, which is directionally consistent with a negative 30-day primary yield outcome for a leveraged trading protocol, but this is an inference rather than a verified protocol metric.

• Primary yield source: Not verifiable as of 2026-08-29.
• 30d direction: Negative is plausible under stress, but unverified.
• Chain split: Not verifiable as of 2026-08-29 for Arbitrum, Base, MegaETH, or Polygon. If you want, I can next produce a concise stress-analysis template for Gains Network that flags the likely yield drivers and the specific missing on-chain checks that would normally be used to verify the 30d figure.

Gains Network appears to be primarily team-operated, with off-chain community governance that is advisory rather than fully binding. The public forum states proposals go through community ideation, forum discussion, then a Snapshot vote, and the decision is delivered by the team & multisig group; it also says execution is after a timelock, but the forum does not establish a fully autonomous DAO that can directly execute changes. The forum specifically says eligible proposers are currently limited to team and community representatives, which supports a DAO-real-but-limited assessment rather than symbolic-only, but also not a mature on-chain DAO. Control of contracts/funds/frontend: the available evidence does not let me verify exact current signers, thresholds, or whether the frontend is independently controlled; those items are Not verifiable as of 2026-08-29. The same applies to any Dune-based voting concentration/top-holder analysis because on-chain checks are unavailable in this run: Not verifiable as of 2026-08-29. Gains Network’s documentation does confirm timelocked admin pathways for protocol components, including 3-day and 14-day timelocks for different roles, with the 14-day path reserved for changes that could affect user funds. Proposal process: forum ideation → forum discussion → Snapshot vote → execution by team/multisig after timelock. The forum also describes 10% of supply quorum and majority vote for Snapshot proposals. Company/legal entity / ToS: I could not verify a controlling legal entity, jurisdiction, registration number, directors, or a ToS that clearly defines company control. Not verifiable as of 2026-08-29. Bottom line: the strongest sourced conclusion is that Gains Network uses off-chain governance with a team/multisig execution layer, not a fully trustless DAO; exact signer/control details remain unverified in this run.

Not verifiable as of 2026-08-29. The search results do not identify the specific stablecoin used by Gains Network across Arbitrum, Base, MegaETH, and Polygon, nor do they provide a reliable event history for that protocol’s collateral/stablecoin. The results only show generic stablecoin depeg examples and unrelated price data for GNS or a “Gains Network USDC” coin listing, which is not sufficient to confirm whether the protocol’s stablecoin depegged, how many times, when the last event occurred, or the depeg percentage. If you want, I can next check the protocol’s docs/governance and independent market data for the exact stablecoin name, then assess its depeg history.

Top 5 risks for Gains Network are: 1) Oracle / price-feed dependence — the protocol’s synthetic trading model relies on external pricing, so feed errors or manipulation can directly affect PnL and vault outcomes. 2) Extreme leverage exposure — leverage up to 500x on crypto and 1000x on forex can magnify even tiny pricing or execution errors into outsized losses for the vault or traders. 3) Vault / counterparty concentration — traders are effectively facing the protocol’s liquidity vault, so losses are socialized into a shared pool rather than isolated to a matching counterparty. 4) Token dilution / backstop risk — independent risk analysis flags a mechanism where GNS minting can backstop vault shortfalls, creating dilution pressure if trader wins exceed fee revenue. 5) Smart-contract / implementation risk — reviews note that leveraged DeFi protocols remain susceptible to code flaws, and external analysis of Gains fork patterns highlights potential logic weaknesses around stop-loss/take-profit behavior.

Gains Network’s top five strengths are: broad market coverage, with crypto, forex, stocks, indices, and commodities available on gTrade; very high leverage, including up to 500x on crypto and 1000x on forex; capital efficiency, using synthetic leverage and shared gToken vault liquidity instead of pair-by-pair order books; self-custody and transparency, since users keep full custody and trades execute on-chain without deposits or signups; and competitive execution, with median spot pricing from multiple sources, low fixed spreads, and no size-based liquidity impact on BTC/ETH. The protocol also emphasizes a polished user experience refined over years of feedback.