Castleswap Finance Ready For Rug Pull
Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' section to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.
It appears that this smart contract is ready to take user funds, containing deliberate exploits.
This is a global/international case not involving a specific country.
About Castleswap Finance
"Yield Farming Castle for Knights of BSC." "Stake LP tokens to earn Castle. Deposit Fee will be used to buyback Castle."
"The MasterChef contract contains the updateLiqProvider function that allows the contract owner (not a TimeLock) to transfer LP tokens to itself, resulting in a possible rug pull at any time. Be cautious and DO NOT engage."
"Contains HARD RUG code that can withdraw all tokens from all pools. DO NOT STAKE IN THIS CONTRACT"
"They also have another contract with hard rug code, 0x29FE9dB5…4040 – do not stake in that one either. Just avoid this project altogether!"
This is a global/international case not involving a specific country.
The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.
Include:
- Known history of when and how the service was started.
- What problems does the company or service claim to solve?
- What marketing materials were used by the firm or business?
- Audits performed, and excerpts that may have been included.
- Business registration documents shown (fake or legitimate).
- How were people recruited to participate?
- Public warnings and announcements prior to the event.
Don't Include:
- Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
- Anything that wasn't reasonably knowable at the time of the event.
There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.
The Reality
This sections is included if a case involved deception or information that was unknown at the time. Examples include:
- When the service was actually started (if different than the "official story").
- Who actually ran a service and their own personal history.
- How the service was structured behind the scenes. (For example, there was no "trading bot".)
- Details of what audits reported and how vulnerabilities were missed during auditing.
What Happened
The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.
| Date | Event | Description |
|---|---|---|
| July 28th, 2021 12:00:00 AM | Main Event | Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here. |
Total Amount Lost
No funds were lost.
How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?
Immediate Reactions
How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?
Ultimate Outcome
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?
Total Amount Recovered
There do not appear to have been any funds recovered in this case.
What funds were recovered? What funds were reimbursed for those affected users?
Ongoing Developments
What parts of this case are still remaining to be concluded?
Prevention Policies
Do not use this project.
References
Contract Address 0x29FE9dB5B2c7a512Ec0aC122D11ED899e5524040 | BscScan (Aug 20)
CastleSwap – RugDoc (Aug 20)
Twitter / Account Suspended (Aug 20)
Castle Finance (Aug 20)