Buy
Market
🔥
Prediction Market

Gate and GoPlus Publish Guide to Smart Contract Security Audits

The second edition of Gate Security Academy, created with GoPlus Security, explains the limits of smart contract audits and how users can better evaluate…

19/11/2026 14:4285 min read

The second issue of the Gate Security Academy, developed in partnership with GoPlus Security, has been released.

The publication looks into the boundaries of smart contract audits, covering what they can confirm and what lies outside their reach, along with ways users can evaluate a project's protections that go beyond the audit document. The series is designed to address various crypto security topics using real-world examples, blending the experience of the exchange and the security firm.

Security should be seen as a continuously evolving condition rather than a fixed achievement stamped on a report.

A number of the platforms that experienced security breaches in 2024 had previously passed security reviews. A few had been looked over by auditors on several occasions. That is not to imply that audits lack value. Rather, it indicates that the scope of what an audit can verify is much more limited than the public generally believes.

An audit report captures a specific snapshot: it reflects a given version of a protocol as assessed by a specific group of engineers at a single moment. Contracts can receive updates, administrative privileges can shift, and the external services a project uses—like oracles and bridges—are subject to change. On top of that, novel exploitation methods appear regularly.

The information in an audit report starts losing its pertinence as soon as it is handed over.

Older contracts that cleared their audits upon deployment years earlier are of particular concern. These are now being re-examined in bulk using modern tools, and underlying flaws in contracts active for years can occasionally be spotted in a little more than ten minutes.

For this edition, GoPlus Security and the Gate security department share their views on contract audits and vulnerability identification, offering insights from the angle of a security vendor and a trading venue.

The content explores questions such as why reviewed projects can still be compromised, the correct way to interpret an audit report, the screening procedures exchanges apply when listing a token, and the steps everyday users can take before confirming a transaction.

Guest Introductions

Adam, Partner at GoPlus: Adam holds a Partner position at GoPlus and leads its Security Research Institute.

GoPlus Security is developing what it describes as the first decentralized security infrastructure for Web3 and AI, merging blockchain with AI-driven tools to deliver intelligent and efficient security services.

Since 2022, the company has reached a volume of 30 million daily API requests and has supported users in avoiding around $100 billion in potential damage.

Gate Security Team: This team oversees the development and upkeep of Gate's security framework for accounts, transactions, and asset protection, and routinely processes user disputes regarding suspicious actions and investigation requests.

Gate began operations in 2013, became an early supporter of full proof-of-reserves, and now reports over 63 million users internationally. The platform considers security the bedrock of its activity. The Gate Security Academy series is intended to clarify the typical mechanisms behind the actual security threats that users face.

Q1. Why do numerous projects still suffer breaches or privilege exploitation despite passing security checks?

Adam, Partner at GoPlus:

A singular audit does not guarantee permanent safety. The conventional approach to smart contract auditing is currently constrained by four fundamental shortcomings.

Snapshot-based reviews. An audit functions as a partly manual check performed by security staff at a fixed moment. Its quality hinges on the tools used, the skill of the auditors, and workplace factors. Code can be updated, admin rights altered, and settings changed. A single audit report begins to degrade immediately upon delivery.

Inability to predict future threats. Fresh forms of vulnerabilities and attack methods constantly surface. Past audits are inherently blind to threats that have yet to develop.

Uncontrolled external dependencies. Many projects depend on oracles, bridges, and outside protocols. Shifts in the risk profile of these external elements typically escape the reach of standard audits.

Vulnerabilities emerging in older contracts. Smart contracts launched years earlier that satisfied audit requirements back then are now being re-evaluated in bulk. Automated scanning has exposed latent weaknesses, including deep-seated flaws in prominent DeFi protocols that stayed hidden long after their release.

Privilege misuse tends to emerge during a project's operational phase rather than from the code itself.

Frequent triggers include broad owner powers like unlimited token minting, address blacklisting, and trading halts; stolen admin keys; flawed multi-signature setups; harmful proposals; and governance strikes.

All these safety concerns can surface while a system is live.

