have been in quite intensive dialogue and development is starting to progress quite well, and it was decided by myself and @faddat that we need to announce what we are doing, and provide the avenue for interested folks to look at the actual work we are doing.

The subproject that we are working on is a cryptographic authentication registry that implements the functions you may be familiar with from Steem as regards to changing user keys, and such, but we are implementing an open standard, with the aim of engendering wide integration with the authentication system we will build Dawn on.

It will include as well as the base keychain of what will become the primary Dawn authentication system, as well as registers for other cryptographic public keys (wallet addresses, and the like) that are tied to the identity you register.

We also will be assembling as many validators for this subchain as possible, though because this is a dependency of the Dawn Ray token ledger, at this point nobody will get paid for hosting this blockchain database. That will come later. It is a very lightweight application, it will resemble in some respects LDAP directories, which don't use asymmetric encryption authentication, which is part of the reason for doing this (increased security).

here is the beginnings of our specification of the new Dawn subproject which is going to be getting the name go-login:

https://quip.com/PKG6A4P7RMqt

You can watch, and you can join the conversation, and if you want to join in the writing, we can grant you write access to add to the document.

aside from this specification side of things, we are beginning the writing of the actual Go language code that will implement the system described in that above mentioned document.

We want to promote the idea, and leverage the power of open access, so that everyone can get involved if they have the desire and skills, so we have an open eclipse web app configured that will house the code-editing side of the task for go-login.

So if you are curious, and/or interested, you can join the development work also here:

http://167.114.0.102:8080/dashboard/#/ide/che/go-login

I just want to add a few more remarks about this. You can read this in the draft document related to this in the first link above, but I wanted to also make brief notes here. We will be building both a client and server side (validator) app with this.

The validator is the record keeper, which everyone understands well enough (like bitcoin miners, or steem witnesses), but designers of these systems, notably demonstrated with the design of Steem, do not consider the actual hosting side of the process - there is a pretty severe shortage of Steem RPC nodes to feed data to users of the system, and proxy their signed broadcasts creating new data on the chain.

And user interface is often left as an afterthought when in fact it's almost more important to have a decent interface than a working back end! Ok, that's an exaggeration, really, the two are both in the same class and of the same importance for the ecosystem.

So we are also writing a client-side service, which will be installed on user's devices, that securely stores their private keys, and provides an interface for them to unlock and gain access to their keys, as well as broadcast their updates to the network of validators. Ideally this will integrate with the authentication systems that use this service as well.

goal of this subproject is to create a tool that simplifies cryptographic authentication for users, creates a global directory of users and their keys so you can just search a username and then send them a message, or money, as the case may be.

By making it completely open and public domain, but targeting the eventual universal use of such a system, we intend that we are creating also a userbase that can more easily migrate to using our tokens as well, by using the same identity they use on every other system that also uses this authentication registry.

It is, in other words, part of the overall Dawn strategy, to include everyone, and critically, try to eliminate the partitioning of the network that is so prevalent in the swarms of users who are on facebook, but not twitter, on reddit, but not slashdot, etc. This approach is the guiding Principle of Dawn - that there should be no barriers between any group of users or any project or any service, except the ones that are necessary for security.