microcosm.blue / Allegedly
Server tools to backfill, tail, mirror, and verify PLC logs
fork atom

PLC Directory Discrepancy: @context Crypto Header Differs Between Allegedly and Source #5

closed
opened by tree.fail

When comparing PLC mirrors, I noticed that Allegedly returns a slightly different DID PLC document than the source plc.directory (according to a comparison of SHA256 hashes of raw output).

Further investigation reveals that reason is a different @context header for crypto: instead of ecdsa-2019, it returns secp256k1-2019.

Here is few affected DIDs:

  • did:plc:n723ktsgvd2bdjpxqwi3ayvb
  • did:plc:um46rb2ebnlwx44fimib6utx
  • did:plc:twbsv3treiimobyuwrz3pm3h

enter image description here

https://atproto-resolver-benchmark.pages.dev/ (pls ignore Enter DID... it does nothing :))

tree.fail (author)

Okay... I guess I'm stupid, this is a problem of geesawra allegedly fork and parakeet... not allegedly. I rushed to help and completely messed it up 🤦‍♂️. I apologize. Closing

sign up or login to add to the discussion
Labels

None yet.

Participants 1
AT URI
at://did:plc:524tuhdhh3m7li5gycdn6boe/sh.tangled.repo.issue/3m6osmbovod22