Contact ValiDeck
ValiDeck is developing PCX as shared infrastructure for privacy-preserving transaction records. At this stage, the most useful conversations are with organizations that operate payment rails, merchants that generate transaction records, researchers working on privacy-preserving computation, and investors interested in infrastructure that sits beneath applications rather than competing with them.
If your work intersects with those areas, write directly. Email reaches the founder without an intake form or intermediary, so providing a little context about what you are building, researching, operating, or evaluating usually makes the first exchange more useful.
How to reach us
One address, one person, no routing. Expect a reply within two business days.
alok.narula@valideck.com
Phone
(226) 751-6476
Post
7-50 Doon Road
Kitchener, ON N2G 3C8
Canada
Payment channels and merchants
ValiDeck is looking for the first organizations willing to test PCX against a live transaction rail. That requires participation on both sides of the transaction: a payment channel capable of carrying the required protocol data and merchants willing to generate records in the prescribed form.
If you operate payment infrastructure, merchant systems, point-of-sale technology, acquiring services, or related commerce infrastructure, the most useful starting point is to describe how transaction information moves through your systems today, where it is retained, and where the record currently stops.
The objective is not to replace existing payment infrastructure. It is to determine how PCX can operate alongside it while adding a standardized, privacy-preserving record layer.
Investors and researchers
PCX is specified end to end and the core patent family has been granted in multiple jurisdictions. The protocol itself is pre-build, and the immediate objective is to move from specification to a working Phase I implementation.
For investors, the relevant question is therefore not whether another consumer application can be built, but whether a new infrastructure layer for transaction records can be validated technically and commercially.
Academic groups working on privacy engineering, cryptography, distributed systems, data architecture, and privacy-preserving computation are also welcome to write directly. ValiDeck is particularly interested in work that can help test the protocol’s assumptions, security boundaries, and implementation choices.
Before you write
The PCX white paper provides the most complete description of the protocol, while the FAQs address many of the questions that arise during an initial review. The Technology, Patents, and Roadmap pages provide additional context on the architecture, intellectual-property position, and development sequence.
Reading the material most relevant to your area before writing usually makes the first conversation substantially more productive. You do not need to understand every part of PCX; it is more useful to identify the part that intersects with your own work.
Working here
ValiDeck is still at the stage where building the technology also means building the team around it. Phase I will require people who can work across boundaries rather than within narrowly defined product roles — particularly in payment systems, protocol engineering, security, distributed systems, systems architecture, and privacy engineering.
Current openings and the profiles ValiDeck expects to need are described on the Careers page. Even where no formal position is open, technically substantive introductions are welcome when there is a strong fit with the work ahead.