Even when an audit flags permission-based dangers, the task of monitoring those permissions and assessing the safety of later choices remains unaddressed. Standard audits provide no answers on this front.

Deploying a contract following an audit marks the start of security efforts, not their conclusion.

Ongoing protection across the whole lifespan of a contract is what projects actually require, not just a single audit document.

Gate Security Team:

An audit reveals the code's potential actions, yet it cannot uncover the team's actual plans.

The team identifies this as a crucial insight gained from lengthy experience in token listing reviews.

Numerous security incidents originate from a project team's deliberate choices.

A contract may be entirely compliant from a technical standpoint, with owner controls set within expected boundaries, but the team can still opt to use those controls at a given time—altering trading conditions, activating blacklists, or issuing more tokens.

Code-wise, such moves are lawful. An audit report often does not identify these as risks since they are built into the contract's design.

This explains the necessity for a further protection layer on top of technical checks.

Gate applies rigorous project vetting during the token onboarding process and demands written pledges from teams to refrain from malicious activity, monitoring their adherence to these pledges.

This added layer targets what audits miss: a clean code base does not guarantee a team will avoid user-harming decisions.

Listed projects are subject to recurring security checks and on-chain surveillance to monitor contract activity.

Users retain the ability to view a contract's current risk profile whenever they wish.

Q2. Given that a single audit cannot assure lasting safety, what adjustments should project teams and the wider industry make?

Gate Security Team:

A structural feature of the crypto sector is that much of its activity—particularly in DeFi—resembles modular finance.

Numerous platforms are assembled from common building blocks: smart contracts, code libraries, wallets, oracles, bridges, connectivity services, web interfaces, and update distribution systems.

Consequently, the issue is not confined to the security of a project's own contracts but extends to the reliability of each connected component.

A failure in an upstream element can cascade financial damage down the dependency chain.

Reviewing large-scale incidents, the source of the problem frequently lay beyond the core protocol logic—in a vendor, a development tool, software distribution, or the user approval flow for transfers.

Adam, Partner at GoPlus:

A fresh attack paradigm has formed and is expanding quickly: attackers leverage automated instruments to find weaknesses with high efficiency.

Assaults have shifted from specialist manual exploration to a production-line method.

If the field continues to rely solely on commissioning an audit report before a launch or contacting a security firm after a breach is found, it resembles bringing a bow and arrow to a machine-gun fight.

The sole viable strategy is to match the attackers' efficiency with equally potent defensive tools.

On an industry scale, the required transition is from reliant on one-off audits or reactive specialist fixes towards continuous security across the entire lifecycle.

GoPlus's DeepScan solution, a three-stage smart contract security model, offers a usable closed-loop system.

Before launch — Token security self-check: Spot possible backdoor threats in minutes, including honeypot tokens, uncontrolled minting, blacklists, unusual transaction fees, and broad owner controls.

At launch — AI smart contract auditing: Perform detailed scrutiny of source code, permission structures, and operational logic. Identify weaknesses in syntax and business logic, and produce a structured audit output.

After launch — Continuous security monitoring and regular checks: Observe new vulnerabilities, attack events, and real-time hazards from external dependencies like oracles, bridges, and third-party protocols. Issue periodic risk alerts and schedule recurring contract reviews and ongoing audits.

Q3. In what ways has the process of finding vulnerabilities changed recently, and how does the security framework compare between on-chain and exchange custody?

Adam, Partner at GoPlus:

In the near term, attackers clearly have an expanded set of methods for discovering flaws.

Three factors account for this.

Automated tools have significantly lowered the barrier to vulnerability discovery. Tasks that once demanded several weeks from top researchers can now be executed by automated assault pipelines in a matter of minutes.

There is an enormous number of older contracts on-chain that passed audits years ago. These contracts form a rich source of possible vulnerabilities for attackers.

Attackers only need one successful exploit. A single weak point can be enough to extract funds, while defenders have to guard against all possible flaws.

Hackers may need only a few minutes to turn these vulnerabilities into stolen funds. Yet defenders are equally capable of locating those same flaws in a comparable timeframe.

