- Home
- Security Audits
- Shopping.io
Web3 · Smart Contract Audit
Shopping.io Security Audits
softstack has completed 7 smart contract audits for Shopping.io between January 2021 and September 2022, reporting 20 findings in total (3 high, 2 medium, 5 low and 10 informational). Every report is published in the softstack public audit archive.
Key facts
- Client
- Shopping.io
- Audits completed
- 7
- First audited
- Latest audit
- Chains
- Ethereum
- Languages
- Solidity, JavaScript
About the project
Shopping.io is a crypto commerce service that lets shoppers buy goods from major online retailers and pay with cryptocurrency. The platform pairs an AI shopping assistant called ShopGPT with a checkout flow that settles orders in crypto. Established in December 2020, it handles international shipping and order tracking, and its SHOP token is issued on Ethereum.
Findings
Combined across all 7 reviews softstack has completed for Shopping.io. Each report is broken out below.
Reports
Newest first. Every report covers its own scope and commit.
Staking & Exchange smart contract audit
0Critical2High1Medium4Low1InformationalScope
Source repositorygithub.com/dchizhevskiy/shop-staking-truffleComponents reviewed
5 modules · 5 files- Exchange.sol
- NftStaking.sol
- SpiExtStaking.sol
- truffle-config.js
- hardhat.config.js
All 9 findings
ID Title Severity Status 6.2.1Price Conflict The users can buy tokens using the buyWithUSD or the buyWithWei function, the first function require 1 USD to buy 1 token, meanwhile the second function requires only 1 Wei to buy 1 token.
High fixed 6.2.2Price Change Can Lead To Free Tokens The users can buy tokens using the buyWithUSD or the buyWithWei function. The required amount to pay is in general (price * amountTokens) / (10**18).
High fixed 6.2.3Missing Transfer Verification The ERC20 standard token implementation functions return the transaction status as a Boolean. It is best practice to check for the return status of the function call, to ensure that the transaction was executed successfully.
Medium fixed 6.2.4Using .transfer() to transfer Ether .transfer() and .send() are recommended as best-practice, to prevent reentrancy attacks, because they only forward 2300 gas, the gas repricing of opcodes in the future may require more than 2300 gas, therefore the transaction will never…
Low fixed 6.2.5Missing Value Verification Certain functions lack a value safety check, the values of the arguments should be verified to allow only the ones that comply with the contract’s logic.
Low fixed 6.2.6Zero Address Checks Missing In the current implementation several functions are not checking for zero addresses. The address- type arguments should include a zero-address test, otherwise, the contract’s functionality may become inaccessible.
Low fixed 6.2.7The Owner Can Renounce Ownership Generally, the account that deploys the contract is also its owner. Consequently, the owner is able to engage in certain privileged activities in his own name.
Low acknowledged 6.2.8Floating Pragma Version Identified It is recommended to specify a fixed compiler version to ensure that the bytecode produced does not vary between builds. This is especially important if you rely
Informational acknowledged 6.2.9Spelling Or Grammatical Errors Spelling and grammatical errors were identified in the codebase. Fixing these mistakes can help improve the end-user experience by providing clear information on errors encountered and improve the maintainability and auditability of the…
Informational wont-fix GSPI Club smart contract audit
0Critical0High0Medium0Low2Informational0 of 2 resolved
Scope
Components reviewed
1 module · 1 file- gspi_club.sol
All 2 findings
ID Title Severity Status 5.1.1Missing natspec documentation Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.
Informational acknowledged 5.1.2A floating pragma is set Code Snippet Result/Recommendation The current pragma Solidity directive is ^0.4.26; It is recommended to specify a fixed version to ensure that the
Informational acknowledged GSPI Staking smart contract audit
0Critical1High1Medium0Low4Informational2 of 6 resolved
Scope
Components reviewed
1 module · 1 file- gspi_staking.sol
All 6 findings
ID Title Severity Status 5.1.1Unsecure calculation Code Snippet Result/Recommendation The calculations could cause unhandled errors such as integer under- or overflow and division by zero. Overall We recommend using the OpenZeppelin library SafeMath to avoid unsecure calculations.
High fixed 5.1.2Wrong import of OpenZeppelin library Code Snippet Result/Recommendation In the current implementation, OpenZeppelin files are added directly into the
Medium acknowledged 5.1.3A floating pragma is set Code Snippet Result/Recommendation The current pragma Solidity directive is ^0.5.13; It is recommended to specify a fixed version to ensure that the
Informational fixed 5.1.4Hardcoded address Code Snippet Result/Recommendation The contract contains unknown address. This address might be used for some malicious activity.
Informational acknowledged 5.1.5Missing natspec documentation Code Snippet Result/Recommendation Solidity contracts can use a special form of comments to provide rich documentation for functions, return variables and more.
Informational acknowledged 5.1.6Old pragma version Code Snippet Result/Recommendation Old pragma version can lead to errors Line 1 pragma solidity ^0.5.13; Use at least 0.6.12 6.
Informational acknowledged SPI Staking smart contract audit
0Critical0High0Medium1Low2Informational0 of 3 resolved
Scope
Components reviewed
1 module · 1 file- spi_staking.sol
All 3 findings
ID Title Severity Status 5.1.1Locking scenario Code Snippet Result/Recommendation If there is no reward sent to the contract with the addReward function, the contract runs out of balance and locks user’s staked SPI.
Low acknowledged 5.1.2A floating pragma is set Code Snippet Result/Recommendation The current pragma Solidity directive is ^0.8.3; It is recommended to specify a fixed version to ensure that the
Informational acknowledged 5.1.3Event not emitted Code Snippet Result/Recommendation The StakeClaimed event is defined but never emitted. Line 34 event StakeClaimed(address user, uint256 amount); We recommend emitting the event after claiming stake in the unstake function.
Informational acknowledged GSPI Token (Shopping.io) smart contract audit
0Critical0High0Medium0Low0InformationalNo security findings reported.
Scope
Source repositorygithub.com/binance-chain/bsc-genesis-contractComponents reviewed
2 modules · 2 files- gspi_token.sol
- GSPI_Token.sol
Staking Contract (Shopping.io) smart contract audit
0Critical0High0Medium0Low1Informational0 of 1 resolved
Scope
Components reviewed
1 module · 1 file- spi_staking.sol
All 1 findings
ID Title Severity Status 5.1.1Unusual symbol extension Code Snippet Result/Recommendation Symbol extension is not consistently used. Fixing these mistakes can help improve the end-user experience by providing clear and consistent symbol extensions.
Informational acknowledged SPI Token (Shopping.io) smart contract audit
0Critical0High0Medium0Low0InformationalNo security findings reported.
Scope
Components reviewed
1 module · 1 file- spi_token.sol
About this engagement
A smart contract audit reviews on-chain code for flaws an attacker could exploit. Engineers trace how assets move through the contracts, check who can call privileged functions, and test the arithmetic, external calls and upgrade paths. Each finding is rated by severity, and fixes are re-checked before the final report.
How softstack runs smart contract auditsMethodology
Review process
Scoping and threat modelling
The commit hash is frozen and the attack surface is mapped: asset flows, trust assumptions, privileged roles and the external systems the code depends on.
Automated analysis
Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.
Manual code review
Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.
Adversarial testing
Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.
Reporting
Every finding is documented with a severity rating, its impact, the steps to reproduce it and a concrete remediation the team can act on.
Remediation verification
Submitted fixes are re-reviewed against the original finding, and the final report records the resolved state of each one.
Standards and references
- SWC RegistrySmart Contract Weakness Classification
- CWECommon Weakness Enumeration
FAQ
Shopping.io was audited by softstack GmbH, a German Web3 security and software company based in Flensburg and certified to ISO/IEC 27001 by TÜV SÜD. softstack has completed 7 smart contract audits for Shopping.io between January 2021 and September 2022. The published reports are linked on this page and in the softstack public audit archive.
7 separate reviews, the first in January 2021 and the most recent in September 2022. Each one covers its own scope and commit, and is listed individually on this page.
20 findings across all 7 reviews: 3 high, 2 medium, 5 low and 10 informational.
Each report covers the code as it stood at the commit it names, the most recent in September 2022. Any code changed after that point is outside the reviewed scope.
Related audits
Browse all security auditsDisclaimer
This audit represents a point-in-time security assessment of the reviewed codebase and is intended for informational purposes only. While Softstack applies industry-standard security review methodologies, no audit can guarantee the absence of vulnerabilities, bugs, or other security risks. This report does not constitute financial, legal, regulatory, or investment advice, nor does it endorse the project, its business model, products, or services. Security is an ongoing process, and we strongly recommend conducting a new assessment following any material code changes or at least every 6 months to address newly emerging threats, vulnerabilities, and ecosystem developments.