As I fill out some exchange listing forms, I figured I'd bring some of the information over to X. Who are the target audience/users of the product? Primary users: • Institutions with EVM dependencies whose apps, custody, tokenization, or internal ledgers already assume Solidity, JSON-RPC, Ethereum account models, or EVM wallets. • Institutions on Hyperledger Besu / Quorum-style stacks that want to keep an Ethereum client and permissioning model, but compose with Canton RWAs instead of running a disconnected private chain. • Issuers and platforms using ERC RWA / security-token standards (ERC-1400, ERC-3643 (T-REX), ERC-1404, CMTAT, DS Protocol, and similar allowlist/transfer-restriction stacks) that need those contracts to settle against Canton-native assets. • Ethereum / Solidity teams who want to deploy existing DeFi apps (lending, perps, DEX, vaults) on Canton without rewriting in DAML. • Solana / SVM teams (upcoming) with the same goal once Zenith SVM is live. • Institutions on Canton (banks, market infrastructure, asset managers, repo/treasury desks) that want to compose with EVM/SVM based DeFi. • Consortium / enterprise operators who want a custom Zenith Stack chain (public, permissioned, private) instead of running their own infrastructure. Secondary users: • Canton-native participants (party-ID users, DAML apps) who need to interact with ERC-20 / EVM apps atomically. • DeFi protocols and market makers that want Canton RWAs (Treasuries, repo claims, deposits, stablecoin cash legs) as collateral, margin, or inventory. • Developers and integrators building wallets, oracles, and settlement venues across Canton and EVM. Zth.