ReFi Finance Runs Away
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.
ReFi Finance appears to have fully disappeared with user's funds. It's not clear what the contract originally did.
This is a global/international case not involving a specific country.
About ReFi Finance
"Reports of refi.finance exit scamming by calling a superuser function to change treasury boardroom implementation to steal 2600 BAS ($144K)."
"Weibo user “CryptoBlanker” broke the news: the refi.finance project party directly used the reserved setBoardroom() function to change the Boardroom address to the address it deployed. Light BAS was taken away 2,600, worth 111 ETH (about 144,000 US dollars)."
"He mentioned the project in his previous Weibo: refi.finance can use the share of three algorithmic stable coins to mine. The project needs to call the exitBoradRoom() function to end mining after each phase (every 6 hours) ends, and then call depositBoradRoom() to start the next round of mining. Only in the interval between the above two operations, users can access their own shares. That is to say, if the owner does not want to maintain the project one day, no one can retrieve their own shares."
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 |
|---|---|---|
| January 27th, 2021 12:00:00 AM | First Event | This is an expanded description of what happened and the impact. If multiple lines are necessary, add them here. |
Total Amount Lost
The total amount lost is unknown.
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
It is unknown how much was recovered.
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
References
SlowMist Hacked - SlowMist Zone (May 17)
refi.finance跑路，抽走超2600个BAS_快讯_鸵鸟区块链 (Jul 17)
refi.finance跑路 抽走超2600个BAS - CN币网 (Jul 17)
REFIBASFarm | 0x55937808414b760d802f5B0d6A806Db4BB8C529a (Jul 17)
Exit Scam: refi.finance Withdraws 2,600 BAS | CoinNess (Jul 17)
No Title (Jul 17)
哔哔News 人人都能看懂的区块链资讯 (Jul 17)