The representative of Union held a video meetup called Hall Cast with Zama and Pyth, and here is a brief summary of why that happened. Similar Infrastructure Layer Characteristics - @union_build also has its own L1, where it handles common operations like proof aggregation. - Like Zama (FHE co-processor) and Pyth (Pythnet, a chain dedicated to price data transmission), Union also has the nature of a "common co-processor" that attaches to the blockchain. - In other words, all three projects share the commonality of being "supporting infrastructure with their own L1." Actual Shared Users/Ecosystem - For example, the Fluton team is using both Zama and Union simultaneously → they are already collaborating within the same ecosystem. - Union has strengths in bridging and proof aggregation, and combining Zama's privacy technology or Pyth's data feeds could make it even stronger. Privacy + Oracle + Bridge Synergy - Union: Asset movement between chains (bridge) & proof aggregation. - Zama: Can protect the privacy of the transfer amount/destination address during bridging. - Pyth: Provides real-time asset price information needed during bridging. → When these three are combined, a safe (private) and accurate (priced) bridge infrastructure can be created. Differences in Perspective - Union: Focused on cross-chain proof & liquidity infrastructure. - Zama: Focused on privacy (Confidentiality). - Pyth: Focused on real-time data (Data Oracle). Therefore, the key point is that Union is not in a competitive relationship with Zama and Pyth, but rather positioned to complement each other.