EOS Drama Continues As Heated Exchange With Block Producer Emerges

Avi Rosten

The ongoing drama surrounding the EOS platform’s controversial consensus mechanism took another interesting turn today - as a screenshot apparently showing a conversation with an EOS block producer (BP) has emerged.

Posted as an image on popular subreddit r/cryptocurrency, the screenshot shows a heated Telegram exchange between an EOS block producer, and another unidentified EOS participant - who chastises the BP for failing to freeze some accounts as directed by the EOS Core Arbitration Forum (ECAF):

eos chat.jpg

While the authenticity of the conversation has yet to be confirmed, the post has generated a stir on social media, with popular cypto figure Whalepanda chiming in on Twitter:

As recently covered on CryptoGlobe, this aspect of the EOS governance model has been highly controversial within the crypto community - as many critics have pointed out that the 21 block producers act in principle as a highly centralised concentration of power.

Despite the fact that EOS allows for BPs to be continuously elected, because of the enormous centralisation of the token’s holdings - the system effectively ensures that EOS whales exert a massively disproportionate influence over who is elected (as argued yesterday).

This latest revelation - if legitimate - again seems to underscore the problems associated with a system that places too much power in the hands of individuals.

Not only does it illustrate the problems of a protocol which might fail to punish bad actors, but it also points to a worryingly dystopian form of governance - where a kind of central committee issues diktats, backed up with threats of legal action.

While the future of one of the world’s largest cryptoassets remains unclear for now, it seems reasonable that token holders might start to question the platform’s organisation if instances such as this one continue to emerge.

Block.one Releases Open-Source Software for Crypto Wallet Ecosystem

Block.one, the Cayman Islands-registered software technology firm responsible for the initial development of EOS, a leading platform for building decentralized applications (dApps), has published a blog post in which it noted that crypto wallets are “a pivotal component in the path towards mass adoption of blockchain-based software.”

Although Block.one will not launch its own wallet “at this time,” the IT firm has released its open-source software which also includes the introduction of EOSIO Labs™.

As explained in EOSIO’s blog, Block.one has open-sourced the Universal Authenticator Library (UAL) Github Repository. According to the blockchain development firm, “this initiative demonstrates an alternative approach” for application developers “integrating with an Authenticator.”

Optional UI Layer For “Consistent Look And Feel”

An Authenticator system may include key managers, wallets, and app explorers. Software developers will be able to access and build programs using a “single, universal API,” EOSIO’s blog post noted. Explaining how the API will function, the blog mentioned that it will provide software architects “an optional … user experience (UI) layer so that users get a consistent look and feel” - which is “independent of the wallet they are using or the site they are on.”

Acknowledging that there’s been an “explosion in the number of [cryptocurrency] wallets” (both hardware and software-based), EOSIO’s blog mentioned that software developers now have a lot more work to do. That’s because they must “integrate with all of those proprietary wallet APIs.” From the end users’ perspective, there may be “increased uncertainty” and “even confusion” - as they may “find that the app they want to use” is not compatible with the wallet(s) they prefer to use, the blog post stated.

Clarifying that “open source repositories for projects” officially released under EOSIO Labs are to be “considered alpha,” the developers at Block.one noted that users must have “no firm expectation of future involvement by Block.one.” Moreover, the privately held company stated that its “continued contributions and involvement will depend on wider community adoption of such projects.”

Repositories Are “Experimental” But Can Graduate To “Supported Status”

Currently, EOSIO Labs “repositories are experimental” (“released under MIT license”), however programmers can use them as “the basis for code and concepts to incorporate into their applications.”

Because the repositories are “not supported by Block.one,” the company confirmed that it will not be “providing responses to issue reports, pull requests, [and] updates to functionality.” The blog further stated:

Depending on the adoption of concepts and codebases from within the EOSIO Labs umbrella, select repositories and concepts can graduate over time to supported status to enable such projects to move ahead rapidly. As projects graduate from EOSIO Labs, they will enjoy the support we feel is needed, as afforded to actively maintained EOSIO open source libraries such as Demux, EOSJS and others.