Polygon zkEVM
100× throughput for a production zkEVM
Gateway engineered cdk-erigon, an Erigon-based execution client for Polygon zkEVM, lifting sequencer throughput by two orders of magnitude in production.
Selected production engagements and institutional pilots, presented with clear attribution and evidence status.
Each record separates the customer context, Gateway contribution, and available result. Pilot and placeholder evidence is labeled explicitly.
Polygon zkEVM
Gateway engineered cdk-erigon, an Erigon-based execution client for Polygon zkEVM, lifting sequencer throughput by two orders of magnitude in production.
Global post-trade market infrastructure
A high-throughput blockchain deployment validated above 23,000 transactions per second, running entirely on the customer’s own premises.
Gnosis Pay
Gateway engineered and operated an early Optimism fork as the settlement chain behind Gnosis Pay, before the OP Stack was a packaged product.
Gnosis Chain
Production RPC infrastructure serving Gnosis Chain with published service levels and continuous operations.
Global technology company
Chain infrastructure priced for scale, combined with agentic identity permissioning for AI-agent workloads.
Latin American financial market infrastructure group
Organisation- and role-aware policy enforced at the JSON-RPC boundary for one of the world’s largest financial-market infrastructure groups: controlled access, attributable decisions, auditable operations.
Bank-consortium settlement network
Differentiated visibility between member banks: each participant sees its own flows while the operator retains an auditable whole.
Global post-trade market infrastructure
A privacy pilot applying deny-by-default access, purpose-bound supervisory views, and approved disclosure to post-trade workflows.
Evidence is presented with the boundary needed to interpret it responsibly.
What Gateway engineered, integrated, or operated is stated for each engagement.
Production records and scoped pilots are differentiated at first glance.
Confidential customers and evidence awaiting publication remain clearly marked.
Start with the operating context, control boundary, and evidence your institution needs.
Thank you