Telepathy enables interoperability without compromise. Built with zkSNARKs, Telepathy allows developers to trustlessly communicate from Ethereum to any other chain with the security of Ethereum's light client protocol, without resorting to less secure multisigs or centralized actors. Live on Ethereum mainnet today. Start building with Telepathy on Ethereum mainnet and 8 supported EVM chains at docs.telepathy.xyz. Check out our demo at demo.telepathy.xyz. Fill out this form to become an early partner. Wen Mainnet? Mainnet Now. At Succinct, we’ve been hard at work over the past year for the mainnet launch of Telepathy. Telepathy is Ethereum’s first zkSNARK interoperability protocol secured by proof of consensus. Today, developers can use Telepathy to read Ethereum state on any other chain without any centralized actors in-between. Recent developments in zero-knowledge proofs allow for us to generate a succinct "proof of consensus"--allowing smart contracts on other chains to directly validate Ethereum state by running a gas-efficient light client. Developers can get started building with Telepathy today at: docs.telepathy.xyz. Try sending a cross-chain message with our demo and check its status on our message explorer. The protocol is currently live on Ethereum mainnet and 8 supported chains (Mainnet, Goerli, Gnosis, Polygon, Binance Smart Chain, Avalanche, Arbitrum and Optimism) and available for anyone to use. Security and transparency matter to us. Our protocol has 3 audits from top firms: Veridise, Trail of Bits (public report forthcoming) and Zellic, and a bug bounty program that will be launching soon with Immunifi. The code is also fully open-sourced: the smart contracts are here and the zkSNARK circuits are here. A detailed description of the protocol is here. To our knowledge, this is the first mainnet deployment of “zk-bridging” from Ethereum--a concept that people have been talking about for a long time, but is finally in production. This is just the first step in Succinct’s long journey in building the end-game of interoperability powered by zkSNARK proof of consensus.

Hi all, Uma from Succinct here. We're building a cross-chain interoperability solution secured with zkSNARKs that is significantly more decentralized, permissionless and censorship resistant compared to existing bridging solutions. While our protocol has not been deployed to mainnet as of right now, we plan on deploying our protocol to mainnet quite soon and I wanted to post in this forum, if not for official consideration, then to raise awareness of a new generation of bridging solutions that are highly aligned with the decentralization, permissionless and censorship resistant properties that Uniswap governance cares about. For some background on the general principal of light-client bridging enabled by zkSNARKs, here is an informational blog post that our team wrote: https://blog.succinct.xyz/post/2022/09/20/proof-of-consensus/ about the general idea. List 3 succinct reasons why you believe your bridge/solution would best serve Uniswap governance.Uniswap as a protocol fiercely cares about decentralization, censorship resistance and permissionlessness. This is evident in the deployment of all versions of the core protocol as non-upgradeable contracts with DAO-controlled voting for any protocol-level changes. Current bridging solutions that rely on permissioned multisigs or PoS validator sets do not inherit the underlying security of Ethereum and compromise on many of Uniswap's core values. We believe that on-chain succinct light clients powered by zkSNARK technology is the first time it's possible for a bridging solution to align fully with Uniswap's core values. Permissioned multisigs that back most existing bridges can forge fraudulent messages or censor valid messages. Permissionless, on-chain systems that verify the consensus of a source chain in the execution layer of a target chain are censorship resistant and not forgeable. As highlighted in the blog-post linked to above, we believe that zkSNARK-enabled succinct light clients are the end-game of cross-chain interoperability. Some of the cons of zkSNARK bridging currently include that it is slower than normal multisig bridging and costs more gas (due to the need to verify a zk proof on-chain vs. the minimal cost of verifying signatures from a multisig). For the governance use-case, where latency and gas-costs are relatively unimportant (as governance has a timelock anyways and messages are infrequent), the cons of zkSNARK bridging are not relevant.

Ramping Up on zkSNARKs / circuits In the background, it's probably good to ramp up on zkSNARKs and circuit stuff because we'll be doing a lot of that and it's fun :D Here are a few resources I've found helpful (by no means necesary to do all of them) Intro series to SNARKs (very similar to the talk I gave), read in the following order https://vitalik.ca/general/2016/12/10/qap.html https://dankradfeist.de/ethereum/2020/06/16/kate-polynomial-commitments.html https://vitalik.ca/general/2017/01/14/exploring_ecp.html (goes over Dankrad's post, but I find Dankrad's post more clear) https://vitalik.ca/general/2017/02/01/zk_snarks.html