DelicacyDefi Rug Pull - Revision history

Azoundria at 23:49, 2 May 2023

2023-05-02T23:49:06Z

← Older revision		Revision as of 17:49, 2 May 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/delicacydefirugpull.php}}		{{Imported Case Study 2\|source=https://www.quadrigainitiative.com/casestudy/delicacydefirugpull.php}}
	{{Unattributed Sources}}		{{Unattributed Sources}}

	[[File:Binancesecurity.jpg\|thumb\|DelicacyDefi]]The anonymous developers behind DelicacyDefi launched a new smart contract hot wallet, complete with an innovative new backdoor. Despite lacking an audit, it appears many added liquidity here. It appears that liquidity was withdrawn on April 27th. The website and social media appear to have been deleted.		[[File:Binancesecurity.jpg\|thumb\|DelicacyDefi]]The anonymous developers behind DelicacyDefi launched a new smart contract hot wallet, complete with an innovative new backdoor. Despite lacking an audit, it appears many added liquidity here. It appears that liquidity was withdrawn on April 27th. The website and social media appear to have been deleted.

	This is a global/international case not involving a specific country.		This is a global/international case not involving a specific country.<ref name="certikorgtwitter-5556" /><ref name="rugdoc-5557" /><ref name="bscscan-5558" /><ref name="bscscan-5559" /><ref name="bscscan-5560" /><ref name="delicacydefiarchive-5561" /><ref name="delicacydefiarchive-5562" /><ref name="bitqueryexplorer-5563" /><ref name="bscscan-5564" /><ref name="reddit-5565" /><ref name="delicacydefimediumarchive-5566" /><ref name="bscxplorer-5567" /><ref name="websitebiography-5568" /><ref name="rugdocchattelegram-5569" /><ref name="rugdocchattelegram-5570" /><ref name="bscscan-5571" /><ref name="bscscan-5572" />
	<ref name="certikorgtwitter-5556" /><ref name="rugdoc-5557" /><ref name="bscscan-5558" /><ref name="bscscan-5559" /><ref name="bscscan-5560" /><ref name="delicacydefiarchive-5561" /><ref name="delicacydefiarchive-5562" /><ref name="bitqueryexplorer-5563" /><ref name="bscscan-5564" /><ref name="reddit-5565" /><ref name="delicacydefimediumarchive-5566" /><ref name="bscxplorer-5567" /><ref name="websitebiography-5568" /><ref name="rugdocchattelegram-5569" /><ref name="rugdocchattelegram-5570" /><ref name="bscscan-5571" /><ref name="bscscan-5572" />

	== About DelicacyDefi ==		== About DelicacyDefi ==
Line 71:		Line 70:
	!Description		!Description
	\|-		\|-
	\|April 27th, 2021 2:39:32 AM		\|April 27th, 2021 2:39:32 AM MDT
	\|Main Event		\|Main Event
	\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
Line 79:		Line 78:
	\|		\|
	\|}		\|}

			== Technical Details ==
			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?

	== Total Amount Lost ==		== Total Amount Lost ==
Line 98:		Line 100:
	== Ongoing Developments ==		== Ongoing Developments ==
	What parts of this case are still remaining to be concluded?		What parts of this case are still remaining to be concluded?
			== General Prevention Policies ==
			Funds stored in smart contract hot wallets face many risks, especially when the wallet is controlled by an anonymous developer. For proper protection, uninsured funds should be stored in a multi-sig wallet with all keys stored offline and held by known and trained individuals. At least two seprate reviews of this setup should be conducted.
			== 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 ~~Policies ==~~		{{Prevention:Regulators:End}}
	Funds stored in smart contract hot wallets face many risks, especially when the wallet is controlled by an anonymous developer. For proper protection, uninsured funds should be stored in a multi-sig wallet with all keys stored offline and held by known and trained individuals. At least two seprate reviews of this setup should be conducted.

	== References ==		== References ==

Azoundria at 17:31, 22 February 2023

2023-02-22T17:31:12Z

Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/delicacydefirugpull.php}} DelicacyDefiThe anonymous developers behind DelicacyDefi launched a new smart contract hot wallet, complete with an innovative new backdoor. Despite lacking an audit, it appears many added liquidity here. It appears that liquidity was withdrawn on April 27th. The website and social media appear to have been deleted. This is a global/int..."

