Polish Parliament Fails to Override President's Veto on Crypto Regulation Bill

iconKuCoinFlash
Share
AI summary iconSummary
On-chain data shows that Poland’s lower house failed to override President Karol Nawrocki’s veto of a crypto regulation bill on September 4. The vote resulted in 241 in favor and 198 against, falling 25 votes short of the 266 required. The bill would have designated the KNF as the crypto regulator. Nawrocki had previously vetoed the bill three times, calling it overly burdensome. On-chain analysis suggests the stalled legislation could impact market clarity. Prime Minister Tusk advocated for approval, citing the Zondacrypto collapse.

Odaily Planet Daily report: On September 4, Poland’s lower house of parliament failed to override President Karol Nawrocki’s veto of the cryptocurrency regulatory bill. The vote resulted in 241 votes in favor of overriding the veto, 198 against, and 3 abstentions—falling 25 votes short of the required 266. The bill aims to designate Poland’s Financial Supervision Authority (KNF) as the regulatory body for cryptocurrencies and has now been vetoed for the third time by Nawrocki. The president argues that the bill imposes excessive regulation on the industry and could force Polish companies to relocate overseas. Prior to the vote, Prime Minister Donald Tusk cited investigations related to the collapsed exchange Zondacrypto and urged lawmakers to support the bill.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.