<?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=YAM_Finance_Incident</id>
	<title>YAM Finance Incident - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?action=history&amp;feed=atom&amp;title=YAM_Finance_Incident"/>
	<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=YAM_Finance_Incident&amp;action=history"/>
	<updated>2026-08-28T10:33:02Z</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=YAM_Finance_Incident&amp;diff=3810&amp;oldid=prev</id>
		<title>Azoundria at 16:14, 2 May 2023</title>
		<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=YAM_Finance_Incident&amp;diff=3810&amp;oldid=prev"/>
		<updated>2023-05-02T16:14:26Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;a href=&quot;https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=YAM_Finance_Incident&amp;amp;diff=3810&amp;amp;oldid=2184&quot;&gt;Show changes&lt;/a&gt;</summary>
		<author><name>Azoundria</name></author>
	</entry>
	<entry>
		<id>https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=YAM_Finance_Incident&amp;diff=2184&amp;oldid=prev</id>
		<title>Azoundria at 17:20, 17 February 2023</title>
		<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=YAM_Finance_Incident&amp;diff=2184&amp;oldid=prev"/>
		<updated>2023-02-17T17:20:53Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;a href=&quot;https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=YAM_Finance_Incident&amp;amp;diff=2184&amp;amp;oldid=704&quot;&gt;Show changes&lt;/a&gt;</summary>
		<author><name>Azoundria</name></author>
	</entry>
	<entry>
		<id>https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=YAM_Finance_Incident&amp;diff=704&amp;oldid=prev</id>
		<title>Azoundria: Created page with &quot;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/yamincident.php}}  YAM FinanceDespite an audit, YAM Finance launched with a coding error which caused governance tokens to be minted rapidly in the protocol. This doomed the project, and ended up with $750,000 worth of yCRV token stuck in the contract.  The project was relaunched in a new smart contract, and the second version was more successful.  This is a global/int...&quot;</title>
		<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=YAM_Finance_Incident&amp;diff=704&amp;oldid=prev"/>
		<updated>2023-01-25T17:40:12Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/yamincident.php}}  &lt;a href=&quot;/cryptocurrencyhackscamfraudwiki/index.php?title=File:Yamfinance.jpg&quot; title=&quot;File:Yamfinance.jpg&quot;&gt;thumb|YAM Finance&lt;/a&gt;Despite an audit, YAM Finance launched with a coding error which caused governance tokens to be minted rapidly in the protocol. This doomed the project, and ended up with $750,000 worth of yCRV token stuck in the contract.  The project was relaunched in a new smart contract, and the second version was more successful.  This is a global/int...&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/yamincident.php}}&lt;br /&gt;
