The rollup centric roadmap enabled scalable blockspace. But scalable blockspace is just the first step. It has to be supplemented by native interoperability. Scaling is interoperability and interoperability is scalability. Incomplete without the other. The next frontier is to enable users on any chain to be able to access apps on a particular chain. Users shouldn't have to think about bridging or changing RPCs as such. That's we are doing with Avail Nexus. The current working solution is to solve this with liquidity providers and solvers, which is a great start. The downside of this is that bigger chains will attract the most solvers because of unit economics. TEE-based approaches will also come to production pretty soon. We are working on one with @Ternoa_. But this will eventually be replaced with zk proof aggregation in a year or two once proving becomes real time or very fast. @AvailProject Nexus is a proof verification runtime. It tracks rollup/chain intermediate and latest state roots and other metadata, essentially acting as a shared bridge. The beauty is that Avail Nexus itself is written against a zkVM - currently @RiscZero but also a parallel implementation in @SuccinctLabs SP1. So the Nexus proof itself is a succinct zk proof that is verified on a Avail pallet on the base layer. Nexus not only verifies zk execution proofs, but it can also verify attestation proofs and others - so we will support all kinds of proving systems. The medium-term intent is to arrive at horizontally scalable chains with uniform trust assumptions. App infra that developers can use as simple as them using something like AWS RDS for databases. Being able to bring liquidity and users from other chains seamlessly to the Avail ecosystem of chains is going to be one of our big focus areas this coming months. Pumped!