bodyType

customContents

entityId

printArticlePageQuery

filter

article

body

urlAlias

articleSectionsContent

articleSeoArticle

articleSourceHeaderArticle

contentSchemaRenderContent

contentSubHeadlineContent

contentHeadlineContent

mainImagePrintArticleArticle

authorBlockPrintArticleArticle

contentSponsorTagContent

articlePianoPaywallContent

scmpYoutubeContent

hooksTrackPageViewArticle

query printArticlePageQuery(
  $entityId: String!
  $customContents: [CustomContentInput]
  $bodyType: BodyFormatTypeEnum
) {
  article(filter: {entityId: $entityId}) {
    entityId
    body(customContents: $customContents, type: $bodyType) {
      json
    }
    urlAlias
    ...articleSectionsContent
    ...articleSeoArticle_3o8td4
    ...articleSourceHeaderArticle
    ...contentSchemaRenderContent
    ...contentSubHeadlineContent
    ...contentHeadlineContent
    ...mainImagePrintArticleArticle
    ...authorBlockPrintArticleArticle
    ...contentSponsorTagContent
    ...articlePianoPaywallContent
    ...scmpYoutubeContent
    ...hooksTrackPageViewArticle
    id
  }
}

fragment articlePianoPaywallContent on Content {
  __isContent: __typename
  ...hooksPaywallPromiseContent
}

fragment articleSectionsContent on Content {
  __isContent: __typename
  sections {
    value {
      ...helpersCheckIfNewsSectionInFirstIndexSection
      ...entityLink
      name
      id
    }
  }
}

fragment articleSeoArticle_3o8td4 on Article {
  ...hooksArticleSeoArticle
  ...helpersCheckIsPostiesArticle
  ...helpersGetArticleTypeArticle
  entityId
  publishedDate
  updatedDate
  summary {
    text
  }
  subHeadline {
    text
  }
  body(customContents: $customContents, type: $bodyType) {
    text
  }
  keywords
  sections {
    value {
      name
      id
    }
  }
  topics {
    name
    entityId
    id
  }
  urlAlias
  authors {
    name
    id
  }
  images {
    style(filter: {style: "768x768"}) {
      url
    }
  }
  readingTime
}

fragment articleSourceHeaderArticle on Article {
  urlAlias
  ...entityLink
}

fragment authorBlockPrintArticleArticle on Article {
  ...defaultArticleDateContent
  ...authorNamesArticle
}

fragment authorNameAuthor on Author {
  ...entityLink
  name
  entityUuid
}

fragment authorNamesArticle on Article {
  authorLocations
  authors {
    entityId
    location
    ...authorNameAuthor
    id
  }
}

fragment blockquoteQuoteContent on Content {
  __isContent: __typename
  ...contentShareWidgetContent
}

fragment checkersCheckContentContainsStarlingImageContent on Content {
  __isContent: __typename
  topics {
    entityId
    id
  }
}

fragment contentHeadlineContent on Content {
  __isContent: __typename
  headline
  socialHeadline
  ...contentHeadlineTagContent
  ...helpersUseContentSponsorContent
}

fragment contentHeadlineTagContent on Content {
  __isContent: __typename
  ...hooksContentHeadlineTagContent
}

fragment contentNewsletterWidgetContent on Content {
  __isContent: __typename
  topics {
    relatedNewsletters {
      ...helpersMassageToNewsletterItemNewsletter
      id
    }
    id
  }
  sections {
    value {
      relatedNewsletters {
        ...helpersMassageToNewsletterItemNewsletter
        id
      }
      id
    }
  }
  ... on Article {
    relatedNewsletters {
      ...helpersMassageToNewsletterItemNewsletter
      id
    }
  }
}

fragment contentSchemaRenderContent on Content {
  __isContent: __typename
  ...blockquoteQuoteContent
  ...imageContent
  ...inlineWidgetContent
  ...photoGalleryWidgetContent
  ...scmpYoutubeContent
}

fragment contentShareWidgetContent on Content {
  __isContent: __typename
  entityId
  urlAlias
  shortUrl
  socialHeadline
  headline
}

