Web 7.0™ / TDW AgenticOS™ / TDW™ / Hyperonomy™ Digital Identity Lab

Copyright (c) 2022 Michael Herman (Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
https://creativecommons.org/licenses/by-sa/4.0/legalcode

The following is an excerpt from a whitepaper I’m working on. Early feedback is always welcome.

BREAKING NEWS: I’ve added some of the more recent revisions that have been made to the DIDComm-ARM to this preview post:

• Layer 4 DIDComm Agent Mesh Network Model
• Layer 5 DIDComm User Agent Model

UPDATE: The most recent version of this whitepaper can be found here:

• Web 7.0 DIDComm Agent Architecture Reference Model (DIDComm-ARM)

Copyright (c) 2022 Michael Herman (Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
https://creativecommons.org/licenses/by-sa/4.0/legalcode

Also checkout: Truth and Marketplace of Ideas

This preliminary taxonomy attempts to characterize the differences between facts, options, folklore, and related terminology. Your feedback is appreciated.

• Facts
  • True Facts – Truths – Hard Facts – 100% true
  • False Beliefs – believed to be true but are, in fact, false
  • Fake Facts – knowingly or purposely 100% false (0% true)

• Perturbations of the Facts
  • Misunderstood Facts
  • Misconceived Facts
  • Misstated or Miscommunicated Facts

• Opinions
  • Feedback that may or may not be true
  • Vague
  • Poor recollected
  • Subjective opinions
  • Humorous/satirical

• Folklore
  • Feedback originating with a fourth party and passed on by a third-party

The driver for the above taxonomy is a new belief in the mind of the author is that only facts or truths should be embedded into verifiable credentials. This gives rise to the concept of the Authentic Conversations Spectrum (illustrated below). The author no longer believes that verifiable credentials can be used or should be used to encode “all data on the planet”.

Reference: Web 7.0 DIDComm Agent Architecture Reference Model (DIDComm-ARM) 0.52 Part 2 of 2

Create your own magic with Web 7.0™ / TDW AgenticOS™. Imagine the possibilities.

Copyright © 2022-2025 Michael Herman (Bindloss, Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
Web 7.0™, TDW AgenticOS™ and Hyperonomy™ are trademarks of the Web 7.0 Foundation. All Rights Reserved.

Want to contribute to the World Wide Web Consortium (W3C) Developers Guide for Verifiable Credentials?

W3C is an international community that develops open standards to ensure the long-term growth of the Web.

A new W3C Community Note Work Item Proposal entitled Verifiable Credentials Guide for Developers has been submitted and you can help create it.

I want to invite everyone interested #DigitalIdentity, #DecentralizedIdentity, #VerifiableCredentials, #TrustOnTheInternet, and/or #SecureInternetStorage to join this key group of people who will be defining and creating the W3C Verifiable Credentials Guide for Developers.

Please contact me directly or post an email to public-credentials@w3.org

Links

• Draft W3C Community Note: https://t.co/veg349grR9
• Work Item: Verifiable Credentials Guide for Developers (VC-GUIDE-DEVELOPERS) https://t.co/LziMaeYskG
• GitHub: https://t.co/ptqaUA6IyC

Michael Herman (Trusted Digital Web) 8:35 PM
What are the common/known strategies for bootstrapping a VDR-based decentralized credential/object platform? …asked naively on purpose.

• Strategies for placing the first/initial DIDs in the VDR?
•  …presumably purposed to be the initial Issuer(s) of verifiable identifiers on the platform?

Best regards,
Michael Herman
Far Left Self-Sovereignist

Stephen Curran 5:37 PM
In Hyperledger Indy, which is a permissioned public network, the first transactions are a DID for one of the  “SuperUser’s (aka “Trustee”) of the network, and DIDs for the initial node operators that verify the transactions.  From there, DIDs for additional nodes are added, DIDs for other Trustees and then DIDs of other types of users (Endorsers, authors), who in turn create other DIDs and object types. 
If you look at von-network (https://github.com/bcgov/von-network) you can spin up a little network (4 nodes in docker) and see the transactions that are used to start the network. In that, the seed for the Trustee DID is well known, so once you’ve started the von-network, you can control it. In a “real” network, that seed (and associated private key) would of course be protected by that first Trustee.
For Sovrin, a ceremony was video’d of all the initial Trustees and Stewards (node operators) when MainNet was started in 2017.

VON Blockchain Explorer

Reference: http://greenlight.bcovrin.vonx.io/browse/domain

Reference: http://greenlight.bcovrin.vonx.io/browse/pool

Initial DID Transactions

Initial Node Transactions

First SCHEMA Transaction

Strongly-typed Code to Generate Bob’s UDID Document

Bob’s UDID Document

{
    "CellId": 6601258412767401213,
    "CredentialCore": {
        "udid": "did:svrn:credential:FD54/8F2B/8D61/9C5B",
        "context": [
            "https://www.sovrona.com/ns/svrn/v1"
        ],
        "claims": [
            {
                "key": "authentication",
                "attribute": [
                    {
                        "key": "publicKey",
                        "value": "1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZ"
                    },
                    {
                        "key": "id",
                        "value": "#pubkey1"
                    },
                    {
                        "key": "type",
                        "value": "AUTHN-KEY"
                    }
                ]
            },
            {
                "key": "service",
                "attribute": [
                    {
                        "key": "serviceEndPoint",
                        "value": "http://localhost:5304/"
                    },
                    {
                        "key": "id",
                        "value": "#sep1"
                    },
                    {
                        "key": "type",
                        "value": "SEP-TCS"
                    }
                ]
            },
            {
                "key": "testkey1",
                "value": "testvalue1"
            },
            {
                "key": "testkey2",
                "attributes": [
                    [
                        {
                            "key": "publicKey",
                            "value": "1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZ"
                        },
                        {
                            "key": "id",
                            "value": "#pubkey1"
                        },
                        {
                            "key": "type",
                            "value": "AUTHN-KEY"
                        }
                    ],
                    [
                        {
                            "key": "publicKey",
                            "value": "1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZ"
                        },
                        {
                            "key": "id",
                            "value": "#pubkey2"
                        },
                        {
                            "key": "type",
                            "value": "AUTHN-KEY"
                        }
                    ]
                ]
            }
        ]
    },
    "Envelope": {
        "kind": "UDIDDocument",
        "encryptionFlag": "NotEncrypted",
        "hashedThumbprint64": "MpUTVq+AYTMEucWUFfMWfsWJRQ6tmO6FGzjAJGMN4T0=",
        "signedHashSignature64": "CLFgZCLJPzozxwB+JjJr7xQdZxgcwbEX4XBsujD+1rCW0sd6T4JFMVFTb86H50HQZ6h7myUld+9pIlbNWS3IPIg11uwYjlzMe32AO+ETCMSEJQJAPN9IJB//C4J2SkAdkK9OszStVsA/GYYtKZQdYSTdDESQCDVw6292N92bIJY=",
        "comments": [
            "Bob's UDID Document",
            "It works!",
            "Created by TDW.TCSServer at 2021-06-15 07:07:09Z"
        ]
    }
}

• Hardwired ThinkPad laptop
  • Edition: Windows 10 Pro
  • Version: 20H2
  • OS build: 19042.928
  • 716 failures
  • 75.67% downtime

• WiFi Wireless Lenovo laptop
  • Edition: Windows 10 Pro
  • Version: 20H2
  • OS build: 19042.985
  • 753 failures
  • 6.86% downtime

• Hardwired ThinkPad laptop: 81.01% downtime (same laptop used for prior NUM reports)
• WiFi Wireless Lenovo laptop: 3.78% downtime