The crucial factor is whether the project team deploys the appropriate tools before the attackers do.

More significantly, defenders hold three structural edges over attackers.

First-mover advantage. Defenders can inspect contracts repeatedly, both prior to launch and during operation. Attackers can only count on defenders having skipped those checks.

Cost advantage. AI-based audits are available on a per-check or yearly subscription model, keeping them cheap enough for frequent and thorough application.

Compounding security knowledge. Knowledge bases grow with each new incident. The more these protective systems are employed, the more effective they become.

The identity of the asset protector and the nature of the threats involved vary completely depending on whether assets are held on-chain or on an exchange.

On-chain self-custody: Security = Private key security + Smart contract security.

The user bears full accountability for protection. The loss or theft of a private key leaves no customer support channel to turn to.

Each interaction carries on-chain dangers such as approval exploits, phishing signatures, and honeypot tokens.

The offsetting benefit is that asset safety does not hinge on any platform's solvency.

Exchange custody: Security = Platform security + Account security.

The platform handles private key administration using hot and cold wallet separation, multi-signature controls, and risk management frameworks.

Essentially, the user outsources technical security to the exchange.

Nevertheless, users must safeguard their own accounts with robust passwords, two-factor authentication, phishing awareness, and careful API key handling.

Selecting a reputable exchange is likewise critical.

In summary, on-chain security revolves around safeguarding private keys and managing individual behavior, whereas exchange security centers on platform trustworthiness and protective systems.

The first scenario tests the user's understanding of Web3 safety. The second evaluates the exchange's set-up as well as the user's account discipline.

Q4. What security enhancements has Gate implemented as a trading venue?

Gate Security Team:

Firstly, the platform carries out recurring security reviews of listed initiatives and watches contract activity via on-chain monitoring.

Contract upgrades, permission alterations, and irregular large-scale trades all warrant ongoing scrutiny.

The initial security check performed at the time of listing has a finite lifespan, comparable to the audit reports previously outlined.

Users are able to examine the current risk signals of a given contract at any moment.

Turning to the platform itself, Gate keeps its security bug bounty program active for global researchers.

Individuals who uncover weaknesses can report them via sec@gate.com, support tickets, or the HackenProof system.

Gate argues that project teams must tolerate security inspection, and the platform itself should abide by the same standard. Security demands ought not be unilateral.

Regarding account safety, the recommendation is against hunting for one "safest location" for all funds. Splitting assets based on usage frequency is more sensible.

Funds intended for regular trading can stay in the spot wallet for quick access. Assets held for six months or longer are better placed in Gate Vault.

Gate Vault relies on MPC technology combined with a 2-of-3 signing protocol.

The private key is split into three parts, stored on the user's device, with Gate, and with an independent outside party.

The complete key is never put together at any point, and neither Gate nor the third party can start a transaction alone.

Any outward transfer is also held for 48 hours before it goes through.

This 48-hour interval acts as a safety window for users, who can cancel the outgoing transfer at any point within it.

Should an incident occur, the hold period provides time for the user to recognize the issue and halt the transfer.

A further enhancement is the Gate Account Security Protection Plan.

The plan is built around the Security Score.

Earlier, account safety configurations were spread over multiple sections, covering login authentication, authenticator apps, two-factor verification, passkeys, trading caps, and withdrawal limits.

Users frequently had trouble gauging the completeness of their account protection.

The Security Score consolidates these elements into a single grade between 0 and 100.

Users can instantly identify which protections are active and which are absent. The system issues prompts to reinforce settings whenever the score shifts.

Holders of a Security Score of 80 plus an account in good standing are eligible to activate the protection plan.

When switched on, it delivers an extra safety layer beyond what users have already established.

Within the coverage term, unauthorized asset withdrawals from an account may qualify for compensation, provided the conditions are satisfied.

The payout ceiling for a single event is currently $200,000.

This cap is slated to rise, with tiered sums tied to VIP level going up to $1 million.

Claims need to be filed within 45 days of the event via the "My Protection" section by contacting security support.