fragment contentSponsorTagContent on Content {
  __isContent: __typename
  ...helpersUseContentSponsorContent
}

fragment contentSubHeadlineContent on Content {
  __isContent: __typename
  subHeadline {
    json
  }
  summary {
    json
  }
  ...contentSchemaRenderContent
}

fragment defaultArticleDateContent on Content {
  __isContent: __typename
  ...hooksArticleDateUtilsContent
}

fragment entityLink on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  __typename
  entityId
  entityUuid
  urlAlias
  urlRedirect {
    toUrl
    id
  }
  application {
    entityId
    id
  }
  ... on Section {
    fullSectionPath {
      entityId
      id
    }
    parentSection
  }
  ...helpersAppBarVariantBase
  ...helpersApplicationBase
  ...helpersCheckIsPlusArticle
  ...helpersStyleSectionContent
}

fragment helpersAppBarVariantBase on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  ...helpersCheckIsLiveArticle
  ...helpersCheckIsPlusPage
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostiesPage
  ...helpersCheckIsPostMagazineArticle
  ...helpersCheckIsStyleArticle
  ...helpersSectionContent
  ...helpersStyleSectionContent
}

fragment helpersApplicationBase on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostiesPage
  ...helpersCheckIsPlusPage
}

fragment helpersCheckIfNewsSectionInFirstIndexSection on Section {
  name
}

fragment helpersCheckIsAmpEnabledArticle on Article {
  entityId
  types {
    value {
      entityId
      id
    }
  }
  sections {
    value {
      entityId
      id
    }
  }
  disableOffPlatformContent
  sponsorType
  published
  ...helpersCheckIsPlusArticle
  ...helpersCheckIsPostiesArticle
}

fragment helpersCheckIsLiveArticle on Article {
  flattenTypeIds
  liveArticle {
    status
    id
  }
}

fragment helpersCheckIsMainTopicContent on Content {
  __isContent: __typename
  topics {
    entityId
    id
  }
}

fragment helpersCheckIsPlusArticle on Content {
  __isContent: __typename
  ... on Article {
    paywallTypes {
      entityUuid
      id
    }
  }
}

fragment helpersCheckIsPlusPage on Page {
  urlAlias
}

