Discover and read the best of Twitter Threads about #eos

Most recents (3)

EOSGov: An #EOS network run by the U.S. Government.

Tell me why this wouldn't work.

@BrendanBlumer @bytemaster7 @VitalikButerin @APompliano @lopp
States would compete as Block Producers to earn block rewards.

Dept's will be created in every state from California to New York to build, upgrade, and maintain infrastructure for an EOS.IO fork.

If a state fails to produce blocks, they don't get inflation $
IRS or DMV (or a new dept) would be responsible for on-boarding new users after verifying their identity in person.

Your birth certificate, fingerprints, photo, etc. will all be on-chain.

Some of it public, but most of it private and verifiable.
Read 7 tweets
PSA: If you think the #EOS launch was chaotic, wait until #TRON launches in a couple of days... I also happened to have reviewed the entire $TRX codebase.
My eyes hurt.

They should rebrand to "TRON: the Frankenstein of crypto." Learn more 👇
Justin Sun loves bashing on #Ethereum, which is hilarious, since the majority of Java-Tron's codebase is based on the EthereumJ library - one of the most buggy implementations of the Ethereum protocol. They tried to hide this, but failed: github.com/tronprotocol/j…
Unsurprisingly, the highly marketed Tron Virtual Machine is a FIFO implementation of the Ethereum Virtual Machine, which makes sense given the use of EthereumJ, but once again it was announced as an original and miraculous piece of software.
Read 6 tweets
1/ Chinese Internet security giant 360 has found "a series of epic vulnerabilities" in the #EOS platform. Some of the bugs allow arbitrary code to be executed remotely on EOS nodes and even taking full control of the nodes.

Source (in Chinese): weibo.com/ttarticle/p/sh…
2/ According to their Weibo (Chinese Twitter), 360 reported the bugs to the EOS team. "The person in charge of the EOS network said that the EOS network will not be officially launched until these issues are fixed."
3/ 360: attacker can deploy smart contracts w/ malicious code to EOS super node, which will execute the contract and trigger a security bug. Once the contract is included in a new block, all full nodes including backup nodes, exchges, wallet nodes, are all susceptible to attack.
Read 5 tweets

Related hashtags

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!