Lunaray Token Security Scan Report

According to Lunaray Security Team, the Token contract security scanning platform has completed the automatic security scan of the RONIN Token contract and the security risk level is Low.

The scan result is only for general security vulnerabilities and is not used as the final contract security audit result, nor as investment advice for users. If you have any questions, please contact

The scan contract address:


The scan tool:

Lunaray Token Security

Scan result:

Onlyowner:There are one or more methods in the contract that only the administrator can operate.

Self transfer:There may be a risk of deflation if the same addresses are not identified at the time of transfer.

No events added:Failure to add method events may result in users or administrators being unable to determine the details of their actions.

Redundant code:There are unused internal methods in the contract, which may result in additional gas consumption.

timestamp:Timestamps may be manipulated by miners

Unused local variables:Unused local variables

Dangerous strict equivalence:Dangerous strict equivalence testing

Fake Recharge:The mild if/else-only judgment is a sloppy way of coding in sensitive function scenarios such as transfer, and will lead to false recharge vulnerabilities.

Hard coding: Unspecified constants that appear in the code can lead to problems such as poor readability of the code.

Incorrect modifier:Incorrect modifier

No safemath library:An integer variable can only have a certain range of numbers represented, and exceeding the range of values expressed by the variable type will result in an integer overflow vulnerability.

Public suicide function calls:Public suicide function calls

Re entrancy:The attacker builds a contract containing malicious code at an external address in the [Fallback function].

Unchecked empty address:No judgement is made on the address passed in, if the address is a address(0), the address cannot be modified again

Unchecked transfer return:Failure to check the method return value when sending tokens using the send or call.value methods in the contract code will lead to unexpected results.

Unspecified method visibility:The visibility of contract functions is public by default, so functions that do not specify any visibility can be called externally by the user.

Unused return values:The return value of an external call is not stored in a local or state variable

Using sha3:sha3 is not secure in solidity

Wrong storage usage:Objects that have not changed their state, using storage to initialize variables will increase gas consumption, risking overrunning the limit and increasing the risk of memory overwriting.


Lunaray social media












Lunaray takes a leading position in smart contract auditing and consulting service for blockchain security.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Clearing the mist around the ETH OGs and Shiba Inu connection (Part 1)

MultiVAC Open Source Code Overview

Lunaray Token Security Scan Report

Recap of OpenSwap AMA at Impossible Finance

Regulating Anonymity, Balancing Opposite Ends of The Spectrum

Vite Bi-weekly Report

[Skypeople]February Card New/Dev Note #5

A First Introduction to Blockchain

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


Lunaray takes a leading position in smart contract auditing and consulting service for blockchain security.

More from Medium

Lunaray Token Security Scan Report

100 NBA NFT Basketball Cards Stolen In Hack On Launch Day🏀

Beosin cryptocurrency tracing service is officially launched to smoothly solve stolen money into…

Lunaray Token Security Scan Report