W3C home > Mailing lists > Public > public-credentials@w3.org > February 2020

Re: Real BTCR DID Document

From: Christopher Allen <ChristopherA@lifewithalacrity.com>
Date: Wed, 12 Feb 2020 22:36:55 -0800
Message-ID: <CACrqygCL9GkYhTHd3cOLaSmv5av+eap5G1StYfG8OBxQ79i8MA@mail.gmail.com>
To: Dave Longley <dlongley@digitalbazaar.com>
Cc: Credentials Community Group <public-credentials@w3.org>, Wolf McNally <wolf@wolfmcnally.com>
Dave Longley and Joe Andrieu,

In the simplest BTCR establishing transaction, a single key can do
everything. Both of these refer to the same key, but give them different
names (#satoshi will always be mutated to the whatever the key is in the
current spent bitcoin transaction, and #vckey-0 will be immutable and
future bitcoin transaction keys will increment the key name).

"authentication": ["#satoshi"],
"assertionMethod": ["#vckey-0"]

What other proof purposes should we add to this list? Any ideas on which
should be mutable (like #satoshi) or immutable but incremented (like
#vckey-0) and what those the key names should be?


— Christopher Allen
Received on Thursday, 13 February 2020 06:37:45 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:57 UTC