2023-01-26T05:44:12Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/delicacydefirugpull.php}} thumb|DelicacyDefiThe anonymous developers behind DelicacyDefi launched a new smart contract hot wallet, complete with an innovative new backdoor. Despite lacking an audit, it appears many added liquidity here. It appears that liquidity was withdrawn on April 27th. The website and social media appear to have been deleted. This is a global/int..."

New page

{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/delicacydefirugpull.php}}

[[File:Binancesecurity.jpg|thumb|DelicacyDefi]]The anonymous developers behind DelicacyDefi launched a new smart contract hot wallet, complete with an innovative new backdoor. Despite lacking an audit, it appears many added liquidity here. It appears that liquidity was withdrawn on April 27th. The website and social media appear to have been deleted.

This is a global/international case not involving a specific country.

== About DelicacyDefi ==
The domain was registered on March 18th, 2021. "Let's goooooo! Come and taste our succulent pools and enjoy the juicy APR's. 1000 Tokens minted. 900 will be burned after 36 hours. Base project for many to come! No migrator code, timelock implemented and audit on the way!"

"We are very, very proud to present you with our upcoming project on BSC: Delicacy Defi! This will not be just another Pancakeswap clone or some random pump-and-dump-coin as we have big plans for the future."

"Our first project will be the DELI token. This will serve as our baseline, but we have already begun development on our next projects that will build further upon The DELI platform. We can’t give away too much at this time but it involves NFT’s, Borrowing and lending on a P2P scale and a very interesting automated, self-sustaining mechanism for applying deflationary pressure on our DELI token."

"The Technicals: Small marketcap: 1000 DELI tokens Have been issued. 100 of these will be used to provide liquidity when the farm will be lau[n]ched. The 900 remaining tokens will be locked in the farm for the duration of the timelock. Afterwards they are going to be burned."

"No Presale: Instead of doing a presale, We are going to incentivize everybody to provide liquidity for our token by rewarding them handsomely. For the first 36 hours (duration of timelock) the DELI/BNB pool is going to be the best rewarding pool. Once liquidity and price stability has been achieved, rewards will be balanced again."

"Security: Our contracts are forked over from Goose, so no migrator code! We also will be having a 36 hour timelock contract set in place. Audit is also being looked into. Fees: All pools except for the native pairs will have a fee of 4%. 1% is going to the team and the remaining 3% is going to be used for regular buybacks & burns. To help get the farms going we are going to discount all fees to 1%! Timing: We are launching very soon. Specific details and last minute updates will always be shared in our Telegram group, so be sure to join us over there!"

"So, let’s work up an appetite, prepare our tummy’s and be ready to taste those exquisite delicacies [and] juicy APR’s!"

"Looks like a rug- lpToken.Update(address(_owner))"

"We’ve received inbounds that may indicate high risks regarding a project named DelicacyDefi. Malicious code snippets appear in the smart contract and we wish the community DYOR with caution before interacting. @BinanceChain"

"The owner of the contract has the ability to approve (unlimited) the spending of the LP tokens deposited by users. It means at a certain stage (say after the farm started), the owner can call this function first to approve the spending, then another call to the LP token's transferFrom() to exploit the deposited LP tokens into its own pocket."

"It replaces the safeApprove() of the standard SafeBEP20 to Update() for the sake of misleading (approval for someone for doing something is always dangerous, isn't it!)." "Owner of DeliMaster can take away all the LPs."

"Be careful potential #RugPull. Check out warning by @certikorg related to #delicacydefi project."

"Update is to update all the pools! And yes we messed around a lot with the code. [A]s we s[t]ated in the [M]edium post we are looking to implement new functions like automatic block reward and peer to peer LP transfer. This is a little piece of code we left in, even by accident."