&lt;br /&gt;
[[File:Yamfinance.jpg|thumb|YAM Finance]]Despite an audit, YAM Finance launched with a coding error which caused governance tokens to be minted rapidly in the protocol. This doomed the project, and ended up with $750,000 worth of yCRV token stuck in the contract.&lt;br /&gt;
&lt;br /&gt;
The project was relaunched in a new smart contract, and the second version was more successful.&lt;br /&gt;
&lt;br /&gt;
This is a global/international case not involving a specific country.&lt;br /&gt;
&lt;br /&gt;
== About YAM Finance ==&lt;br /&gt;
&amp;quot;YAM is a modified clone of Ampleforth, a stablecoin with dynamic supply. Depending on the demand, YAM and Ampleforth can increase or decrease the total supply to maintain the $1 peg. Supply is changed by calling a dedicated “rebase” function.&amp;quot; &amp;quot;Community-led DeFi stablecoin YAM managed to attract hundreds of millions of dollars in a matter of hours after it launched on Aug. 11.&amp;quot; &amp;quot;YAM’s key difference from Ampleforth is that it automatically bought yCRV tokens whenever supply increased.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;At 08:01 AM UTC, Aug-13-2020, the creator of YAM, @brockjelmore, tweeted about the failure of rescuing the $750,000 yCRV tokens locked in the governance contract.&amp;quot; &amp;quot;[A] single line of code doomed the Yam farmers&amp;quot;, &amp;quot;creat[ing] “Zimbabwe style” inflation.&amp;quot; &amp;quot;[A] bug in the rebase function meant that each call after the first one would “exponentially increase [supply] every time by 10^1e18.”&amp;quot; &amp;quot;The team wanted to use YAM in the project’s governance, but the rebase function issued excess YAM tokens to the project’s treasury, which diluted YAM holders’ governance power.&amp;quot; &amp;quot;The price plummeted by 99% within 24 hours, resulting in the “permanent destruction” of the governance contract. Curve tokens worth 750,000 USD It is locked and cannot be used.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;The team tried to fix the bug by initiating a voting process to stop rebasing until the project’s governance contract is swapped. However, the initiative failed despite high voter turnout.&amp;quot; &amp;quot;By the time the team realized nothing could be done to save the project, $750,000 of yCRV were already locked in the treasury.&amp;quot; &amp;quot;The team didn’t give up and eventually swapped the project’s governance module to a working one. YAM holders could migrate via a temporary smart contract.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Yam Finance all but collapsed ... following the discovery of [the] fatal error, but the project has since gained $200 million in total value locked.&amp;quot; &amp;quot;Yam is still the 7th largest Defi project according to total value locked (TVL).&amp;quot; &amp;quot;The project library suffered a serious loss of as much as 750,000 US dollars of Curve tokens.&amp;quot; &amp;quot;[P]rice plummeted 99%.&amp;quot; &amp;quot;After the bug announcement, the YAM token’s value dropped significantly as the token touched an all-time high of $167.66 per token. At the time of publication, the token is only worth $0.97 per YAM.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;[B]lockchain security company Peckshield [conducted] an audit of the migration contract.&amp;quot; “Following the audit, we will publish the report, deploy the migration contract, and enable migration through [the website],” the blog stated. Users will then need to burn their V1 tokens and mint new V2 tokens within 72 hours of the migration deployment. &amp;quot;[T]he Yam Finance team announced that the new [V3] protocol's migration would start at 8 PM UTC on Friday, September 18.&amp;quot; &amp;quot;V3 ha[s] successfully passed the audit performed by PeckShield.&amp;quot; &amp;quot;Following the migration, YAMv2 emerged. The token managed to climb to $32 but failed to repeat the previous success and returned to $25.7 by the time of writing.&amp;quot; &amp;quot;[T]here is a lot of work that can be done to improve Yam. Despite the last month of progress, the relaunch of Yam is truly a starting point.&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;
&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 - YAM Finance Incident&lt;br /&gt;
!Date&lt;br /&gt;
!Event&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
|August 13th, 2020 12:00:00 AM&lt;br /&gt;
|First Event&lt;br /&gt;
|This is an expanded description of what happened and the impact. If multiple lines are necessary, add them here.&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Total Amount Lost ==&lt;br /&gt;
The total amount lost is unknown.&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;
It is unknown how much was recovered.&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;
&lt;br /&gt;
== Prevention Policies ==&lt;br /&gt;
The safest storage of assets is an offline multi-signature wallet. Storing funds in a smart contract is very similar to a hot wallet and should be avoided.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
[https://cointelegraph.com/news/yam-suffers-technical-outage-following-scam-accusations Yam Suffers Technical Outage Following Scam Accusations] (Aug 11)&lt;br /&gt;
&lt;br /&gt;
[https://news.bitcoin.com/new-defi-yield-farming-project-yam-finance-sees-460-million-locked-in-17-hours/ Defi Project Yam Finance Sees Over $500M Locked in 24 Hours, Devs Reveal Contract Bug | Bitcoin News] (Aug 11)&lt;br /&gt;
&lt;br /&gt;
[https://cointelegraph.com/news/how-one-line-of-code-destroyed-yam-defi How One Line of Code Destroyed Yam DeFi] (Aug 12)&lt;br /&gt;
&lt;br /&gt;
[https://cointelegraph.com/news/rebase-bug-permanently-breaks-yam-governance Rebase Bug Permanently Breaks Yam Governance] (Aug 12)&lt;br /&gt;
&lt;br /&gt;
[https://medium.com/@bitrou_defi/the-impact-of-the-yam-projects-lightning-incident-3339c1208123 The impact of the Yam project’s lightning incident] (Aug 12)&lt;br /&gt;
&lt;br /&gt;
[https://news.bitcoin.com/defi-yam-token-market-plummets-near-zero-founder-failed/ Defi Implosion: YAM Token Market Cap Plummets to Near Zero as Founder Claims He 'Failed' | Bitcoin News] (Aug 12)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1294332510500016130 @YamFinance - Twitter] (Aug 13)&lt;br /&gt;
&lt;br /&gt;
[https://www.youtube.com/watch?v=DXUhD8m_KMc Meteoric Rise And Fall Of YAM Explained - Ethereum, DEFI - YouTube] (Aug 13)&lt;br /&gt;
&lt;br /&gt;
[https://coingeek.com/defi-strikes-again-yam-protocol-bug-leads-to-750000-loss/ DeFi strikes again: YAM protocol bug leads to $750,000 loss - CoinGeek] (Aug 13)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1295145183227654144 @YamFinance - Twitter] (Aug 15)&lt;br /&gt;
&lt;br /&gt;
[https://etherscan.io/tx/0xf1dcb609401efd8e6ed4e74908f9fb301d4a052656f98736ec7cab0f30ed6787 Ethereum Transaction Hash (Txhash) Details | Etherscan] (Aug 17)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1296129003405938693 @YamFinance - Twitter] (Aug 18)&lt;br /&gt;
&lt;br /&gt;
[https://cointelegraph.com/news/investors-tip-400m-into-failed-defi-yam-project-hoping-for-a-sequel Investors Tip $400M Into Failed DeFi ‘Yam’ Project Hoping for a Sequel] (Aug 18)&lt;br /&gt;
&lt;br /&gt;
[https://github.com/yam-finance/yam-migration/blob/master/PeckShield-Audit-Report-YAMv2-v1.0.pdf yam-migration/PeckShield-Audit-Report-YAMv2-v1.0.pdf at master · yam-finance/yam-migration · GitHub] (Aug 18)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1297210568777109504 @YamFinance - Twitter] (Aug 21)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1307053167193010176 @YamFinance - Twitter] (Sep 17)&lt;br /&gt;
&lt;br /&gt;
[https://www.fxstreet.com/cryptocurrencies/news/yam-finance-announces-migration-to-v3-in-hopes-to-revive-the-project-202009180806 Yam Finance announces migration to V3 in hopes to revive the project] (Sep 17)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1307806818568212482 @YamFinance - Twitter] (Sep 19)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1307806817595072512 @YamFinance - Twitter] (Sep 19)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1307806816613654528 @YamFinance - Twitter] (Sep 19)&lt;br /&gt;
&lt;br /&gt;
[https://cryptopotato.com/yam-finance-replants-and-rebases-but-tokens-still-slide/ Yam Finance Replants and Rebases But Tokens Still Slide] (Sep 21)&lt;br /&gt;
&lt;br /&gt;
[https://anchor.fm/camila-russo/episodes/It-Was-Exciting-But-it-Was-Also-Terrifying-Dan-Elitzer-and-Clinton-Bembry-on-Yam-Finances-Backstory-ek7540 &amp;quot;It Was Exciting But it Was Also Terrifying:&amp;quot; Dan Elitzer and Clinton Bembry on Yam Finance's Backstory by The Defiant  • A podcast on Anchor] (Sep 25)&lt;br /&gt;
&lt;br /&gt;
[https://yam.finance/ YAM Finance] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://blockcast.cc/news/chengdu-lianan-in-august-there-were-5-security-incidents-in-the-defi-field-and-a-total-of-39-incidents-in-the-blockchain-field/ Chengdu Lianan: In August, there were 5 security incidents in the DeFi field, and a total of 39 incidents in the blockchain field • Blockcast.cc- News on Blockchain, DLT, Cryptocurrency] (Jun 12)&lt;br /&gt;
&lt;br /&gt;
[https://cryptobriefing.com/50-million-lost-the-top-19-defi-cryptocurrency-hacks-2020/ Millions Lost: The Top 19 DeFi Cryptocurrency Hacks of 2020 | Crypto Briefing] (May 21)&lt;br /&gt;
&lt;br /&gt;
[https://cryptobriefing.com/no-audits-no-problem-defi-stablecoin-yam-attracts-over-100-million/ No Audits, No Problem: DeFi Stablecoin YAM Attracts Over $100 Million | Crypto Briefing] (Jun 26)&lt;br /&gt;
&lt;br /&gt;
[https://cryptobriefing.com/what-ampleforth-how-ampl-redefining-decentralized-money/ What Is Ampleforth? How AMPL Is Redefining Decentralized Money | Crypto Briefing] (Jun 26)&lt;br /&gt;
&lt;br /&gt;
[https://cryptobriefing.com/yam-finance-defi-experiment-comes-to-a-grinding-halt/ The Yam Finance DeFi Experiment Comes to a Grinding Halt | Crypto Briefing] (Jun 26)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293336418983579649 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293389937371418624 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293608262252875778 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293669286536523778 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293720210474545152 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293720662150799360 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293704924015071234 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293729910121467904 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293739908721446912 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293755728163995648 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293770311221956608 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293783734693564416 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293790396666056705 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293811276062380033 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293814954164981760 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1293842435924082689 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1294122110223147013 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1294316417144233991 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1294339895637364736 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1295749281765306369 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1295798079816437761 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1296141830816509953 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1296898679589220354 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/YamFinance/status/1297947962430107648 @YamFinance Twitter] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://medium.com/yam-finance/save-yam-245598d81cec Save Yam] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://medium.com/yam-finance/yam-post-rescue-attempt-update-c9c90c05953f Yam Post Rescue Attempt Update] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://medium.com/yam-finance/yam-migration-faq-57c705688fe6 Yam Migration Faq] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://medium.com/yam-finance/yam-migration-live-955c63766ab8 Yam Migration Live] (Jul 10)&lt;br /&gt;
&lt;br /&gt;
[https://hacked.slowmist.io/en/?c=ETH%20DApp SlowMist Hacked - SlowMist Zone] (May 17)&lt;br /&gt;
&lt;br /&gt;
[https://www.certik.org/blog/blockchain-hacks-2020-15-billion-lost-how-can-we-mitigate-hacks-in-2021 Blockchain Hacks: 2020 | $15 billion lost, how can we mitigate hacks in 2021? | CertiK Foundation Blog] (Jul 22)&lt;br /&gt;
&lt;br /&gt;
[https://mobile.twitter.com/certik_io/status/1293999091245035521 https://mobile.twitter.com/certik_io/status/1293999091245035521] (Jan 10)&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/amanusk_/status/1293816698592780289 @amanusk_ Twitter] (Jul 24)&lt;/div&gt;</summary>
		<author><name>Azoundria</name></author>
	</entry>
</feed>