GoPlus Security

• Name: GoPlus Security
• URL: https://gopluslabs.io/
• Category: wallet-security middleware company / transaction-simulation and screening operator / risk-verdict distribution infrastructure provider
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: GoPlus Security belongs as an entity note, not a protocol note. The useful question is who authors the token, address, approval, dapp, phishing-site, and transaction-simulation verdicts that downstream wallets, exchanges, and apps can turn into warnings, friction, or hard stops. The real control surface is the company-run interpretation and distribution stack that many partners can embed directly into signing and browsing flows.
• What it does:
  • Provides real-time security APIs covering token risk, malicious addresses, NFT risk, token approvals, dapp security information, phishing sites, signature decoding, and transaction simulation
  • Supports both EVM and Solana-oriented security surfaces, including Solana token analysis and transaction simulation for Solana and EVM flows
  • Ships official SDKs in multiple languages so wallets, apps, exchanges, and other platforms can wire GoPlus checks directly into their products
  • Extends beyond the core screening API into SafeToken issuance and token-locker tooling, but those are side branches rather than the center of the note
  • Maintains a public GitHub organization with official SDKs and adjacent security tooling, including AI-agent security repos, which shows the company trying to widen from onchain risk APIs into a broader security-control-plane pitch
• Key claims:
  • The homepage calls GoPlus The Leading Web3 and AI Agent Security Solutions and presents it as a decentralized security layer for Web3, which is useful vendor language because it shows the company wants to be read as foundational security infrastructure rather than a narrow scanner widget
  • The getting-started docs say GoPlus is building an open, permissionless, and user-driven User Security Network for Web3 and describe the APIs as delivering real-time, automated security intelligence
  • The docs enumerate a broad security product surface including Token Security, Malicious Address, NFT Security, Approval Security, dApp Security Info, Signature Decode, Phishing Site Detection, Solana token security, and both Solana and EVM transaction simulation APIs
  • The SDK materials show official Node.js support and point integrators to the API overview and SDK guide, which reinforces that direct partner embedding is central to the product rather than incidental
  • The combined API, SDK, and partner-facing language implies the real leverage is in risk-label policy, simulation coverage, false-positive handling, and how many downstream products inherit GoPlus verdicts with limited local review
• Whitepaper: No classic standalone whitepaper or litepaper is the important artifact here. The strongest primary materials remain the official site, docs portal, SDK docs, Node SDK README, and public GitHub organization; see ../whitepapers/goplus-security-primary-sources-2026-04-26.md.
• Sources:
  • https://gopluslabs.io/
  • https://docs.gopluslabs.io/docs/getting-started
  • https://docs.gopluslabs.io/docs/goplus-sdk
  • https://raw.githubusercontent.com/GoPlusSecurity/goplus-sdk-node/main/README.md
  • https://github.com/GoPlusSecurity

Why this company note belongs in the corpus

• GoPlus is analytically stronger as an operator note than as a project note because the meaningful question is not what protocol is this? but who is classifying risk and shipping those classifications into other products?
• Many downstream products do not consume only raw chain data; they import GoPlus-authored interpretations of whether a token, address, approval, domain, or transaction looks dangerous enough to warn on or block.
• That makes the entity boundary worth preserving. The company can quietly become part of the real execution policy for many wallets and apps even when users think they are just seeing a generic security check.

Internal linkages

• Legacy project-layer alias preserved for old links: goplus-security.
• Best adjacent wallet-safety comparisons: blockaid and blowfish.
• Best adjacent operator-risk comparison: hypernative.
• Positive-design companion on signer-facing authenticity: signer-intent-truth-security-object.
• Positive-design companion on keeping losses bounded after bad classifications or compromised sessions: post-authentication-bounded-loss-design.

Protocol / company boundary

• There is no especially clean standalone GoPlus protocol boundary doing the analytical work here.
• The useful surface is the company-run risk-classification, simulation, phishing-detection, and partner-distribution stack that sits between raw user intent and the final downstream warning or enforcement behavior.
• That is why GoPlus belongs in companies/: the real control question is who authors and distributes the screening truth that partners start treating as policy, not whether one part of the product menu can be described as a protocol.

Control surface

• Practical leverage sits in risk-label policy, simulation quality, source selection, false-positive and false-negative tradeoffs, partner integration defaults, and whether an output stays advisory or becomes a hard block.

• None of that is onchain. The visible wallet prompt is only the last inch of the stack; authority already accumulated when GoPlus or the integrating partner decided what counts as suspicious enough to surface or stop.

• If wallets, exchanges, or apps start treating GoPlus outputs as canonical risk truth, meaningful control shifts into that offchain interpretation layer even when the final signature still belongs to the end user or operator.

• Treat GoPlus as screening and policy middleware, not as a neutral protocol primitive.

• Last reviewed: 2026-08-13 UTC