"This time we do it right. ALL new contract will be posted and published days before launch, allowing everybody to go over them as much as they want! No more FUD, no more mess. Clarity and security becoime our number 1 priorities!" "Again, thanks to everybody who is still believing in us. We will keep working hard to bring you a true decentralized gem!"

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.
{| class="wikitable"
|+Key Event Timeline - DelicacyDefi Rug Pull
!Date
!Event
!Description
|-
|April 27th, 2021 2:39:32 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 ==
Funds stored in smart contract hot wallets face many risks, especially when the wallet is controlled by an anonymous developer. For proper protection, uninsured funds should be stored in a multi-sig wallet with all keys stored offline and held by known and trained individuals. At least two seprate reviews of this setup should be conducted.

== References ==
[https://mobile.twitter.com/certikorg/status/1373445038936559618 https://mobile.twitter.com/certikorg/status/1373445038936559618] (Jan 10)

[https://rugdoc.io/project/delicacydefi/ Delicacydefi – RugDoc] (Jan 12)

[https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#code https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#code] (Jan 12)

[https://bscscan.com/tx/0x25b632883c6ff01ada13b9de84af6c2fc9d58794419f0b8cb6e6dd2d689deb0b https://bscscan.com/tx/0x25b632883c6ff01ada13b9de84af6c2fc9d58794419f0b8cb6e6dd2d689deb0b] (Jan 12)

[https://bscscan.com/tx/0x7b43387776b2a0df25829f57733dc8fd9504598a6b98b80feda22a792efb2e13 https://bscscan.com/tx/0x7b43387776b2a0df25829f57733dc8fd9504598a6b98b80feda22a792efb2e13] (Jan 12)

[https://web.archive.org/web/20210319214932/https://delicacydefi.com/ Delicacy DeFi] (Jan 12)

[https://web.archive.org/web/20210320095002/https://delicacydefi.com/ Delicacy DeFi] (Jan 12)

[https://explorer.bitquery.io/bsc/token/0x66b32cee882d82a897a1f6102a18da5af6f01f6f delicacydefi.com (DELI) ERC20 Token Analytics | Binance Smart Chain Mainnet | Bitquery] (Jan 12)

[https://bscscan.com/token/0x66b32cee882d82a897a1f6102a18da5af6f01f6f?a=0xbb55e2546a501926e3cf55a570a9a3f4d43f6717 https://bscscan.com/token/0x66b32cee882d82a897a1f6102a18da5af6f01f6f?a=0xbb55e2546a501926e3cf55a570a9a3f4d43f6717] (Jan 12)

[https://www.reddit.com/r/Yield_Farming/comments/m6fpt9/launching_soon_no_presale_delicacy_defi/ �Launching soon! No presale! Delicacy Defi � : Yield_Farming] (Jan 12)

[https://web.archive.org/web/20210321170255/https://delicacydefi.medium.com/introducing-delicacy-defi-70d8c1b133ca Introducing Delicacy Defi] (Jan 12)

[https://bscxplorer.com/address/0xB5caCF6043C0E090E60052c5b85915d3FeF581C3 Binance Smart Chain Address Info: 0xB5caCF6043C0E090E60052c5b85915d3FeF581C3] (Jan 12)

[https://websitebiography.com/new_domain_registrations/2021-03-18/36 New Domain Registrations On 18th March 2021 | Page 36] (Jan 12)

[https://t.me/RugDocChat/15804/ Telegram: Contact @RugDocChat] (Jan 12)

[https://t.me/RugDocChat/15184/ Telegram: Contact @RugDocChat] (Jan 12)

[https://bscscan.com/token/0x57da991f138bdf9ecfbb4c710ec57706c7646c57 https://bscscan.com/token/0x57da991f138bdf9ecfbb4c710ec57706c7646c57] (Jan 12)

[https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#tokentxns https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#tokentxns] (Jan 12)

← Older revision		Revision as of 11:31, 22 February 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/delicacydefirugpull.php}}		{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/delicacydefirugpull.php}}
			{{Unattributed Sources}}

	[[File:Binancesecurity.jpg\|thumb\|DelicacyDefi]]The anonymous developers behind DelicacyDefi launched a new smart contract hot wallet, complete with an innovative new backdoor. Despite lacking an audit, it appears many added liquidity here. It appears that liquidity was withdrawn on April 27th. The website and social media appear to have been deleted.		[[File:Binancesecurity.jpg\|thumb\|DelicacyDefi]]The anonymous developers behind DelicacyDefi launched a new smart contract hot wallet, complete with an innovative new backdoor. Despite lacking an audit, it appears many added liquidity here. It appears that liquidity was withdrawn on April 27th. The website and social media appear to have been deleted.

	This is a global/international case not involving a specific country.		This is a global/international case not involving a specific country.
			<ref name="certikorgtwitter-5556" /><ref name="rugdoc-5557" /><ref name="bscscan-5558" /><ref name="bscscan-5559" /><ref name="bscscan-5560" /><ref name="delicacydefiarchive-5561" /><ref name="delicacydefiarchive-5562" /><ref name="bitqueryexplorer-5563" /><ref name="bscscan-5564" /><ref name="reddit-5565" /><ref name="delicacydefimediumarchive-5566" /><ref name="bscxplorer-5567" /><ref name="websitebiography-5568" /><ref name="rugdocchattelegram-5569" /><ref name="rugdocchattelegram-5570" /><ref name="bscscan-5571" /><ref name="bscscan-5572" />

	== About DelicacyDefi ==		== About DelicacyDefi ==
Line 49:		Line 51:

	Don't Include:		Don't Include:

	* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.		* 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.		* Anything that wasn't reasonably knowable at the time of the event.
Line 71:		Line 72:
	\|-		\|-
	\|April 27th, 2021 2:39:32 AM		\|April 27th, 2021 2:39:32 AM
	\|~~First~~ Event		\|Main Event
	\|~~This is an expanded~~ description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
	\|-
	\|
	\|
	\|
	\|-		\|-
	\|		\|
Line 95:		Line 92:

	== Total Amount Recovered ==		== Total Amount Recovered ==
	~~It is unknown how much was~~ 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?		What funds were recovered? What funds were reimbursed for those affected users?
Line 106:		Line 103:

	== References ==		== References ==
	[https://mobile.twitter.com/certikorg/status/1373445038936559618 https://mobile.twitter.com/certikorg/status/1373445038936559618] (Jan 10)		<references><ref name="certikorgtwitter-5556">[https://mobile.twitter.com/certikorg/status/1373445038936559618 https://mobile.twitter.com/certikorg/status/1373445038936559618] (Jan 10, 2022)</ref>

	[https://rugdoc.io/project/delicacydefi/ Delicacydefi – RugDoc] (Jan 12)		<ref name="rugdoc-5557">[https://rugdoc.io/project/delicacydefi/ Delicacydefi – RugDoc] (Jan 12, 2022)</ref>

	[https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#code https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#code] (Jan 12)		<ref name="bscscan-5558">[https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#code https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#code] (Jan 12, 2022)</ref>

	[https://bscscan.com/tx/0x25b632883c6ff01ada13b9de84af6c2fc9d58794419f0b8cb6e6dd2d689deb0b https://bscscan.com/tx/0x25b632883c6ff01ada13b9de84af6c2fc9d58794419f0b8cb6e6dd2d689deb0b] (Jan 12)		<ref name="bscscan-5559">[https://bscscan.com/tx/0x25b632883c6ff01ada13b9de84af6c2fc9d58794419f0b8cb6e6dd2d689deb0b https://bscscan.com/tx/0x25b632883c6ff01ada13b9de84af6c2fc9d58794419f0b8cb6e6dd2d689deb0b] (Jan 12, 2022)</ref>

	[https://bscscan.com/tx/0x7b43387776b2a0df25829f57733dc8fd9504598a6b98b80feda22a792efb2e13 https://bscscan.com/tx/0x7b43387776b2a0df25829f57733dc8fd9504598a6b98b80feda22a792efb2e13] (Jan 12)		<ref name="bscscan-5560">[https://bscscan.com/tx/0x7b43387776b2a0df25829f57733dc8fd9504598a6b98b80feda22a792efb2e13 https://bscscan.com/tx/0x7b43387776b2a0df25829f57733dc8fd9504598a6b98b80feda22a792efb2e13] (Jan 12, 2022)</ref>

	[https://web.archive.org/web/20210319214932/https://delicacydefi.com/ Delicacy DeFi] (Jan 12)		<ref name="delicacydefiarchive-5561">[https://web.archive.org/web/20210319214932/https://delicacydefi.com/ Delicacy DeFi] (Jan 12, 2022)</ref>

	[https://web.archive.org/web/20210320095002/https://delicacydefi.com/ Delicacy DeFi] (Jan 12)		<ref name="delicacydefiarchive-5562">[https://web.archive.org/web/20210320095002/https://delicacydefi.com/ Delicacy DeFi] (Jan 12, 2022)</ref>

	[https://explorer.bitquery.io/bsc/token/0x66b32cee882d82a897a1f6102a18da5af6f01f6f delicacydefi.com (DELI) ERC20 Token Analytics \| Binance Smart Chain Mainnet \| Bitquery] (Jan 12)		<ref name="bitqueryexplorer-5563">[https://explorer.bitquery.io/bsc/token/0x66b32cee882d82a897a1f6102a18da5af6f01f6f delicacydefi.com (DELI) ERC20 Token Analytics \| Binance Smart Chain Mainnet \| Bitquery] (Jan 12, 2022)</ref>

	[https://bscscan.com/token/0x66b32cee882d82a897a1f6102a18da5af6f01f6f?a=0xbb55e2546a501926e3cf55a570a9a3f4d43f6717 https://bscscan.com/token/0x66b32cee882d82a897a1f6102a18da5af6f01f6f?a=0xbb55e2546a501926e3cf55a570a9a3f4d43f6717] (Jan 12)		<ref name="bscscan-5564">[https://bscscan.com/token/0x66b32cee882d82a897a1f6102a18da5af6f01f6f?a=0xbb55e2546a501926e3cf55a570a9a3f4d43f6717 https://bscscan.com/token/0x66b32cee882d82a897a1f6102a18da5af6f01f6f?a=0xbb55e2546a501926e3cf55a570a9a3f4d43f6717] (Jan 12, 2022)</ref>

	[https://www.reddit.com/r/Yield_Farming/comments/m6fpt9/launching_soon_no_presale_delicacy_defi/ ~~�Launching~~ soon! No presale! Delicacy Defi � : Yield_Farming] (Jan 12)		<ref name="reddit-5565">[https://www.reddit.com/r/Yield_Farming/comments/m6fpt9/launching_soon_no_presale_delicacy_defi/ Launching soon! No presale! Delicacy Defi : Yield_Farming] (Jan 12, 2022)</ref>

	[https://web.archive.org/web/20210321170255/https://delicacydefi.medium.com/introducing-delicacy-defi-70d8c1b133ca Introducing Delicacy Defi] (Jan 12)		<ref name="delicacydefimediumarchive-5566">[https://web.archive.org/web/20210321170255/https://delicacydefi.medium.com/introducing-delicacy-defi-70d8c1b133ca Introducing Delicacy Defi] (Jan 12, 2022)</ref>

	[https://bscxplorer.com/address/0xB5caCF6043C0E090E60052c5b85915d3FeF581C3 Binance Smart Chain Address Info: 0xB5caCF6043C0E090E60052c5b85915d3FeF581C3] (Jan 12)		<ref name="bscxplorer-5567">[https://bscxplorer.com/address/0xB5caCF6043C0E090E60052c5b85915d3FeF581C3 Binance Smart Chain Address Info: 0xB5caCF6043C0E090E60052c5b85915d3FeF581C3] (Jan 12, 2022)</ref>

	[https://websitebiography.com/new_domain_registrations/2021-03-18/36 New Domain Registrations On 18th March 2021 \| Page 36] (Jan 12)		<ref name="websitebiography-5568">[https://websitebiography.com/new_domain_registrations/2021-03-18/36 New Domain Registrations On 18th March 2021 \| Page 36] (Jan 12, 2022)</ref>

	[https://t.me/RugDocChat/15804/ Telegram: Contact @RugDocChat] (Jan 12)		<ref name="rugdocchattelegram-5569">[https://t.me/RugDocChat/15804/ Telegram: Contact @RugDocChat] (Jan 12, 2022)</ref>

	[https://t.me/RugDocChat/15184/ Telegram: Contact @RugDocChat] (Jan 12)		<ref name="rugdocchattelegram-5570">[https://t.me/RugDocChat/15184/ Telegram: Contact @RugDocChat] (Jan 12, 2022)</ref>

	[https://bscscan.com/token/0x57da991f138bdf9ecfbb4c710ec57706c7646c57 https://bscscan.com/token/0x57da991f138bdf9ecfbb4c710ec57706c7646c57] (Jan 12)		<ref name="bscscan-5571">[https://bscscan.com/token/0x57da991f138bdf9ecfbb4c710ec57706c7646c57 https://bscscan.com/token/0x57da991f138bdf9ecfbb4c710ec57706c7646c57] (Jan 12, 2022)</ref>

	[https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#tokentxns https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#tokentxns] (Jan 12)		<ref name="bscscan-5572">[https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#tokentxns https://bscscan.com/address/0xfb19cef55cfbb082489a4a79a484353198fec099#tokentxns] (Jan 12, 2022)</ref></references>