Try   HackMD
{ // message
  PROCESSING: {
		nonce: 12345...,
    recipient: Bob
  },
  AUTHZ: {
    signer: Alice,
    target: Lawyer
  }
}
  1. Recipient in processing
    • Avoid leakage of contacts via iterability
  2. Remove recipient from contextId
    • Avoid leakage of contacts via iterability
  3. Move target to AUTHZ
    • To store in different destinations
    • Computed message/canonical ID remains the same even if AUTHZ is a different JWS
  4. Nonce protects against iterability of signer DID.
Last changed by 
 
Daniel Buchner
1
109

Read more

DWeb Node Protocols Interface

Across a wide array of decentralized app, service, and protocol scenarios there exists a need for entities to expose various interactions to the public and shape interactions that adhere to expected schemas, data relationships, and protocol flows (e.g. tbDex). The following proposal describes a mechanism for defining protocols and associated logic DWeb Nodes use to address these needs in an extensible way that covers the vast majority of app and service use cases.

Aug 15, 2023
Why Can Haz No?

ipfs.send(['/dns6/foo.com/tcp/443/https', SECOND_MULTIADDR], CID, BLOCKSTORE) ipfs.retrieve(['/dns6/foo.com/tcp/443/https', SECOND_MULTIADDR], CID) IPFS CAT Swarm.connect();

Mar 2, 2023
TP1 - DWeb Node Protocols Interface

Created: August 9, 2022 Status: Draft Summary Across a wide array of decentralized app, service, and protocol scenarios there exists a need for entities to expose various interactions to the public and shape interactions that adhere to expected schemas, data relationships, and protocol flows (e.g. tbDex). The following proposal describes a mechanism for defining protocols and associated logic DWeb Nodes use to address these needs in an extensible way that covers the vast majority of app and service use cases. Motivation When thinking about apps and services as protocols, most apps and services have some aspects of interactions between participants that is open to the public and must follow certain business rules for how data is related and handled. Being able to expose open initiation of app or service flows is something you see with Twitter (anyone can reply to your tweets), credential issuance (anyone can apply for a credential), and tbDEX (anyone can submit an Ask), to name a few. Additionally, in virtually all apps and services there exist relationships between data/objects that define what objects are attached to others, and who can perform certain actions within a flow. Due to the fact both credential issuance and tbDEX require both of the technical capabilities outlined above, we need to put such a mechanism in place to enable them. Goals

Sep 16, 2022
Hub Specification Planning

Oct 30, 2019
Read more from Daniel Buchner
Published on HackMD