Indexer infrastructure for Canton Network — Digital Asset's institutional finance chain. Privacy-aware storage, not permission-layer-on-top.
The core work is Indexer infrastructure for Canton Network. Canton is operated by regulated participants — banks, asset managers, market infrastructure providers — with privacy-by-default at the chain level. Public-DeFi indexers fail Canton's regulatory test. Zpoken builds the Indexer that holds the privacy boundary at the storage layer.
Canton inverts the public-DeFi norm of transparency-by-default. Two things matter for chain engineering on Canton.
Indexers on public chains assume that data is public and apply access control at the query layer. Canton's regulatory frame requires structural privacy at the storage layer — the indexer doesn't store what it isn't entitled to. This isn't a security layer over a fully replicated store; it's a different storage architecture from the ground up.
Canton's privacy semantics live deep in the chain's protocol layer, and the protocol evolves with the institutional applications running on top of it. An indexer built without chain-engineering input has to be rebuilt the first time the protocol semantics change. The Indexer is part of Canton's chain layer, not separate application middleware.
Engagements at this intersection led by Mike Yezhov and Anton Yezhov. See /founders.
If you're building infrastructure for an institutional or privacy-first chain — indexers, settlement systems, regulatory reporting layers — the engagement starts with a 30-minute call.
That call is with a founder. Shapes, discovery, and terms → /engagement