KyotoSwap security record
As of 3 Nov 2026, KyotoSwap has 1 audit report on Trustblock, by CertiK, dated 21 Apr 2023. That report lists no open critical findings.
Record last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Audits1
Newest first
Findings17
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 3 | 1 |
| Low | 9 | 0 | 4 |
MediumBurnt token not transferred to the "burn" addressKyotoSwap · CertiK · 21 Apr 2023Fixed
In the contract `MasterChef`, the burnt token would not be transferred to the `address(0)` or the burn address(`0x000000000000000000000000000000000000dEaD`). It actually transfers the tokens to the `_owner` address. Also, almost 99%(`989202815829/1e12`) of the reward Kswap tokens will be transferred to the `_owner` address.
Open the reportLowDead CodeKyotoSwap · CertiK · 21 Apr 2023Fixed
In the contract `TokenLocker`, the function `redeem()` will call the function `LibTokenLocker.enforceLockExistsAndExpired()` to check the lock status before calling `LibTokenLocker.redeem()`. The function `LibTokenLocker.enforceLockExistsAndExpired()` will revert the transaction if the lock expiration time has not passed(`block.timestamp < lock.expiresAt`). However, the function `LibTokenLocker.redeem()` supports partial redemption before the `lock.expiresAt` by the following code snippet. The `if` condition will never be true when calling from `TokenLocker.redeem()`, otherwise, the transaction has already been reverted in the function `LibTokenLocker.enforceLockExistsAndExpired()`. On the contrary, the function `TokenLocker.deposit` supports partial redemption without calling the function `LibTokenLocker.enforceLockExistsAndExpired()`. Thus, the user can get partial redemption and all the previously locked token back. ```solidity=144 if (block.timestamp < lock.expiresAt) { reward = calculateRewardDiff( reward, lock.duration, (block.timestamp - lock.lockedAt) ); } ``` Also, the function `LibTokenLocker.redeem()` will burn all the locked amount and this contradicts the logic that the user can partially unlock and get the rewards.
Open the reportLowInitial Value Of `lastRewardBlock`KyotoSwap · CertiK · 21 Apr 2023Fixed
The `lastRewardBlock` is initialize to `block.number + 200` when the `block.number >= _startBlockNumber`. Thus, the user may deposit immediately to the new added pool, but can only get rewards after 200 blocks.
Open the reportLowMissing Zero Address ValidationKyotoSwap · CertiK · 21 Apr 2023Fixed
Addresses should be checked before assignment or external call to make sure they are not zero addresses. ```solidity=530 treasury = _treasury; ``` - `_treasury` is not zero-checked before being used.
Open the reportLowRecommended explicit pool validity checksKyotoSwap · CertiK · 21 Apr 2023Fixed
There's no sanity check to validate if a pool is existing.
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="kyoto-swap"></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