did-dht-method
go-pdu
| did-dht-method | go-pdu | |
|---|---|---|
| 2 | - | |
| 20 | 46 | |
| - | - | |
| 9.3 | 7.0 | |
| 8 days ago | 9 months ago | |
| Go | Go | |
| Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
did-dht-method
-
9 Things You Didn't Know About Decentralized Identifiers
TBD is the company I work at. It's a business unit within Block. created its own DID method called DID:DHT. DHT stands for Distributed Hash Table indicating the use of Mainline DHT. You can learn more about DID:DHT via the spec and this blog post from TBD’s Director of Open Standards, Gabe Cohen.
-
The Did DHT Method Specification 1.0
This is pretty neat, but you should publish a spec for Pkarr -- the layer below did-dht -- first. Right now Pkarr is a software program/library, not a specification. I think this will help you simplify and articulate your work more clearly to people who aren't immersed in it. I think it will also be extremely useful to people who don't need the incredible complexity of w3c DIDs.
The choice to sign an entire DNS packet seems very strange and probably hasn't been through through properly.
Why use DNS packets? Presumably because you want to leverage the existing infrastrucure of recursive DNS resolvers. However these resolvers do not preserve packets!. If I send a query to my recursive resolver, and it makes a query to the authoritative server, it can (and almost always does) modify the resulting packet from the authoritative before returning a reply to me.
The upshot here is: if you're signing packets, almost all recursive resolvers will destroy your signatures. This is why DNSSEC signs individual resource records instead of packets. I think that's what you want to be doing: sign an RR, not a packet. If you absolutely need to sign multiple RRs, you'll need to specify a canonical way to assemble the RRs (i.e. sort them). But I really think you want to sign a single RR, which includes the hash of other RRs.
Lastly, please take this issue more seriously: https://github.com/TBD54566975/did-dht-method/issues/80#issu... the only response given was that "the DHT-DID [spec] uses Pkarr [a piece of software]" which makes no sense... specs depend on specs, not implementations. Then the issue derailed (as unthreaded discussions always do... gee thanks github for ruining everything) into some side tangent about KRPC and CBOR instead of addressing "why DNS?".
go-pdu
We haven't tracked posts mentioning go-pdu yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
ORCID-Source - ORCID Open Source Project
resgate - A Realtime API Gateway used with NATS to build REST, real time, and RPC APIs, where all your clients are synchronized seamlessly.
did-spec-registries - DID Spec Registry (Note)
Nomad - Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.
torrent - Full-featured BitTorrent client package and utilities
dragonboat - A feature complete and high performance multi-group Raft library in Go.
DHT - BitTorrent DHT Protocol && DHT Spider.
hprose - Hprose is a cross-language RPC. This project is Hprose for Golang.
gocelery - Celery Distributed Task Queue in Go
glow - Glow is an easy-to-use distributed computation system written in Go, similar to Hadoop Map Reduce, Spark, Flink, Storm, etc. I am also working on another similar pure Go system, https://github.com/chrislusf/gleam , which is more flexible and more performant.
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
serf - Service orchestration and management tool.