View source for Ramses Exchange Reward Distribution Logic Vulnerability

{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/ramsesexchangerewarddistributionlogicvulnerability.php}}
{{Unattributed Sources}}

[[File:Ramsesexchange.jpg|thumb|Ramses Exchange Logo/Homepage]]Ramses Exchange is an online decentralized exchange platform which allows swapping between pools, contributing liquidity, or voting in their decentralized governance. On October 23rd, an error in their reward distribution logic was exploited to gain an attacker $93k. Multiple third parties published analyses of the exploit. It does not appear that the Ramses Exchange team has publicly acknowledged the attack, while they appear to have already been running a competitive audit competition. It is unclear whether the attack will have any effect on platform users.<ref name="arbiscan-16841" /><ref name="ramses-16842" /><ref name="ramsesdocs-16843" /><ref name="solidityscanblog-16844" /><ref name="diligence-16845" /><ref name="coinmonksmedium-16846" /><ref name="code4renatwitter-16847" /><ref name="ramsesexchangetwitter-16848" /><ref name="ramsesexchangetwitter-16849" />

== About Ramses Exchange ==
"Welcome to Ramses Exchange. Swap tokens, provide liquidity, vote, and more."

"Ramses is a next-generation AMM designed to serve as Arbitrum's central liquidity hub, combining the secure and battle-tested superiority of Uniswap v3 with a custom incentive engine, vote-lock governance model, and streamlined user experience.

RAMSES places a strong emphasis on fostering a vibrant and engaged ecosystem. As part of this commitment, RAMSES will launch with a focus on providing veNFTs to top protocols on Arbitrum. These veNFTs empower protocols to actively manage their positions in a way that aligns with the best interests of their platforms.

RAMSES is dedicated to achieving a high level of decentralization while ensuring the platform remains functional and efficient. To strike this balance, RAMSES establishes a council comprising trusted entities from the broader community. This council is responsible for making decisions in emergency situations, ensuring the platform's integrity and security are upheld.

RAMSES incorporates some of the most advanced features implemented in existing DEXes. These features have been widely recognized and adopted by many users. RAMSES aims to provide a seamless and user-friendly experience while leveraging the innovative capabilities and underlying value it brings to the market.

By these core tenets, RAMSES seeks to bring forth a DEX that not only aligns with the original vision of Solidly but also introduces novel functionalities and prioritizes the needs of the community."

== 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 contract of Ramses Exchange on Arbitrum was attacked, resulting in a loss of approximately $93,000."
{| class="wikitable"
|+Key Event Timeline - Ramses Exchange Reward Distribution Logic Vulnerability
!Date
!Event
!Description
|-
|October 23rd, 2024 6:00:30 PM MDT
|Arbitrum Attack Transaction
|The blockchain transaction on the arbitrum chain which is the attack on Ramses Exchange.
|-
|November 4th, 2024 8:16:00 AM MST
|Competitive Audit Conclusion
|The Ramses Exchange team announces the conclusion of their competitive audit and that they are excited to look through the findings.
|}

== Technical Details ==
"On October 24th, 2024, the Ramses Exchange (@RamsesExchange) on Arbitrum suffered a loss of nearly $93,000 due to a flaw in its reward distribution logic. The vulnerability allowed the attacker to repeatedly claim rewards across multiple tokenIds without a corresponding reduction in the total rewards supply. By depositing tokens and invoking getPeriodReward() with different NFTs, the attacker drained reward pools, exploiting the contract’s failure to adequately track reward limits per period. The exploit primarily targeted accumulated incentives and fees rather than the underlying liquidity provider funds."

"The root cause is that the FeeDistributor contract did not decrease tokenTotalSupplyByPeriod after each reward claim, resulting in an inflated total reward supply. This oversight allowed repeated reward calculations from the same supply, leading to excess distributions."

== Total Amount Lost ==
The total amount lost has been estimated at $93,000 USD.

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?
== Individual Prevention Policies ==
{{Prevention:Individuals:Placeholder}}

{{Prevention:Individuals:End}}

== Platform Prevention Policies ==
{{Prevention:Platforms:Placeholder}}

{{Prevention:Platforms:End}}

== Regulatory Prevention Policies ==
{{Prevention:Regulators:Placeholder}}

{{Prevention:Regulators:End}}

== References ==
<references><ref name="arbiscan-16841">[https://arbiscan.io/tx/0xb91c4e0debaf0feb1f20c979eebc1282c8024ae299ef5903591badcf1f4938bb Arbitrum One Transaction Hash (Txhash) Details | Arbitrum One] (Accessed Nov 15, 2024)</ref>

<ref name="ramses-16842">[https://www.ramses.exchange/ R A M S E S] (Accessed Nov 15, 2024)</ref>

<ref name="ramsesdocs-16843">[https://docs.ramses.exchange/ What is RAMSES? | RAMSES] (Accessed Nov 15, 2024)</ref>

<ref name="solidityscanblog-16844">[https://blog.solidityscan.com/ramses-exchange-hack-analysis-288ec1b806ff Ramses Exchange Hack Analysis. Overview: | by Shashank | Oct, 2024 | SolidityScan] (Accessed Nov 15, 2024)</ref>

<ref name="diligence-16845">[https://diligence.consensys.io/audits/2024/08/ramses-v3/ Ramses V3 | Consensys Diligence] (Accessed Nov 15, 2024)</ref>

<ref name="coinmonksmedium-16846">[https://medium.com/coinmonks/unraveling-the-90k-mystery-inside-ramses-exchanges-reward-exploit-3972812b2eff Unraveling The 90k Mystery Inside Ramses Exchanges Reward Exploit] (Accessed Nov 15, 2024)</ref>

<ref name="code4renatwitter-16847">[https://twitter.com/code4rena/status/1848817293545115990 @code4rena Twitter] (Accessed Nov 15, 2024)</ref>

<ref name="ramsesexchangetwitter-16848">[https://twitter.com/RamsesExchange/status/1850917865173487697 @RamsesExchange Twitter] (Accessed Nov 15, 2024)</ref>

<ref name="ramsesexchangetwitter-16849">[https://twitter.com/RamsesExchange/status/1853456332952617149 @RamsesExchange Twitter] (Accessed Nov 15, 2024)</ref></references>