Story – Korea Crypto Crackdown
South Korean regulators have announced a plan to ban banks from activities involving cryptocurrencies, prompting major banks in the country to declare they will no longer issue accounts required for crypto trading.
South Korea’s top bitcoin exchanges are all affected, including Bithumb, Coinone, and Korbit. Banks that have made announcements include Shinhan Bank, Korea Development Bank, and Industrial Bank of Korea..
There’s a 2 minute video report on this from the Straits Times:
In which the reporter says things like the one group in particular that has got authorities alarm bells going off is students.
“On Wednesday the government held an emergency meeting to try and find a solution.”
Erm, excuse me? A solution to people using their own free will to do what the hell they want to do with their own money? Unbelievable.
South Korea is a country where gambling is only legal for visiting foreigners. I mean what on Earth?
So they have casinos but the national citizens are not allowed to use them?
Anyway the Korean authorities said they may even come out with their official announcement about what they are going to do as soon as Friday, which is tomorrow.
Many of us will see this as bad news because it was the big waves of Korean money flowing into crypto that have generated such nice gains for us over the last few months.
For that one reason I’d like the Korean authorities to leave well alone.
The actual solution to to make sure everyone understands the risks of what they are doing and then get out of their way, allow them to exercise their free will and teach them to take responsibility for their own actions.
This doesn’t stop crypto to crypto trading of course, it just stops you registering a bank account to trade fiat for crypto.
Story – EOS On The Rise Again
As you probably already know, I’m a huge EOS fanboy, am completely biassed towards it and you should probably just skip this whole section of the video.
If you are still here then let’s take a look at a development that could end up being one of many significant projects for EOS:
The Coin telegraph article here claims that Everipedia is going to make use of the EOS blockchain and EOS storage.
Being an EOS fanboy I want to just accept this blindly, but I’m not going to.
From the research I’ve done on this, this morning, the proof that Everipedia are going to use EOS is in the draft version of the Everipedia whitepaper.
In the limited amount of time I had to investigate this today I haven’t yet managed to get a copy of this draft whitepaper and verify the EOS claim for myself.
That is where you come in dear viewers. If anyone can post a comment on today’s video with a link to the draft whitepaper, if you include your Steem username I’ll send you a Steem Dollar as a thank you.
I say a Steem Dollar because the transaction will be free, take 3 seconds and has a stable value.
The YouTube comments are time stamped remembered so it’s basically who ever posts it first gets the reward.
The reason that Everipedia is significant is because the cofounder of Wikipedia Dr Larry Sanger has joined as their chief information office because he sees Everipedia being the replacement for Wikipedia.
Now I’m just waiting for the day that CryptoKitties announces that it is moving to EOS and then we can really celebrate.
Story – Blockchain.info Launch Full BCH Support
As promised by Blockchain.info in an announcement I covered on the 16th of November they have just launched full support for the sending and receiving of Bitcoin Cash using the world’s most popular web wallet..
Here’s the video if you want to go back and check it out.
They said they’d roll out Bitcoin Cash support before rolling out Segwit support for Bitcoin which they have yet to do.
As I said when I covered the announcement, this is going to do Bitcoin Cash the world of good because it raises awareness and enables a super simple way for people to store and manage their Bitcoin Cash.
At time of recording Bitcoin Cash support isn’t appearing in the mobile app but I’m sure that’s not far away.
*5,000 character limit reached.*