Ethereum

The beta for Web3PGP is open and live on Kraken Ink testnet. Come & Play. Feedbacks and reactions are welcome 🙏

The beta for Web3PGP is open and live on Kraken Ink testnet. Come & Play. Feedbacks and reactions are welcome 🙏 

https://w3pgp-3izi8135u-gbdevws-projects.vercel.app/

Very cool, I've been looking forward to something like this for a while.
Qs:
- Is it using EAS for publishing to the chain, or custom events?
- Any plans to import existing keys from the MIT keyserver?
- Can I gpg --fetch-keys from this registry, or are you planning to send an upstream GnuPG patch to add this feature?

Contributor @ /walletbeat.

Censorship resistance requires privacy.

Hey thank you for those questions 😊 

It is even simpler: the Blockchain only records the OpenPGP messages which contain the public key or the revocation certificate as the data of a simple Ethereum log (event). The smart contract enforces the key fingerprint uniqueness.

Then, the user can extract the OpenPGP message from the Ethereum log and verify it using its OpenPGP client/library 

I already have a CLI named 'dexes' but I haven't released it yet. The CLI only acts as a light client from W3PGP and takes as input OpenPGP messages like that:

gpg --export --openpgp --armor <fingerprint> | dexes w3pgp publish-key

Or you can import a key from the Blockchain into your GPG keyring like that

dexes w3pgp fetch-key <fingerprint> | gpg --import

Thanks! 🙂  

The idea when I create CLI and integration toolkits is to try to adopt and stick with the UNIX philosophy. gpg is already a great tool and there are lots of other ones like key servers etc... My goal is only to provide a bridge to the blockchain.

Currently, I am working on the events. The CLI will keep running and publishing events (key published, key revoked). The user can choose to print the output on the stdout, in a file or in a unix socket so another program can relay events to messaging systems or other programs. Messages are formatted as cloudevent and use opentelemetry so traceability data are forwarded with the events. The goal is also to achieve distrubted tracing easily.

And maybe, one day,  an AI agent will use it 😁

Very cool, I didn't think of using pipes to shovel directly from the chain to gpg and vice versa.