GOExchangeToken security record
As of 3 Nov 2026, GOExchangeToken has 1 audit report on Trustblock, by Quantstamp, dated 24 Jan 2019. That report lists no open critical findings.
Record last updated . It holds audits, findings and contracts up to Nov 2026, and incidents up to Oct 2026. Trustblock does not review code.
Audits1
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| GOExchangeToken | Security firm: Quantstamp | Date: | Scope: Files named in the report | No open critical findings | Open · certificate.quantstamp.com |
Findings2
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 0 | 2 |
LowAllowance Double-Spend ExploitGOExchangeToken · Quantstamp · 24 Jan 2019Fixed
As it presently is constructed, the contract is vulnerable to the allowance double-spend exploit, as with other ERC20 tokens.
Open the reportLowGoExchangeToken explicitly extends ERC20 although it is already extended by ERC20BurnableGOExchangeToken · Quantstamp · 24 Jan 2019Fixed
GoExchangeToken explicitly extends ERC20, ERC20Detailed, and ERC20Burnable. There is no need to list ERC20 as it is already extended by ERC20Burnable.
Open the reportContracts
No deployed address is recorded for these audits.
The reports name a repository or files. Open a report to see its scope.
Show this on your site
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Content
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="goexchangetoken"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us