Coz

{ "pay": { "msg": "There are also other options.", "alg": "ES256", "iat": 1748248973, "tmb": "9PcBWntvjAktwfiPp8WxgOyQOwc1h6Lo1UnB_gkWXKk", "typ": "cyphr.me/msg/create" }, "sig": "sHyMrykhsta5etjqH1e5oho0EpEs2FrblQ0DFHQo0aMgKd2V__SQ2Fl2EOSKt8wl65iLmKgIaMVEgCmhtvbUcg" } Verify: https://cozejson.com Spec: https://github.com/Cyphrme/Coze

We addressed these concerns while developing Coze, a cryptographic JSON messaging specification. The specification details how we chose to address these concerns. https://github.com/Cyphrme/Coze

And shameless plug for another alternative, Coze: https://github.com/Cyphrme/Coze

We're working on an open source alternative to Passkeys starting with Coze https://github.com/Cyphrme/Coze. We have not yet published our next steps, but we will soon.

Coze is open source under the BSD 3 license, and the reference implementation is written in Go. You can play with Coze using the online tool (https://cyphr.me/coze). There is also the simple tool (https://cyphr.me/coze_verifier_simple/coze.html). This is an example coze: { "pay": { "msg": "Coze Rocks", "alg": "ES256", "iat": 1623132000, "tmb": "cLj8vsYtMBwYkzoFVZHBZo6SNL8wSdCIjCKAwXNuhOk", "typ": "cyphr.me/msg" }, "sig": "Jl8Kt4nznAf0LGgO5yn_9HkGdY3ulvjg-NyRGzlmJzhncbTkFFn9jrwIwGoRAQYhjc88wmwFNH5u_rO56USo_w" } Coze also defines a key format allowing cryptographic keys to be represented completely in JSON: { "alg":"ES256", "iat":1623132000, "kid":"Zami's Majuscule Key.", "tmb":"cLj8vsYtMBwYkzoFVZHBZo6SNL8wSdCIjC

Our website is already using public key authentication using Coze. https://github.com/Cyphrme/Coze. We've been doing public key authentication for around 2 years now. No passwords needed, just public key auth.

On my website, I'm doing authentication via simple public key authentication using Coze. No passwords. No email. No Google. Just public key authentication with private keys in possession of the user. https://github.com/Cyphrme/Coze

Our contribution to solving the digital identity problem is Coze, an open source and cryptographic messaging specification. [https://github.com/Cyphrme/Coze] We use Coze to sign messages that authorize user actions, such as uploading images, logging in, and leaving comments.

How to fix censorship on social media? Empower everyone with their own cryptographic keys. This requires easier to use cryptographic tools so developers can write clients for users. I'm working on a tool that makes using cryptography easier: https://github.com/Cyphrme/Coze

Disclosure, I'm the author: If you're looking for something different from JWT, allow me to suggest Coze. https://github.com/Cyphrme/Coze

Now that there's less eyeballs on this. Here's our open source JWT alternative: https://github.com/Cyphrme/Coze. We've got a roadmap in using that to build alternatives to FIDO. Please feel free to message me with questions or anything else and I will detail our plans. Before competing against FIDO, the libraries need to be far more ergonomic. Coze is a good start. > I’m absolutely willing to help any project with these goals. We would love your help.