This site is reader-supported. When you click through links on our site, we may be compensated.
<div class="featured_image_container"> </div> <strong>On March 19, the Financial Action Task Force (FATF) published draft guidance on the risk-based approach to virtual assets. The newly updated guidance now applies anti-money laundering and know-your-customer rules to stablecoins, decentralized finance (defi), and non-fungible token (NFT) assets.</strong>
FATF Defines Decentralized Exchanges and Defi as a Virtual Asset Service Providers
For a while now, cryptocurrency proponents have said that one day, global regulators would likely target decentralized finance (defi) and the latest non-fungible token (NFT) hype. For a while now, the Financial Action Task Force (FATF) has been trying to come up with a regulatory standard for cryptocurrencies businesses called a “virtual asset service provider” (VASP). Things like the FATF’s Travel Rule have always been controversial, but regulators from a number of countries have been adopting the organization’s guidance. Recently Gibraltar updated its guidance notes to align with the FATF rules and South Africa has been attempting the same.
The FATF’s latest guidance is merely an update of some of its past recommendations toward virtual assets (VA) and VASPs. However, the updated version now discusses stablecoins, defi, and NFTs, as things like decentralized exchanges (dex) are considered VASPs. The newly revised guidance suggests imposing anti-money laundering and know-your-customer (AML/KYC) rules toward dex applications. The FATF calls these platforms “Decentralized or distributed applications (dapp) or a platform that offers “exchange or transfer services.”
“A dapp, for example, is a term that refers to a software program that operates on a P2P network of computers running a blockchain protocol— a type of distributed public ledger that allows the development of other applications,” the latest guidelines note. “These applications or platforms are often run on a distributed ledger but still usually have a central party with some measure of involvement, such as creating and launching an asset, setting parameters, holding an administrative ‘key’ or collecting fees.”
The global regulator’s guidance adds:
Dapps can facilitate or conduct the exchange or transfer of [virtual assets].
‘The FATF Is No Stranger to Defi, Dex, and NFTs’
FATF’s latest guidance essentially defines a non-fungible token (NFT) as a VA as it defines a stablecoin. The latest guidance on NFT, defi, and stablecoins indicate that the FATF has noticed these emerging trends within the crypto space. Additionally, the FATF tweeted about the guidance and asked for commentary about the 99-page report. “The FATF wants to hear your views on draft guidance for taking a risk-based approach to virtual assets and virtual asset service providers,” the organization tweeted. “Relevant private sector stakeholders can take part in the public consultation.”
The report also touched upon VA transfers to and from unhosted wallets. “The FATF recognizes that unlike traditional fiat wire transfers, not every VA transfer may involve (or be book-ended by) two obliged entities,” the FATF guidance says. In instances in which a VA transfer involves only one obliged entity on either end of the transfer (e.g., when an ordering VASP or other obliged entity sends VAs on behalf of its customer, the originator, to a beneficiary that is not a customer of a beneficiary institution but rather an individual VA user who receives the VA transfer.”
Of course, the conversation about the FATF’s new definitions for defi, NFTs, stablecoins, dapps, and dex applications was a topical discussion on social media. “FATF ain’t no stranger to defi, dex & NFT,” Björn Godenrath tweeted. “Classification as a virtual asset service provider brings market participants into the scope of traditional money laundering regulations (if they can be identified),” he added.
What do you think about the FATF guidelines and definitions tied to defi and NFTs? Let us know what you think about this subject in the comments section below.
<div class="article__body__tags-related"> <div class="article__body__tags-related__tags"> <h6 class="article__body__tags-related__title"> Tags in this story </h6> <div class="article__body__tags"> <a href="https://news.bitcoin.com/tag/the-big-bitcoin-heist/">"The Big Bitcoin Heist"</a>, <a href="https://news.bitcoin.com/tag/99-page-report/">99-page report</a>, <a href="https://news.bitcoin.com/tag/aml/">AML</a>, <a href="https://news.bitcoin.com/tag/bitcoin/">Bitcoin</a>, <a href="https://news.bitcoin.com/tag/bjorn-godenrath/">Björn Godenrath</a>, <a href="https://news.bitcoin.com/tag/decentralized-exchange/">decentralized exchange</a>, <a href="https://news.bitcoin.com/tag/defi/">DeFi</a>, <a href="https://news.bitcoin.com/tag/dex/">DEX</a>, <a href="https://news.bitcoin.com/tag/fatf/">fatf</a>, <a href="https://news.bitcoin.com/tag/fatf-guidance/">FATF guidance</a>, <a href="https://news.bitcoin.com/tag/financial-action-task-force/">Financial Action Task Force</a>, <a href="https://news.bitcoin.com/tag/kyc/">KYC</a>, <a href="https://news.bitcoin.com/tag/nft/">nft</a>, <a href="https://news.bitcoin.com/tag/regulation/">Regulation</a>, <a href="https://news.bitcoin.com/tag/regulatory-standards/">Regulatory standards</a>, <a href="https://news.bitcoin.com/tag/the-fatf/">The FATF</a>, <a href="https://news.bitcoin.com/tag/va/">VA</a>, <a href="https://news.bitcoin.com/tag/vasp/">vasp</a>, <a href="https://news.bitcoin.com/tag/vasps/">VASPs</a> </div> </div> </div> <p class="images_credits"><em><b>Image Credits</b>: Shutterstock, Pixabay, Wiki Commons</em></p> <div class="disclaimer" readability="18.596525096525"><strong>Disclaimer</strong>: This article is for informational purposes only. It is not a direct offer or solicitation of an offer to buy or sell, or a recommendation or endorsement of any products, services, or companies. <a href="https://bitcoin.com">Bitcoin.com</a> does not provide investment, tax, legal, or accounting advice. Neither the company nor the author is responsible, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with the use of or reliance on any content, goods or services mentioned in this article.