fragment helpersCheckIsPostMagazineArticle on Article {
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersCheckIsPostiesArticle on Article {
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersCheckIsPostiesPage on Page {
  urlAlias
}

fragment helpersCheckIsStyleArticle on Content {
  __isContent: __typename
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersGetArticleTypeArticle on Content {
  __isContent: __typename
  ... on Article {
    types {
      value {
        entityId
        id
      }
    }
  }
}

fragment helpersMassageToNewsletterItemNewsletter on Newsletter {
  entityId
  name
  alternativeName
  description {
    text
  }
  summary {
    text
  }
  homepageDescription {
    text
  }
}

fragment helpersSanitizeArticleTypeEntityIdsArticle on Article {
  types {
    value {
      entityId
      id
    }
  }
}

fragment helpersSanitizeAuthorTypesArticle on Article {
  authors {
    types
    id
  }
}

fragment helpersSanitizedAuthorEntityIdsArticle on Article {
  authors {
    entityId
    id
  }
}

fragment helpersSectionContent on Section {
  fullSectionPath {
    entityId
    id
  }
}

fragment helpersStyleSectionContent on Section {
  fullSectionPath {
    entityId
    id
  }
}

fragment helpersUseContentSponsorContent on Content {
  __isContent: __typename
  topics {
    entityId
    sponsor {
      ...sponsorTagSponsor
      name
      type
      id
    }
    id
  }
  ... on Article {
    sponsorType
  }
  ...helpersCheckIsMainTopicContent
}

fragment hooksArticleDateUtilsContent on Content {
  __isContent: __typename
  createdDate
  publishedDate
  updatedDate
}

fragment hooksArticleSeoArticle on Article {
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostMagazineArticle
  ...helpersCheckIsStyleArticle
  ...hooksContentHeadlineTagContent
  ...helpersCheckIsAmpEnabledArticle
  entityId
  headline
  socialHeadline
  types {
    value {
      entityId
      id
    }
  }
  authors {
    entityId
    id
  }
  images {
    generic_og: style(filter: {style: "og_image_scmp_generic"}) {
      url
    }
    styles(filter: {styles: ["og_image_posties_article", "og_postmag", "og_image_style", "og_image_scmp_analysis", "og_image_scmp_explainer", "og_image_scmp_editorial", "og_image_scmp_fact_check", "og_image_scmp_debate", "og_image_scmp_live", "og_image_scmp_obituary", "og_image_scmp_opinion", "og_image_scmp_review", "og_image_scmp_series", "og_image_scmp_generic"]}) {
      url
      style
    }
    type
  }
  urlAlias
}

fragment hooksContentHeadlineTagContent on Content {
  __isContent: __typename
  __typename
  ... on Article {
    types {
      value {
        name
        entityId
        description {
          text
        }
        id
      }
    }
    ...helpersCheckIsStyleArticle
  }
  flag
  sections {
    value {
      name
      id
    }
  }
  ...hooksContentHelperContent
}

fragment hooksContentHelperContent on Content {
  __isContent: __typename
  ...helpersSanitizeArticleTypeEntityIdsArticle
  ...helpersSanitizeAuthorTypesArticle
  ...helpersSanitizedAuthorEntityIdsArticle
  flag
}

fragment hooksPaywallPromiseContent on Content {
  __isContent: __typename
  entityId
  ...helpersCheckIsPostiesArticle
}

fragment hooksTrackPageViewArticle on Article {
  entityId
  publishedDate
  headline
  sections {
    value {
      name
      id
    }
  }
  urlAlias
  authors {
    name
    id
  }
  entityUuid
}

fragment imageContent on Content {
  __isContent: __typename
  headline
  ...checkersCheckContentContainsStarlingImageContent
}

fragment inlineWidgetContent on Content {
  __isContent: __typename
  ...contentNewsletterWidgetContent
}

fragment mainImagePrintArticleArticle on Article {
  images {
    title
    url
    isSlideshow
    size_652x446: style(filter: {style: "652x446"}) {
      url
    }
  }
}

fragment photoGalleryDialogContent on Content {
  __isContent: __typename
  __typename
  ...contentShareWidgetContent
}

fragment photoGalleryWidgetContent on Content {
  __isContent: __typename
  ...photoGalleryDialogContent
}

fragment scmpYoutubeContent on Content {
  __isContent: __typename
  entityId
  urlAlias
  publishedDate
}

fragment sponsorTagSponsor on Sponsor {
  name
  type
  images {
    url
  }
}


sections

types

disableOffPlatformContent

sponsorType

published

headline

socialHeadline

authors

images

publishedDate

updatedDate

summary

subHeadline

keywords

topics

readingTime

authorLocations

entityUuid

Matt Haldane

Enoch Yiu

Hong Kong is poised to approve its biggest overhaul ever to cryptocurrency regulation in its bid to become a hub for the virtual asset (VA) market. These assets have so far been outside existing regulatory regimes in the city, as they do not qualify as securities under local law.
The new rules currently being deliberated would bring cryptocurrencies under the purview of the Securities and Futures Commission (SFC) as a new asset class. But the government does not specifically mention cryptocurrencies, non-fungible tokens (NFTs) or blockchain – only “virtual assets”.
While the term on its own may sound vague, the SFC has something very specific in mind when it talks about these assets. Here is a look at precisely what the SFC will be regulating and what the changes mean for crypto trading in Hong Kong.
What does Hong Kong mean by virtual assets?
At the most basic level, Hong Kong defines a virtual asset as “a cryptographically secured digital representation of value”.

This is one of several attributes that the government specifies in its definition included in the amendment to the city’s anti-money-laundering law. While the document does not mention blockchain, this technology is widely understood to be the primary means of securing digital asset ownership by using cryptographic signatures on a public ledger.
This means that many NFTs and similar digital products could fall under the purview of the SFC once the amendment is passed. However, there are exceptions that could offer carve-outs for certain types of digital goods.
The amendment specifies that a virtual asset must either be used as a medium of exchange – whether for buying goods, discharging debt or investing – or provide the ability to vote on the management of affairs related to such assets. The latter point suggests that tokens granting rights for the governance of decentralised autonomous organisations (DAOs) also qualify as virtual assets even though they are not used as a medium of exchange.
However, there are some important exceptions. A “limited purpose digital token” does not qualify as a virtual asset in this amendment. This could be an important distinction for things like in-game assets secured using blockchain. Many people expect NFTs to play an important role in securing assets in the metaverse, and this could allow such products to be governed separately.
Additionally, a central bank digital currency does not qualify. In fact, no digital representations of value count under this bill if “issued by a government … or by an entity authorised by the government”, nor do funds stored in digital wallets.




Securities and futures do not qualify as virtual assets, either, but the SFC has been governing these related financial products separately since at least 2017. That year the SFC clarified that bitcoin does not qualify as a security and is therefore not regulated, but it does govern bitcoin futures.
When will the new rules go into effect?
The original proposal of the Anti-Money Laundering and Counter-Terrorist Financing (Amendment) Bill 2022 specifies that the licensing regime for virtual asset services would come into operation on March 1, but the government decided to push it to June 1, according to Joseph Chan, Undersecretary for Financial Services and the Treasury.
Chan said the Financial Services and Treasury Bureau submitted the bill to the Legislative Council in July and it is expected to come to a vote soon, hopefully by the end of this year.
“After listening to the feedback of the Hong Kong Association of Banks and other regulators, we decide to implement the effective date of the law change for the virtual asset licensing regime to be moved to June 1. This will allow more time for the industry to have sufficient time to prepare to comply with the new regulatory requirements,” Chan told the Post, adding that he also informed local brokers about the new effective date.

How does Hong Kong currently regulate virtual assets?
Hong Kong has some minimal regulations for virtual assets that the SFC clarified in past years amid an explosion in the popularity of cryptocurrencies. However, such assets have largely been unregulated and the SFC has said that cryptocurrencies like bitcoin do not qualify as securities and thus fall outside its area of responsibility.
In 2019, the SFC introduced what it has described as a “regulatory sandbox” in the form of a completely voluntary licensing scheme. The idea was that exchanges could give clients peace of mind if they had a government license.
But to fall under the SFC, an exchange would have to issue at least one token that qualified as a security, which refers to a fungible financial instrument that typically denotes ownership of something else, such as stock in a company.
Once under the purview of the SFC, the government agency would be able to assess management of other aspects of the business, including the exchange of cryptocurrencies.
The catch was that the regulation limited exchanges to servicing professional investors, or those with portfolios of at least HK$8 million (US$1 million), to ensure that those trading cryptocurrencies could afford the large losses that may be associated with the volatile assets.

Only two cryptocurrency exchanges opted to get the license – OSL in 2020 and HashKey Pro just this year.
Prior to this regulation, the SFC said in 2018 that portfolio managers that invest more than 10 per cent of a mixed portfolio in virtual assets are subject to certain rules, such as notification requirements for asset management services related to cryptoassets.
While options within Hong Kong for retail crypto investors have been limited in recent years, the opt-in licensing regime has meant that they have never been barred from buying and selling cryptocurrencies on unregulated platforms.
How does Hong Kong plan to regulate virtual assets going forward?
Unlike the 2019 regulation, the new licensing regime will require virtual asset platforms to meet a range of capital and investor protection measures set by the SFC.
The rules are not finalised yet and the SFC is still consulting stakeholders. The biggest change is expected to be allowing licensed exchanges to serve retail investors. Details on how retail participation will be allowed are still being worked out.
Other changes will bring virtual asset exchanges in line with the same anti-money-laundering, counterterrorist financing, and investor protection rules as those currently applicable to traditional financial institutions.

The expected rules for licensing and financial reporting are included in a draft amendment to the anti-money-laundering law that has been released for public review.
As currently written, virtual asset platforms operating in Hong Kong will be granted a nine-month grace period to apply for a license, otherwise they must exit the Hong Kong market.
The amendment will also require platforms to comply with reporting requirements. Similar to other financial reports, VA platforms must detail profits and losses and liquid capital. Additionally, they must list all addresses for where they keep books and records related to asset clients.
Another benefit of the new rules is that banks will be able to offer clients access to virtual assets by partnering with licensed platforms, the government said in its October 31 announcement on the planned changes.
How will the new rules safeguard user assets?
New reporting requirements could help mitigate issues for which FTX was criticised before its collapse last month.
Bankruptcy filings showed FTX had a complex corporate structure spanning dozens of subsidiaries across several markets. A run on the exchange was also exacerbated by a liquidity crunch.
Hong Kong’s main lesson from FTX’s collapse? More regulation is needed
In addition to reporting requirements on liquid assets and addresses of where customer assets are held, platforms will be required to identify risks that could render them insolvent.
The SFC policy already requires licensed platform operators to have an insurance policy safeguarding investors against risks of hacking, but not risks of going out of business, according to Becky Tam, chief operating officer of virtual insurer OneDegree.
Hong Kong-based OneDegree is among the few insurers globally that provides coverage against hacking for institutional cryptocurrency custodians and exchanges that accept cryptocurrency deposits from investors.
Tam said the risk for investors in the case of FTX’s collapse is counterparty risk. “We may consider adding this element to our offerings in the future in accordance with the development and evolution of the cryptocurrency regulatory environment,” she said.


What are virtual assets in Hong Kong and what do the city’s new rules mean for crypto trading?

A man uses a bitcoin ATM in Hong Kong on January 11, 2018. The Securities and Futures Commission has introduced new rules for virtual assets that would regulate cryptocurrencies as a new asset class. Photo: AP

Cryptocurrencies are secured through hash functions like the SHA-256 algorithm depicted here. This converts data into values of a fixed size. Tokens secured this way could soon fall under the purview of the Securities and Futures Commission.

Joseph Chan, Under Secretary for Financial Services and the Treasury, speaking at the SCMP’s Redefining Hong Kong event on November 10, 2022. Photo: SCMP/ Dickson Lee

HashKey Group’s booth during the Hong Kong FinTech Week at the Convention and Exhibition Centre in Wan Chai on November 3, 2021. Photo: Shutterstock

Chief Executive of the Hong Kong Monetary Authority (HKMA) Eddie Yue Wai-man delivers the Opening Keynote on the first day of Hong Kong FinTech Week at the Convention and Exhibition Centre in Wan Chai on October 31, 20222. Government-issued tokens like those for central bank digital currencies do not qualify as virtual assets to be governed by the Securities and Futures Commission under new rules currently under review. Photo: SCMP / Sam Tsang

Tech

Policy

Business

Banking & Finance

Money

News

Hong Kong

New rules on virtual assets are expected to apply to cryptocurrencies but not government-issued digital currencies and limited use tokens
By creating a new asset class, Hong Kong is aiming to reclaim its status as Asia’s crypto hub while addressing concerns in the wake of the FTX crash


New rules on virtual assets from June 2023 will bring all unregulated crypto platforms under SFC oversight as Hong Kong vies to become Asia’s cryptocurrency hub.


Digital currencies

Bitcoin

Blockchain

Banking & finance

Financial regulation

Regulation

Investing

Provide background, definition and detail of a specific topic, helping the reader understand how something works or what has happened in the past.  (Eg. What is Nafta? US and Mexico are on the verge of revising trade deal.)


Explainer

Explainer | What are virtual assets in Hong Kong and what do the city’s new rules mean for crypto trading?

New rules on virtual assets are expected to apply to cryptocurrencies but not government-issued digital currencies and limited use tokens By creating a new asset class, Hong Kong is aiming to reclaim its status as Asia’s crypto hub while addressing concerns in the wake of the FTX crash

New rules on virtual assets are expected to apply to cryptocurrencies but not government-issued digital currencies and limited use tokens

By creating a new asset class, Hong Kong is aiming to reclaim its status as Asia’s crypto hub while addressing concerns in the wake of the FTX crash