#621 Compliance Middleware SDK for Zenith EVM: acting on an issuer's decision recorded on Canton, seeking a champion

Hi all, I’m Mykola from Woof. We build and run DeFi infrastructure for Compound, and we’re proposing to bring part of that work to Canton. #621 is not yet funded.

We’re proposing an open-source SDK that lets a Solidity contract on Zenith EVM act on a compliance decision that stays on Canton. The application operator runs an authorizing service that reads the issuer’s or operator’s record through the Ledger API, checks the current decision and the address-to-party binding, and signs a short-lived permit for one specific EVM action. The contract trusts a configured signer and checks the permit’s binding, expiry, single use and the revocation path. Woof supplies the open-source code; each operator runs its own service. This Milestone 1 path does not depend on Gateway contract calls and runs on Zenith’s public EVM testnet.

The facts come from records the issuer or operator already controls: an issuer’s approval contract, the operator’s own compliance-status template, or the Registry App allowlist. The SDK defines no credential standard. The Registry App controls an issuer’s own instruments; this SDK covers a dApp’s own per-action permissions, including positions and LP shares. ChainSafe confirmed in the PR that it builds on #453’s address registration without overlapping it.

We’re requesting 1,248,700 CC across two milestones. 30% is paid only once two external teams integrate the SDK in a test environment and confirm it themselves.

Proposal: Proposal: Compliance Middleware SDK for EVM Developers on Zenith by Noosphere-314 · Pull Request #621 · canton-foundation/canton-dev-fund · GitHub
PoC: GitHub - woof-software/canton-compliance-poc · GitHub (EVM side), GitHub - woof-software/canton-localnet-poc · GitHub (Daml side)

We’re looking for a Tech & Ops Committee member willing to champion it.