EOSCommunity.org Forums

Issue #3: September 2019

Issue #3: September 2019

Hey everyone! We’ve officially decided on a cadence for the newsletter— we’ll be sending it out the first week of each month. We feel that this will leave enough time in between each newsletter for us to really separate the signal from the noise and offer updates on the most important things happening in the EOSIO ecosystem. Our goal is for this newsletter to be the the best resource for staying on top of important developments in this space. If you have any suggestions on how we can improve it, please let us know (via Twitter, Telegram, or by responding directly to this email).

If you like this newsletter and want to support this (and other work we do), please consider voting for us on the EOS mainnet (and WAX) at teamgreymass .

EOSIO Ecosystem Updates

EOS Incubator by Tokenika

Tokenika, the block producer based in Poland, has officially launched EOS Incubator. True to its name, EOS Incubator is an incubator and accelerator for projects building on EOSIO software. If you are working on a project and could use some additional resources, make sure to reach out to the team.

Block.one’s Digital Identity Patent

Block.one is generally pretty quiet about what they are working on, but the folks at Everything EOS always seem to be paying attention where nobody else is. They recently discovered a patent by Block.one for “systems and methods for creating a secure digital identity.”

It’s a new system developed by Dan Larimer and a number of others that ties users to devices and devices to public keys, where the entire process is audited on-chain. It’s interesting to see Block.one explore a non-KYC digital identity system, especially given the fact that they have pitched Voice as a KYC’d platform. You can read more about the patent on Google Patents here.

Remme: Distributed Public Key Infrastructure on EOSIO

Block.one interviewed the team behind Remme, a new EOSIO-based chain for public key infrastructure (PKI). The team describes it: “That PKI protocol utilizes the EOSIO codebase to create a decentralized system for storing and revoking digital keys in a highly secure manner.”

It’s quite an interesting project and use case for EOSIO software. We’re excited about the project and have been poking around their Telegram group to learn more.

Chintai Updates

We’re incredibly impressed with the Chintai team’s rate of shipping recently. They just launched two major new services.

Mynt (short for “My Native Token”) is “an end-to-end service for deploying customizable token distribution events on EOSIO blockchains.” The team is leveraging their experience launching the CHEX token to provide not just technical infrastructure for teams looking to distribute tokens, but also legal and financial advice.

The Chintai team also recently launched an automated resource management service. This is a really important step towards allowing dApps to abstract away resource management and other blockchain complexities from end-users. You can read more about that service here.

Wordproof: Timestamping for Wordpress on EOSIO

Wordproof is a new service that allows Wordpress users to timestamp their content (and subsequent updates to their content) on the EOS blockchain. Wordproof is similar to proof of existence on Bitcoin and EOS Argentina’s project EOSProof. The difference is that Wordproof aims to make timestamping dead simple for existing users of Wordpress (which powers more than 1/3 of the websites on the internet).

Here’s a short video explaining how Wordproof works:

Greymass Updates

Coffee with Greymass

We launched a new podcast! It’s called Coffee with Greymass, and we’re really excited about it. CWG will be a venue for us to have interesting conversations related to EOS and the crypto ecosystem at large.

Our first episode was a team update where we discuss the many things we’re currently working on internally— Anchor, our new signing protocol, our APIs, and some of our plans for the future. It’s a great overview of everything exciting we’re doing here at Greymass. Our second episode is an interview with our very own Johan Nordberg, where we talked about his other project, Decentium.

We’re really excited about launching this podcast and will be doing episodes regularly. If there’s a subject you’d like to hear us discuss, or a guest you’d like to see us interview, please let us know!

Driving Adoption: a look at the internet, the web, and now crypto by Jesta

Our very own Aaron Cox (aka Jesta) just spun up his own Decentium blog. His first article, Driving Adoption, is a look at the history of the web and what it can teach us about adoption of blockchain technology (along with some prescriptive measures we, as a community, can take to ensure that happens as quickly and smoothly as possible). It’s an awesome article, and we recommend giving it a read. It was initially written in response to a question posed to the EOSIO community via Telegram from the Starkness proxy about what can be done to increase EOS adoption.

Delphi Oracle Update

EOS Titan’s Delphi Oracle is one of our favorite projects on EOS, providing a distributed price feed oracle that pulls from multiple sources to eliminate reliance on any single party (we’re one of the BP participants). The EOS Titan team has been hard at work developing several other use cases for this oracle besides just price feeds, and they’ve recently launched a random number generator (RNG). The RNG will use multiple inputs to compute a random number that will essentially offer “randomness-as-a-service” for dApps and other projects built on EOS. It’s still a work in progress, but we’re excited about this as well as some of the other Delphi-based services EOS Titan is working on.

EOSIO 1.8 Test Environment

The upcoming EOS mainnet hard fork to transition to EOSIO v1.8.0 is happening soon, so we’ve created an API test environment for developers to test their applications before the September 23rd activation date. If you’re an application developer, you’ll need to take some measures to make sure you are ready for the change over.

The endpoint for the test environment can be accessed here.