<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?action=history&amp;feed=atom&amp;title=Float_Protocol_Rari_Capital_Weak_Oracle</id>
	<title>Float Protocol Rari Capital Weak Oracle - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?action=history&amp;feed=atom&amp;title=Float_Protocol_Rari_Capital_Weak_Oracle"/>
	<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Float_Protocol_Rari_Capital_Weak_Oracle&amp;action=history"/>
	<updated>2026-08-25T18:12:38Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.1</generator>
	<entry>
		<id>https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Float_Protocol_Rari_Capital_Weak_Oracle&amp;diff=5434&amp;oldid=prev</id>
		<title>Azoundria: Created page with &quot;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/floatprotocolraricapitalweakoracle.php}} {{Unattributed Sources}}  Float Protocol Logo/HomepageFloat Protocol's liquidity pool had limited liquidity, and was used by Rari Fuse to determine the eligibility to borrow assets. An attacker manipulated the price through a large purchase, then took out a loan using the inflated value, profiting $250k+ after all was said an...&quot;</title>
		<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Float_Protocol_Rari_Capital_Weak_Oracle&amp;diff=5434&amp;oldid=prev"/>
		<updated>2024-01-30T23:29:50Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/floatprotocolraricapitalweakoracle.php}} {{Unattributed Sources}}  &lt;a href=&quot;/cryptocurrencyhackscamfraudwiki/index.php?title=File:Floatprotocol.jpg&quot; title=&quot;File:Floatprotocol.jpg&quot;&gt;thumb|Float Protocol Logo/Homepage&lt;/a&gt;Float Protocol&amp;#039;s liquidity pool had limited liquidity, and was used by Rari Fuse to determine the eligibility to borrow assets. An attacker manipulated the price through a large purchase, then took out a loan using the inflated value, profiting $250k+ after all was said an...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/floatprotocolraricapitalweakoracle.php}}&lt;br /&gt;
{{Unattributed Sources}}&lt;br /&gt;
&lt;br /&gt;
[[File:Floatprotocol.jpg|thumb|Float Protocol Logo/Homepage]]Float Protocol's liquidity pool had limited liquidity, and was used by Rari Fuse to determine the eligibility to borrow assets. An attacker manipulated the price through a large purchase, then took out a loan using the inflated value, profiting $250k+ after all was said and done. It appears that the funds were ultimately returned.&lt;br /&gt;
&lt;br /&gt;
This is a global/international case not involving a specific country.&amp;lt;ref name=&amp;quot;ergobtctwitter-12910&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;web3isgoinggreat-12911&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;floatprotocoltwitter-12912&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;peckshieldtwitter-12913&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;snapshot-12914&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;etherscan-12915&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;floatprotocol-12916&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== About Rari Capital ==&lt;br /&gt;
&amp;quot;Float Protocol, DeFi Money. Decentralised Finance needs stability, but we can do better than the dollar.&lt;br /&gt;
&lt;br /&gt;
FLOAT tracks a basket of digital assets instead of trying to exactly match the price of a dollar. It is designed to change value over time corresponding to your digital purchasing power.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Float Protocol Pool 90 on @RariCapital pool suffered effects from a lack of liquidity in the Uniswap V3 FLOAT/USDC oracle which lead to severe price manipulation.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Our @RariCapital pool just experienced effects from a weak oracle. We're looking into the issue and will update with more information shortly.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;The attacker brought in &amp;gt;47 ETH via Tornado Cash and deployed an orchestrating contract.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Via the contract they swapped 47 ETH -&amp;gt; 129,447 USDC -&amp;gt; 77.5k FLOAT; this brought the vast majority of FLOAT out of the pool dramatically increasing the price within the FLOAT/USDC pool.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;The attacker waited for 2-7 minutes for the time weighted oracles to shift the price.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;At this point they were then able to deposit FLOAT into Rari Fuse at a vastly increased rate and borrow other assets, before selling the FLOAT back into the Uniswap V3 pool to return the price.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;The orchestrating contract still contains 250k USDC and 5 fFLOAT.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Lack of liquidity in the Uniswap V3 FLOAT/USDC oracle allowed an attacker to manipulate the prices within the pool, then deposit it at a much higher rate. The hacker pulled about 350 ETH (equivalent to $1.1 million) out of the pool, though according to PeckShield they later returned around $250,000 for some reason.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;The depositors primarily impacted were Float Protocol's treasury diversification funds, FRAX AMO, and FEI PCV deposits.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;As such we currently calculate there was 1 depositor of $25k DAI in user funds lost at this time, but are still collecting further information for a follow up proposal.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This is a global/international case not involving a specific country.&lt;br /&gt;
&lt;br /&gt;
The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.&lt;br /&gt;
&lt;br /&gt;
Include:&lt;br /&gt;
&lt;br /&gt;
* Known history of when and how the service was started.&lt;br /&gt;
* What problems does the company or service claim to solve?&lt;br /&gt;
* What marketing materials were used by the firm or business?&lt;br /&gt;
* Audits performed, and excerpts that may have been included.&lt;br /&gt;
* Business registration documents shown (fake or legitimate).&lt;br /&gt;
* How were people recruited to participate?&lt;br /&gt;
* Public warnings and announcements prior to the event.&lt;br /&gt;
&lt;br /&gt;
Don't Include:&lt;br /&gt;
* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.&lt;br /&gt;
* Anything that wasn't reasonably knowable at the time of the event.&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== The Reality ==&lt;br /&gt;
This sections is included if a case involved deception or information that was unknown at the time. Examples include:&lt;br /&gt;
&lt;br /&gt;
* When the service was actually started (if different than the &amp;quot;official story&amp;quot;).&lt;br /&gt;
* Who actually ran a service and their own personal history.&lt;br /&gt;
* How the service was structured behind the scenes. (For example, there was no &amp;quot;trading bot&amp;quot;.)&lt;br /&gt;
* Details of what audits reported and how vulnerabilities were missed during auditing.&lt;br /&gt;
&lt;br /&gt;
== What Happened ==&lt;br /&gt;
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.&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Key Event Timeline - Float Protocol Rari Capital Weak Oracle&lt;br /&gt;
!Date&lt;br /&gt;
!Event&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
|January 14th, 2022 2:28:52 PM MST&lt;br /&gt;
|Swap Completed&lt;br /&gt;
|The attacker completes their swap to manipulate the price and extract a profit.&lt;br /&gt;
|-&lt;br /&gt;
|January 14th, 2022 3:13:00 PM MST&lt;br /&gt;
|Tweet Sent Out&lt;br /&gt;
|Float Protocol sends out a tweet to notify users that their &amp;quot;pool just experienced effects from a weak oracle&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|January 14th, 2022 7:53:00 PM MST&lt;br /&gt;
|Follow On Post&lt;br /&gt;
|A follow up post-morten is posted by the Float Protocol team.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Technical Details ==&lt;br /&gt;
This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?&lt;br /&gt;
&lt;br /&gt;
== Total Amount Lost ==&lt;br /&gt;
The total amount lost has been estimated at $250,000 USD.&lt;br /&gt;
&lt;br /&gt;
How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?&lt;br /&gt;
&lt;br /&gt;
== Immediate Reactions ==&lt;br /&gt;
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?&lt;br /&gt;
&lt;br /&gt;
== Ultimate Outcome ==&lt;br /&gt;
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?&lt;br /&gt;
&lt;br /&gt;
== Total Amount Recovered ==&lt;br /&gt;
The total amount recovered has been estimated at $250,000 USD.&lt;br /&gt;
&lt;br /&gt;
What funds were recovered? What funds were reimbursed for those affected users?&lt;br /&gt;
&lt;br /&gt;
== Ongoing Developments ==&lt;br /&gt;
What parts of this case are still remaining to be concluded?&lt;br /&gt;
== Individual Prevention Policies ==&lt;br /&gt;
{{Prevention:Individuals:Placeholder}}&lt;br /&gt;
&lt;br /&gt;
{{Prevention:Individuals:End}}&lt;br /&gt;
&lt;br /&gt;
== Platform Prevention Policies ==&lt;br /&gt;
{{Prevention:Platforms:Placeholder}}&lt;br /&gt;
&lt;br /&gt;
{{Prevention:Platforms:End}}&lt;br /&gt;
&lt;br /&gt;
== Regulatory Prevention Policies ==&lt;br /&gt;
{{Prevention:Regulators:Placeholder}}&lt;br /&gt;
&lt;br /&gt;
{{Prevention:Regulators:End}}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references&amp;gt;&amp;lt;ref name=&amp;quot;ergobtctwitter-12910&amp;quot;&amp;gt;[https://twitter.com/ErgoBTC/status/1482157504436092934 @ErgoBTC Twitter] (Mar 15, 2023)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;web3isgoinggreat-12911&amp;quot;&amp;gt;[https://web3isgoinggreat.com/single/float-protocol-rari-capital-pool-exploited An attacker pulls about 350 ETH from Float Protocol's Rari Capital pool] (Jan 30, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;floatprotocoltwitter-12912&amp;quot;&amp;gt;[https://twitter.com/FloatProtocol/status/1482184042850263042 @FloatProtocol Twitter] (Jan 30, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;peckshieldtwitter-12913&amp;quot;&amp;gt;[https://twitter.com/peckshield/status/1482211298699923457 @peckshield Twitter] (Jan 30, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;snapshot-12914&amp;quot;&amp;gt;[https://snapshot.org/#/snapshot.floatprotocol.eth/proposal/0x16c8d5dbcfebf99ca31c3bb7bb31e6ead573d8eb300fcabd3c8c4d070d54dc48 Snapshot] (Jan 30, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;etherscan-12915&amp;quot;&amp;gt;[https://etherscan.io/tx/0x40db7bd89d2a3f7df2793ba4f5be9a2ca93463d6bb6af024e5cd1b73ff827248 https://etherscan.io/tx/0x40db7bd89d2a3f7df2793ba4f5be9a2ca93463d6bb6af024e5cd1b73ff827248] (Jan 30, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;floatprotocol-12916&amp;quot;&amp;gt;[https://floatprotocol.com/ Float Protocol] (Jan 30, 2024)&amp;lt;/ref&amp;gt;&amp;lt;/references&amp;gt;&lt;/div&gt;</summary>
		<author><name>Azoundria</name></author>
	</entry>
</feed>