Required documentation comprises a police report and records of the asset movements.

Q5. What components should a thorough audit report contain, and how should security scores, critical discoveries, and suggested fixes be applied?

Adam, Partner at GoPlus:

A report meant to drive decisions, not just be stored, must include a minimum of four sections.

Security Score (Quantifiable Rating) — For Initial Screening, Not Final Conclusions

Development teams can treat the score as a measurable standard for internal safety reviews and monitor variations with each update.

Exchanges can rely on it for initial token listing checks, dismissing projects that evidently fall short of safety thresholds early on.

General users can use the score as a starting point: steer clear of low-rated projects, and look deeper into the key findings of high-rated ones.

Key Findings (High-Risk Issues and Core Conclusions) — For Decision-Making

This part acts as the report's executive briefing.

It ought to point out which problems are critical enough to prevent a release and require resolution in advance.

For non-technical managers and exchange listing evaluators, grasping the key discoveries is typically enough.

Issue Details (Vulnerability Evidence and Impact Analysis) — For Identifying Problems

This segment targets technical personnel.

It must specify the exact location of the weakness, reaching the contract, function, and code line, plus the vulnerability category, severity, assault route, and primary cause.

Effective issue write-ups supply repeatable execution sequences and activation criteria, as opposed to a plain enumeration of issues.

Remediation Recommendations (Actionable Fixes) — For Closing the Loop

Suggestions ought to be precise, workable, and sufficiently elaborate for code-level execution.

Once corrections are applied, the contract needs to be re-scanned and re-tested to confirm the repairs.

Collectively, these phases constitute a full closed circuit: scoring, key findings, problem details, fixes, and re-examination.

Gate Security Team:

Drawing from its work building contract audit tools, the Gate team offers three additional observations.

First, the two sections most easily overlooked are often the ones that should come first: audit objectives and limitations, and the scope of the audit.

Gate's reports are built around nine dimensions: audit targets and constraints, scope, severity classification, priority ranking, vulnerability specifics, risk channels, threat modeling, critical function assessment, and fix guidance.

Yet the opening two elements determine whether the audience misinterprets the full document.

Without a clear statement of constraints, readers might believe the audit addresses every possible risk.

Without defined scope, it is impossible to know if the review covered just the core contract or also included liquidity pools, strategy agreements, oracles, and outside connections.

Numerous marketing claims simply state "Audited" without clarifying what was actually examined.

Such phrasing conveys almost no meaningful insight.

Second, when reviewing key findings, users should consider risks together, even if each individual feature does not qualify as a vulnerability.

A typical pattern emerges in audit documents.

The contract owner can blacklist addresses and freeze assets.

Trading pairs can be reset, blocking regular users from moving tokens.

Minimum holding thresholds can stop users from liquidating their full positions.

A sole owner can modify several key rules at any moment.

Looked at individually, these four attributes could all be regarded as standard design elements.

Assessed as a set, though, they reveal that contract authority is heavily centralized in one individual.

Third, users should understand how the report was generated, because that determines the boundaries of its reliability.

The process for contract auditing at Gate unfolds in three phases.

The initial stage is static analysis, which inspects fundamental hazards like access controls, reentrancy, price manipulation, flash loans, and logical coherence.

The next stage is business scenario modeling. Core interaction patterns are derived from the contract, business flows and edge cases are validated, and issues that might escape rule-based detection are uncovered.

The last stage is semantic verification. Vital business pathways are reviewed individually to verify the reality of risks flagged in earlier stages.

The third phase mainly aims to cut down on false positives.

Reports cluttered with incorrect alarms quickly exhaust users' patience, leading them to possibly abandon the review procedure altogether.

Consequently, the false-positive rate is a key factor in whether a security tool sees regular use.

Q6. What hands-on safety steps can standard users implement immediately?

Adam, Partner at GoPlus:

Check token security before trading.

Before purchasing a fresh token, users should review its safety profile.

Specific attention should go to possible backdoors like honeypot tokens, uncontrolled minting, blacklisting functions, irregular trading fees, and expansive owner controls.

Regularly clean up contract approvals.

