Chainpoint Community Group Announcement

Hello All,


I was surprised to return from a vacation to find ten posts about
Chainpoint added to the mailing list since September 8th.

On the advice of the W3C, we’ve setup a Chainpoint Community Group
<https://www.w3.org/community/chainpoint/> that will work in conjunction
with the Blockchain Community Group.  I hope everyone interested will join.

For over a year, I’ve worked with many of you on evolving Chainpoint
<http://chainpoint.org/> - a standard for creating a universally verifiable
proof of any data, file, or series of events by anchoring data to the
blockchain and other sources. Chainpoint has been a major topic of
discussion at several W3C events and dozens of W3C participants have
provided feedback.  On August 15th, we made good on our commitment from the W3C
Blockchains And The Web Workshop
<https://www.w3.org/2016/04/blockchain-workshop/report> and launched a
major update to Chainpoint.


   -

   *Chainpoint 2.0** Announcement* -
   https://medium.com/@WayneVaughan/chainpoint-a-standard-blockchain-proof-protocol-79def1c37189#.b2gse7f7h
   -

   Official Site - http://chainpoint.org
   -

   Github - http://github.com/chainpoint
   -

   Chainpoint White Paper (latest) -
   https://github.com/chainpoint/whitepaper


We've even started to get some press! At the beginning of September, this
Fedscoop article
<http://fedscoop.com/web-consortium-starts-work-on-blockchain-standards>
appeared where a  Doug Schepers from W3C cited Chainpoint as an example of
a blockchain technology that has made significant progress down the
standardization path.

Since the publication of this article, I have received many emails from
companies interested in Chainpoint.  This included private emails from Adan
Sanchez de Pedro Crespo and several public posts requesting modifications
to Chainpoint to accommodate his company’s technology. These posts don’t
acknowledge the significant effort made to mature Chainpoint, nor the
hundreds of companies that are using Chainpoint.

I understand Adan's requests to add features to a future update of
Chainpoint to accomodate his company's format. We're open to weighing them
against the existing Chainpoint spec and considering future improvements.
We're not starting from ground zero.  We have a mature specification that’s
been in production for over a year, a test suite for generating and
validating proofs in popular languages, and enterprise companies such as
Philips and AT&T using Chainpoint. At each step, we chose to use standard
technologies that could be adopted by a broad set of developers.


   -

   Standard Merkle Trees
   -

   JSON-LD
   -

   Support for all major SHA algorithms
   -

   Extensibility for multiple anchor sources
   -

   Naming conventions that match other widely used technologies


We're happy to discuss the technical choices that were made and look
forward to everyone's suggestions and contributions to future enhancements
in the Chainpoint Community Group <https://www.w3.org/community/chainpoint/>.
I’d like to thank everyone from the community who contributed to Chainpoint
2.0 and the W3C team who helped us organize our efforts over the past year.

Sincerely,

Wayne
----------

[image: Tierion] <http://tierion.com/>

Wayne Vaughan / CEOwayne@tierion.com / 860.836.8633

Tierionhttp://tierion.com

[image: Twitter] <https://twitter.com/waynevaughan> [image: Linkedin]
<https://linkedin.com/in/wayne> [image: skype]
<https://htmlsig.com/skype?username=w.vaughan>