We contributed to building the ENS Gateway (using our dm3 existing resolver technology) to store ENS entries in Arbitrum but read them over CCIP in ENS (verifiable on Mainnet).

We are currently working on our next steps of Extending the dm3 protocol and SDK (and reference implementation) to allow users to store the dm3 profile at Arbitrum.

Currently, there is no fully web3-based, scalable, and interoperability-focused messaging core protocol for Arbitrum and even less one that brings the identity protocols as a core piece of the infrastructure. We can provide solutions not only for the entire Arbitrum ecosystem but also custom-made solutions for dApps that require custom-made messaging and identity management.