Users ought to cancel permissions given to DApps that are no longer in use, with special emphasis on unlimited allowances.

A large number of theft cases stem from difficulties with contracts users had previously approved.

Strengthen account security.

Employ robust passwords and activate two-factor verification.

Apply minimal privilege rules to API keys and avoid authorizing withdrawal rights to unverified applications.

Make phishing prevention second nature.

Confirm domain names before authorizing any action, steer clear of links delivered in private communications, and treat airdrops, support messages, and exceptionally high staking yields with suspicion.

Phishing materials are growing more persuasive, requiring users to stay logical and vigilant constantly.

Separate assets according to their purpose.

Only the minor sums required for daily operations should reside in hot wallets.

Hardware wallets are advised for larger positions.

Spreading assets across different storage methods lowers concentration risk.

Pay attention to a project's approach to security, not just its audit reports.

A project's commitment to ongoing audits and security surveillance mechanisms carries greater weight than a report from years earlier.

Preference should go to initiatives that treat security as a priority and are transparent about the design and upkeep of their protective systems.

Gate Security Team:

The Gate team describes Adam's suggestions as thorough and seeks to link some of them to Gate's own practical features.

Check token security before trading.

Users can employ Gate AI's contract audit tool directly.

Entering a contract address delivers a report in a few minutes.

Attention should center on four categories: owner authority, blacklists and trade constraints, minting rights, and transaction fees.

A red flag in any single category warrants halting the evaluation entirely.

Strengthen account security by raising your Security Score above 80.

Items such as fund passwords, authenticator apps, two-factor authentication, anti-phishing codes, passkeys, daily withdrawal ceilings, and withdrawal channel administration are all part of the checklist.

Users simply follow the instructions and fill in each entry.

The key benefit of the Security Score is converting disjointed settings into a structured list, relieving users of the need to prioritize protections on their own.

Qualifying users who exceed a score of 80 can also enable the Account Security Protection Plan, gaining an extra defense after tightening their own account safety.

Use two existing tools to protect against phishing.

Messages claiming to be from Gate should first be checked via the Official Verification Channel to confirm the domain or email address.

Genuine Gate emails always carry the user's personal Anti-Phishing Code. Correspondence lacking this code should be considered fraudulent.

Check approval amounts carefully before signing.

A contract might be sound on its own, yet that does not guarantee the safety of the transaction a webpage requests a signature for.

A trustworthy DApp typically demands only the amount necessary for the specific operation.

An immediate request for unlimited approval is itself a cause for caution.

When a wallet pop-up shows only an unintelligible string of characters, declining the signature is consistently safer than signing and investigating later.

In closing, the article stresses that security is a fluid condition, not a fixed one.

Deploying a project post-audit is merely the start of the security task.

For project teams, this places greater weight on post-launch monitoring than on the audit document itself.

For exchanges, it implies that listing a token is only the start of the vetting process.

For everyday users, the short period spent on reviewing a transaction before authorization stands as one of the cheapest safety measures available, though it is also one of the most easily missed.

No security certification provides permanent immunity.

When every participant adds one more step, the advantage moves towards the defenders.

About Gate

Gate was launched in 2013 by Dr. Han and ranks among the premier cryptocurrency and integrated finance platforms. It covers asset management, trading, and payments, catering to more than 63 million users internationally. The platform facilitates trading of over 5,400 digital tokens and 12,800 stock assets and ETFs, besides offering traditional finance assets like metals, stocks, indices, forex, and commodities. Gate is recognized for being an early adopter of 100% Proof of Reserves. Its suite comprises Gate Money, Gate Wallet, Gate Ventures, Gate for AI Agent, and other services.

Disclaimer:

This material is not an offer, solicitation, or suggestion. Independent professional guidance should be sought prior to investment choices. Gate may limit or forbid particular services in certain regions. Further details are available in the User Agreement.

Share to

Disclaimer: this article comes from third-party media and is provided for reference only. It does not constitute investment advice. Crypto and other financial products carry significant price volatility risk, so please make your own decisions carefully.

Related articles