28.03.2024

Legal Framework for Tokenization Submitted to Russia’s Crypto Bill

The head of CBR’s fintech division Ivan Zimin noted that it was one of the biggest projects backed by the sandbox. He was especially excited about the possibility of issuing hybrid tokens, believing that they can “quickly adapt to demands from businesses and users.”

A successful tokenization trial could lead to big changes in Russia’s proposed cryptocurrency legislation.

The Central Bank of Russia (CBR) announced on Feb. 17 the completion of a blockchain tokenization pilot using a platform developed by Nornickel within its regulatory sandbox.

The bank subsequently proposed to amend Russia’s digital assets law to accommodate tokenization platforms.

The platform is open to all organizations and it allows them to issue hybrid tokens backed by a basket of assets. The technology is said to expand financing possibilities for businesses, while giving new investment options for its users.

Zimin also revealed that the bank proposed a regulatory amendment driven by the results of the pilot:

“Following the results of the pilot program, the Central Bank of Russia proposed amendments for the federal bill project ‘On digital financial assets’ that are required to integrate and develop these solutions on the growing digital asset market.”

The platform was developed by Nornickel, one of the largest mining companies in the world. The corporation previously developed the platform to tokenize palladium, and began testing a digital asset trading platform in December 2019.

Crypto’s unclear regulatory status in Russia

The Russian government’s attitude toward cryptocurrency remains somewhat contradictory.

In January 2018, the Russian parliament began work on a bill regulating the usage of digital assets. Multiple delays have crippled the adoption of the bill, which still remains under consideration as of February 2020.

Though Russia’s new Prime Minister identified the digital economy as one of the government’s key priorities, progress is not uniform. Despite solid support for blockchain, the country’s regulators are still skeptical of cryptocurrencies.

Alongside the complex decision-making process, several ministries and the central bank were reportedly considering a ban of cryptocurrency for payments in November, as well as plans for a legal framework to “confiscate” Bitcoin.

Law Enforcement Data Requests Rose by Almost 50% in 2019, Says Kraken

Cryptocurrency exchange Kraken has said the cost of responding to law enforcement requests for user data is rising sharply year on year.

In a tweet on Tuesday, the firm posted an infographic teasing its new 2019 Transparency Report, indicating it had received 710 information requests in total – 49 percent more than in 2018. Last year, the exchange received 475 requests and just 160 were dealt with in 2017.

The country issuing most requests in 2019 was the U.S. with 432 (almost 61 percent of the total). The FBI issues most requests of the U.S. agencies, followed by the Drug Enforcement Administration (DEA) and Immigration and Customs Enforcement (ICE).

The U.K. was the second nation in terms of request volume, with 86 (12 percent), followed by Germany (44) and Italy (20).

Further set out in the infographic, of 1,222 user accounts affected by requests, 62 percent had data returned to the issuing agency. The remaining 28 percent were «non-valid,» meaning that they «did not meet local legal requirements» or Kraken’s policy on law enforcement requests.

Kraken co-founder and CEO Jesse Powell said in a tweet that the cost of servicing such law enforcement requests in a «high-wage market» (the firm is based in California) was more than $1 million in 2019.

«Several things contribute to the cost. Older business with 8+ years of data, millions of accounts, high security around accessibility of personal data, the good stuff is all encrypted and hard/slow/impossible to search/export in bulk (upside being its that way for hackers too),» he said in another post.

Leave a Reply

Your email address will not be published. Required fields are marked *