npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@aviarytech/didcomm-protocols.trust-ping

v0.1.42

Published

DIDComm Trust Ping Protocol

Downloads

37

Readme

DIDComm Trust Ping

This protocol is core to the DIDComm v2 specification and is a standard way for agents to test connectivity, responsiveness, and security of a DIDComm channel.

There are two parties in a trust ping: the sender and the receiver. The sender initiates the trust ping. The receiver responds. If the receiver wants to do a ping of their own, they can, but this is a new interaction in which they become the sender.

Messages

  1. ping

    The trust ping interaction begins when sender creates a ping message like this:

    {
      "type": "https://didcomm.org/trust_ping/1.0/ping",
      "id": "518be002-de8e-456e-b3d5-8fe472477a86",
      "from": "did:example:123456",
      "body": {
        "response_requested": true
      }
    }

    response_requested: default value is true. If false, the sender is not requesting a ping_response from the receiver. If true, the sender is requesting a response.

  2. ping_response

    When the message arrives at the receiver, assuming that response_requested is not false, the receiver should reply as quickly as possible with a ping_response message that looks like this:

    {
      "type": "https://didcomm.org/trust_ping/1.0/ping_response",
      "id": "e002518b-456e-b3d5-de8e-7a86fe472847",
      "thid": "518be002-de8e-456e-b3d5-8fe472477a86"
    }