# ZK-PKI, Blockchain native Public Key Infra

**URL:** <https://forum.polkadot.network/t/zk-pki-blockchain-native-public-key-infra/17316>\
**Category:** Ecosystem\
**Created:** [March 14, 2026, 12:34pm UTC](https://forum.polkadot.network/t/zk-pki-blockchain-native-public-key-infra/17316 "2026-03-14T12:34:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![prodigalwon](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/prodigalwon/32/10964_2.png) [@prodigalwon](https://forum.polkadot.network/u/prodigalwon)\
**Post date:** [March 14, 2026, 12:34pm UTC](https://forum.polkadot.network/t/zk-pki-blockchain-native-public-key-infra/17316/1 "2026-03-14T12:34:35Z")

</div>

Got your attention, did I?

A blockchain-native X.509 workflow, built it for Substrate in FRAME. Not on GitHub yet, debating patenting first. I don’t know of anyone else doing this in any blockchain ecosystem.

Once production-ready, the goal is to deploy on Paseo, proof it, and submit for consideration as a Kusama pallet.

The mobile app and DNS-adjacent pallet projects are both rapidly approaching production-ready! As of today, the Android VM was buying registered names from the SDK node hosting the DNS pallet.

Stay tuned, I actually deliver on things. Its the potential politics and nepotism I’m worried about.