About DIDX

DIDX operates the official company and registry layer behind PassPal and Passpod.

DIDX is established in Korea. It helps visitors understand what is official, where to go next, and how safe receipt states can be checked.

What DIDX operates

DIDX keeps the ecosystem organized around three clear roles.

PassPal

The product and pilot interface. Use it to view products, pilots, Console entry, and access requests.

Passpod

The protocol and knowledge layer. Use it to learn TASK Core, AgentTrust, Trust Action Receipts, and sensitive-action workflows.

DIDX Registry

The registry layer. Use it to understand or check safe receipt states when available.

A note from the founder

The story is not about proving a company with too many details. It is about explaining the need DIDX was created to address.

“The next wave of digital risk is not only about identity. It is about actions.”

DIDX was founded by Edward D.C. Park, a Korean founder born and raised in France.

DIDX was created in response to a growing need: AI agents, automated workflows, hackers, and malicious actors can now request or trigger sensitive digital actions faster than people can review them.

Wallets and verifiable credentials are important foundations. The founder is actively studying and engaging with the EUDI Wallet ecosystem and Unfold-related interoperability work, with the goal of making Passpod complementary to wallets rather than competing with them.

But identity alone is not enough. Organizations also need a trust-action layer: a way to check sensitive actions before they continue and record what was requested, checked, approved, denied, expired, or revoked.

That is why the ecosystem is being built around Passpod TASK Core. TASK Core is the rule-checking engine on which useful modules can be built gradually, including AgentTrust, Remote Worker TrustPass, and access-review workflows.

DIDX does not claim official endorsement by EUDI Wallet programs, Unfold, or public institutions. The ecosystem is designed to be complementary to wallets, credentials, and responsible decision-makers.

Boundary: DIDX does not make final decisions and does not expose private documents by default. It anchors the official company and registry layer behind the ecosystem.